Fivetran MCP Server
OfficialServer 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 | |
| FIVETRAN_ALLOW_WRITES | No | Set to 'true' to enable POST, PATCH, and DELETE operations | false |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_endpointsA | Discover Fivetran API endpoints. With no arguments, returns {categories: {category: count}, callable_counts: {category: n}, total: N}. Provide |
| get_schemaA | Return the full schema for a Fivetran endpoint — description, parameters, request body schema, response schema. Provide |
| account_readA | Read operations on Fivetran account (1 endpoints: get_account_info). Pass the endpoint name in |
| connections_readA | Read operations on Fivetran connections (12 endpoints: connection_column_config, connection_details, connection_moved_job_status, connection_schema_config, connection_state, connection_sync_history, connection_warnings, get_connection_certificate_details, + 4 more). Pass the endpoint name in |
| connector_sdk_readA | Read operations on Fivetran connector sdk (3 endpoints: download_connector_sdk_package, get_connector_sdk_package, list_connector_sdk_packages). Pass the endpoint name in |
| destinations_readA | Read operations on Fivetran destinations (6 endpoints: destination_details, get_destination_certificate_details, get_destination_certificates_list, get_destination_fingerprint_details, get_destination_fingerprints_list, list_destinations). Pass the endpoint name in |
| external_logging_readA | Read operations on Fivetran external logging (3 endpoints: get_account_log_service_details, get_log_service_details, list_log_services). Pass the endpoint name in |
| external_secrets_managers_entities_readA | Read operations on Fivetran external secrets managers entities (1 endpoints: list_esm_entities). Pass the endpoint name in |
| external_secrets_managers_readA | Read operations on Fivetran external secrets managers (3 endpoints: get_esm_details, get_esm_entities, list_esms). Pass the endpoint name in |
| groups_readA | Read operations on Fivetran groups (6 endpoints: group_details, group_service_account, group_ssh_public_key, list_all_connections_in_group, list_all_groups, list_all_users_in_group). Pass the endpoint name in |
| hybrid_deployment_agents_readA | Read operations on Fivetran hybrid deployment agents (2 endpoints: get_hybrid_deployment_agent, get_hybrid_deployment_agent_list). Pass the endpoint name in |
| metadata_readA | Read operations on Fivetran metadata (2 endpoints: metadata_connector_config, metadata_connectors). Pass the endpoint name in |
| private_links_readA | Read operations on Fivetran private links (2 endpoints: get_private_link_details, get_private_links). Pass the endpoint name in |
| proxy_readA | Read operations on Fivetran proxy (3 endpoints: get_proxy_agent, get_proxy_agent_connections, get_proxy_agent_details). Pass the endpoint name in |
| public_readA | Read operations on Fivetran public (1 endpoints: metadata_public_connectors). Pass the endpoint name in |
| roles_readA | Read operations on Fivetran roles (1 endpoints: list_all_roles). Pass the endpoint name in |
| system_keys_readA | Read operations on Fivetran system keys (2 endpoints: get_system_key_details, get_system_keys). Pass the endpoint name in |
| teams_readA | Read operations on Fivetran teams (8 endpoints: get_team_membership_in_connection, get_team_membership_in_group, get_team_memberships_in_connections, get_team_memberships_in_groups, get_user_in_team, list_all_teams, list_users_in_team, team_details). Pass the endpoint name in |
| transformation_projects_readA | Read operations on Fivetran transformation projects (2 endpoints: list_all_transformation_projects, transformation_project_details). Pass the endpoint name in |
| transformations_readA | Read operations on Fivetran transformations (4 endpoints: transformation_details, transformation_package_metadata_details, transformation_package_metadata_list, transformations_list). Pass the endpoint name in |
| users_readA | Read operations on Fivetran users (8 endpoints: get_user_api_key, get_user_membership_in_connections, get_user_membership_in_group, get_user_memberships_in_connections, get_user_memberships_in_groups, list_all_users, list_api_keys, user_details). Pass the endpoint name in |
| webhooks_readA | Read operations on Fivetran webhooks (2 endpoints: list_all_webhooks, webhook_details). Pass the endpoint name in |
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 22 tools
Tools are mostly distinct by Fivetran resource category (account, connections, destinations, users, etc.), and meta-tools like list_endpoints and get_schema serve unique discovery/schema roles. Minor overlap exists between metadata_read and public_read, and all category tools share a near-identical 'pass endpoint name' template, but boundaries remain clear.
All names use snake_case; category tools consistently follow [resource]_read, and meta-tools use list_endpoints/get_schema. A fully uniform verb_noun pattern is not achieved because read tools are noun_read, but the convention is predictable and readable.
22 tools is above the typical 3-15 range and feels heavy, with many single-endpoint category wrappers (e.g., roles_read, public_read, account_read) that could have been consolidated. Each tool still maps to a meaningful API category, so it is borderline rather than excessive.
The surface is entirely read-only, with no create/update/delete/merge operations for any Fivetran resource, so common lifecycle tasks (creating a connector, updating a destination, deleting a user) are impossible. Read coverage is broad across categories, but the absence of write operations is a significant gap for a Fivetran management server.