fivetran-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIVETRAN_API_KEY | Yes | Your Fivetran API key | |
| FIVETRAN_API_SECRET | Yes | Your Fivetran API secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_connectionsA | List all Fivetran connections (connectors) with their sync status. Optionally filter by group. |
| get_connection_detailsA | Get detailed information for a specific connection including config, status, sync state, and schedule. |
| create_connectionA | Create a new Fivetran connection (connector). Use get_connector_metadata to discover available connector types and their required config. Returns compact confirmation by default — set verbose=true for full response. |
| update_connectionA | Update a connection's configuration, schedule, or settings. Returns compact confirmation by default — set verbose=true for full response. |
| delete_connectionA | Permanently delete a connection and all its synced data configuration. This cannot be undone. |
| trigger_syncA | Trigger an immediate sync for a connection without waiting for the next scheduled sync. Returns compact confirmation by default — set verbose=true for full response. |
| pause_connectionA | Pause a connection's sync schedule. The connection will not sync until resumed. Returns compact confirmation by default — set verbose=true for full response. |
| resume_connectionA | Resume a paused connection. It will sync on its next scheduled interval. Returns compact confirmation by default — set verbose=true for full response. |
| get_connection_schemaA | Get the schema configuration for a connection: all schemas, tables, and columns with their enabled/disabled state. |
| update_connection_schemaA | Update schema config to enable/disable schemas, tables, or columns for a connection. Returns compact confirmation by default — set verbose=true for full schema response. |
| reload_schemaA | Reload the schema configuration from the source. Detects new tables, columns, or schema changes. Returns compact confirmation by default — set verbose=true for full response. |
| get_sync_statusA | Get the current sync status for a connection: sync state, last sync time, schedule, and any warnings or failures. |
| get_table_statusA | Get per-table sync status for a connection: enabled state, sync mode, and metadata for each table. |
| get_sync_logsB | Get sync logs for a connection. Returns the connection state including sync history and warnings. |
| list_groupsA | List all groups (workspaces) in the Fivetran account. |
| get_group_connectorsA | List all connections within a specific group. |
| list_destinationsB | List all destinations in the account with their configuration and status. |
| test_destinationA | Run setup tests for a destination to verify connectivity and configuration. Returns compact confirmation by default — set verbose=true for full response. |
| list_usersB | List all users in the Fivetran account. |
| invite_userA | Invite a new user to the Fivetran account with a specified role. Returns compact confirmation by default — set verbose=true for full response. |
| list_teamsB | List all teams in the Fivetran account. |
| resync_tablesA | Force a historical resync of specific tables within a connection. Only re-syncs the specified tables, not the entire connection. Returns compact confirmation by default — set verbose=true for full response. |
| get_connector_metadataA | Get available connector types and their configuration schemas. Use this to discover what connectors Fivetran supports and what config each requires. |
| searchA | Search the Fivetran REST API catalog to discover endpoints. Returns method, path, summary, and parameter details. Call with no arguments to see all available categories. |
| executeA | Execute any Fivetran REST API call. Use the search tool first to discover available endpoints and their parameters. Write operations return compact summaries by default — set verbose=true for full response. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
Most tools have clear verb+noun names, but several overlap in purpose: get_connection_details, get_sync_status, and get_sync_logs all report sync/status information, and list_connections overlaps with get_group_connectors. Descriptions help, but an agent could still plausibly pick the wrong status or schema tool. This overlap prevents a higher score.
Tool names overwhelmingly follow a predictable snake_case verb_noun pattern, with list_*, get_*, create_*, update_*, and delete_* dominating. The pattern is weakened by the bare verbs search and execute, plus reload_schema missing the connection_ prefix and get_group_connectors using get instead of list. These are minor deviations from an otherwise consistent scheme.
25 tools sits at the high end of the 'heavy' range and covers many resource areas: connections, schema, sync, groups, destinations, users, teams, and generic API access. Each tool has a purpose, but the set could likely be trimmed by consolidating overlapping status/log tools and relying more on execute. It is not extreme enough for a 2, but it is not a tight, well-scoped surface.
The connection lifecycle is solid: create/get/update/delete, schema management, sync triggers, and resync are all present. However, destination setup is incomplete with only list/test and no create/update/delete, and user/group/team management stops at listing or inviting. The search/execute escape hatch can work around these gaps, but the high-level tool surface has notable missing lifecycle operations.