Fivetran moves data from hundreds of sources into a warehouse, and most of the day-to-day questions about it are small and awkward: did the Postgres connector finish, which connections are broken, when did this destination last load. Answering them means opening the dashboard and clicking through connector pages. The Fivetran MCP Server is Fivetran's first-party Model Context Protocol server that puts those questions inside whatever MCP client you already work in.
How it exposes the API
Rather than registering one tool per endpoint — which would flood a client's tool list — the server uses a discovery-then-execute shape:
list_endpoints browses the available API operations by category or free-text search.get_schema returns the parameter and response schema for a chosen operation, and with a service parameter returns the connector-specific configuration fields for a particular source.- Execution tools are resource/action pairs such as
connections_read, connections_write and destinations_delete.
That design keeps the tool surface small while still reaching the whole API, and it means the agent reads the real schema before it constructs a call.
Permissions are opt-in, not implied
The server starts read-only. FIVETRAN_SCOPE widens it to read/write or read/write/delete, and DISALLOWED_ACTIONS denies individual operations by resource:action. The README's recommended denylist blocks the credential-adjacent endpoints — system-keys:read, the user API-key read/create/rotate/delete operations — so an agent with write scope still cannot mint itself a key. Setting that denylist is worth doing before the first run rather than after.
Running it
It is a Python package (3.10+) run through uv, with no install step required:
uvx --from git+https://github.com/fivetran/fivetran-mcp fivetran-mcp
It authenticates with a Fivetran API key and secret. For team use it can also run as a hosted HTTP service with --transport streamable-http --host 0.0.0.0 --port 8000, and the repository ships plugin repositories (for example copy-connections) that add higher-level operations on top.
Who it is for
Data and analytics engineers who already run Fivetran and want incident triage and routine connector questions answered without a context switch. It is not a replacement for the Fivetran UI — it is the same API, addressed in language, with a permission model you configure up front.
MIT licensed, maintained in Fivetran's own GitHub organisation.