A side-by-side look at the Fivetran MCP and MCP Data Pipeline Connector MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Fivetran MCP for data platforms work as a local process; choose MCP Data Pipeline Connector for data platforms as a local process. You can also run both side by side in one mcpServers block.
list_connections, get_connection_status, trigger_sync.connect_source, list_sources, list_tables.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Platforms | Data Platforms |
| Quality signal | 53/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 15 | 7 |
| Full listing | View Fivetran MCP | View MCP Data Pipeline Connector |
list_connectionsList all Fivetran connections in the account.get_connection_statusGet detailed status for a specific Fivetran connection.
Returns comprehensive information including sync state, tasks with full details,
warnings, and scheduling configuration. Use this for investigating connection
issues and understanding sync status.trigger_syncTrigger a data sync for a Fivetran connection.
This starts a sync without waiting for the next scheduled sync time.
Does not override the standard sync frequency.trigger_resyncTrigger a full historical resync for a Fivetran connection.
This re-syncs all historical data from the source. Use with caution
as it may take significant time and resources.resync_tablesTrigger a historical resync for specific tables within a connection.
This re-syncs historical data only for the specified tables, not the entire
connection. Useful when you need to refresh specific tables without a full resync.pause_connectionPause a Fivetran connection.
Paused connections will not sync data until resumed.resume_connectionResume a paused Fivetran connection.
The connection will start syncing according to its schedule.list_groupsList all Fivetran groups (destinations) in the account.
Groups represent destinations where data is synced to.test_connectionTest a Fivetran connection to diagnose connectivity and configuration issues.
Executes diagnostic tests to identify root causes when syncs fail, validate
connection health proactively, and support incident response workflows.get_schemaRetrieve the complete schema configuration for a Fivetran connection.
Returns all schemas and tables with their enabled/disabled status,
sync modes, and configuration. Useful for understanding what data
is being synced and investigating missing tables.get_connection_schemaRetrieve schema information for a Fivetran connection with optional table filter.
When called without a table parameter, returns all schemas and tables.
When a table is specified (format: "schema.table_name"), returns detailed
information for that specific table including all column metadata.
This is useful for:
- Debugging dbt model failures when columns are missing
- Detecting schema changes
- Building new models with accurate column metadata
- Identifying which columns are actively synced vs excludedlist_tablesList all tables in a Fivetran connection with their sync status.
Provides a flattened view of all tables across all schemas,
showing enabled status, sync mode, and configuration.
Useful for quickly seeing which tables are being synced.connect_sourcelist_sourceslist_tablesget_schemaquerytransformcheck_healthPaste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"fivetran-mcp": {
"command": "uvx",
"args": [
"fivetran-mcp@latest"
]
}
}
}
{
"mcpServers": {
"mcp-data-pipeline-connector": {
"command": "npx",
"args": [
"-y",
"mcp-data-pipeline-connector@latest"
]
}
}
}