fivetran-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIVETRAN_API_KEY | No | Fivetran API key (preferred) | |
| FIVETRAN_API_SECRET | No | Fivetran API secret (preferred) | |
| FIVETRAN_SYNC_API_KEY | No | Fivetran API key (alternative) | |
| FIVETRAN_SYNC_API_SECRET | No | Fivetran API secret (alternative) |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_connectionsC | List all Fivetran connections in the account. |
| get_connection_statusA | Get 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_syncA | Trigger 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_resyncA | Trigger 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_tablesA | Trigger 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_connectionA | Pause a Fivetran connection. Paused connections will not sync data until resumed. |
| resume_connectionA | Resume a paused Fivetran connection. The connection will start syncing according to its schedule. |
| list_groupsA | List all Fivetran groups (destinations) in the account. Groups represent destinations where data is synced to. |
| test_connectionA | Test 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_schemaB | Retrieve 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_schemaA | Retrieve 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:
|
| list_tablesA | List 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. |
| get_table_columnsA | Retrieve column details for a specific table in a Fivetran connection. Returns column names, sync configuration, and metadata. Useful for investigating schema issues or understanding table structure. Note: Column data types are not available via the Fivetran API. Data types can be queried directly from your destination database. |
| reload_schemaA | Reload the schema configuration from the source for a Fivetran connection. Fetches the latest schema from the data source and updates the configuration. Useful after source schema changes to detect new tables or columns. |
| get_table_statusA | Get per-table sync status for a Fivetran connection. Returns detailed status for each table including enabled/disabled state, sync configuration, and metadata from the most recent successful sync. Useful for debugging large connectors with many tables, identifying stale tables, and monitoring data freshness. For connectors with many tables (e.g., Airtable with 20+ bases, or Postgres with 50+ tables), this provides visibility into which specific tables are configured and their sync settings. Note: Table metadata (like destination names) is only available after at least one successful sync has completed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/YimingYAN/fivetran-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server