curl.
Set it up in Cursor
Add this to~/.cursor/mcp.json, or to .cursor/mcp.json in a project:
<connector_id>:
Tools
Suggested order for a database:
connector_status, list_connections, list_tables, list_columns or describe_table, then query.
Suggested order for files: connector_status, list_filesystems, fs_du on a candidate folder, fs_ls, then fs_search if you need to look inside.
Try a prompt such as: “Using the timbal-connector-erp tools, list the tables in erp and describe the ones about customers.”
Behaviour
- The tools do exactly what the equivalent HTTP requests do: same limits, same capability checks, same audit entry for
query(markedvia=mcp). - The connection’s
querysetting on the server still decides whatquerymay do. - Every tool except
connector_statusneeds the connector online;connector_statusstill answers when it is offline. A connector that is offline, or lacks a capability, returns a tool error with the same message as the API. Nothing here can reach a server the connection can’t. - It does not start jobs or syncs, copy files into a knowledge base, or push configuration. For those, use the API.
Next steps
Sync your data
Start a job or schedule a sync.
MCP integration
Connect Timbal’s own tools to your IDE.