Fivetran MCP Server (Cloud Run Hosted)

Production-ready Model Context Protocol server for Fivetran, Claude Code and Gemini CLI-compatible, deployed as a remote MCP Server on Google Cloud Run.

Based on: Official Fivetran MCP Server by Fivetran
Cloud Run Extension: Mark Rittman (@markrittman) | Rittman Analytics

Origin and Extensions

This project is based on the official Fivetran MCP Server, which provided the original set of Fivetran MCP tools using the stdio transport. We extended it significantly for production Cloud Run deployment:

What changed	Detail
Transport	Replaced stdio with HTTP (FastAPI) for Cloud Run
Authentication	Per-request header auth (`X-Fivetran-API-Key` / `X-Fivetran-API-Secret`)
Tool count	Expanded from 25 to 78 tools covering the full Fivetran REST API
Test suite	225 tests at 94% coverage (unit, integration, protocol, e2e)
OAuth 2.1 layer	Optional OAuth flow for Claude.ai web integration
GCP Secret Manager	Encrypted credential storage for the OAuth flow
Containerisation	Dockerfile + Cloud Build + one-command deployment scripts

What This Enables

The Fivetran MCP Server lets Claude manage your Fivetran account through natural language. Ask Claude to:

List all connections and check their sync status
Create new connectors to SaaS tools, databases, or files
Trigger, pause, or resume syncs
Enable or disable specific tables and columns
Run dbt transformations
Manage destinations, groups, users, and webhooks

All 78 operations map directly to the Fivetran REST API v1.

Deploy Your Own Instance

Prerequisites

Google Cloud Platform account with billing enabled
gcloud CLI installed and authenticated
Docker (for local testing only)
GCP roles: Cloud Run Admin, Secret Manager Admin, Service Account Admin, Cloud Build Editor

1. Clone and configure

git clone https://github.com/rittmananalytics/Fivetran-MCP-Server-on-Cloud-Run.git
cd Fivetran-MCP-Server-on-Cloud-Run

export GCP_PROJECT_ID="your-gcp-project-id"
export CLOUD_RUN_REGION="europe-west2"   # change to your preferred region

2. Set up a service account

chmod +x setup-service-account.sh
./setup-service-account.sh

This creates a service account with permissions for Secret Manager and Cloud Logging.

3. Deploy to Cloud Run

chmod +x deploy.sh
./deploy.sh

The script will:

Enable required GCP APIs
Build the container image using Cloud Build
Store a generated JWT secret in Secret Manager
Deploy the service to Cloud Run
Print the service URL

4. Verify

SERVICE_URL=$(gcloud run services describe fivetran-mcp-server \
    --platform managed --region ${CLOUD_RUN_REGION} \
    --format 'value(status.url)')

curl ${SERVICE_URL}/health
# {"status":"healthy","version":"2.0.0"}

After deployment you'll have these endpoints:

Endpoint	Purpose
`https://your-service-url/health`	Health check
`https://your-service-url/mcp`	MCP JSON-RPC
`https://your-service-url/authorize`	OAuth 2.1 authorisation
`https://your-service-url/token`	OAuth 2.1 token

Updating

git pull
./deploy.sh

Cost estimate

Service	Cost
Cloud Run	~$0 at rest; ~$0.10–$1/day under active use
Secret Manager	$0.06 per 10,000 accesses
Cloud Build	120 build-minutes/day free
Total	< $5/month for light usage

Setting Up in Claude Code

Option A: Direct header auth (recommended)

This is the simplest approach — credentials are passed as HTTP headers on every request.

Add the following to ~/.claude/mcp_settings.json:

{
  "mcpServers": {
    "fivetran": {
      "url": "https://YOUR-SERVICE-URL/mcp",
      "transport": "http",
      "headers": {
        "X-Fivetran-API-Key": "YOUR_FIVETRAN_API_KEY",
        "X-Fivetran-API-Secret": "YOUR_FIVETRAN_API_SECRET"
      }
    }
  }
}

Get your API credentials from Fivetran dashboard → Account → Settings → API Config.

Restart Claude Code after editing mcp_settings.json.

Option B: OAuth 2.1 flow

If you prefer not to store credentials in config files, use the OAuth flow:

{
  "mcpServers": {
    "fivetran": {
      "url": "https://YOUR-SERVICE-URL/mcp",
      "transport": "http",
      "auth": {
        "type": "oauth2",
        "authorizationUrl": "https://YOUR-SERVICE-URL/authorize",
        "tokenUrl": "https://YOUR-SERVICE-URL/token",
        "clientId": "claude-code",
        "scopes": ["fivetran:read", "fivetran:write"]
      }
    }
  }
}

On first use, Claude will provide an authorisation URL. Open it, enter your Fivetran credentials, and a JWT token (valid for 1 hour) will be issued and stored.

Verifying the connection

In Claude Code, ask:

List my Fivetran connections

Claude will call list_connections and return your connectors.

Using the Claude Code Skill

This repo includes a Claude Code skill at .claude/skills/fivetran/SKILL.md that provides Claude with detailed guidance on all 78 tools, common workflows, and safety guidelines.

The skill activates automatically when you're working with Fivetran topics. You can also invoke it directly with /fivetran.

Available Tools (78)

Account (1)

Tool	Description
`get_account_info`	Get account information for the current credentials

Connections (13)

Tool	Description
`list_connections`	List all connections (auto-paginates)
`create_connection`	Create a new connection
`get_connection_details`	Full details including status and config
`modify_connection`	Update settings (sync frequency, paused, etc.)
`delete_connection`	Destructive. Permanently delete a connection
`get_connection_state`	Detailed sync state
`modify_connection_state`	Update sync state
`sync_connection`	Trigger an immediate sync
`resync_connection`	Full historical re-sync
`resync_tables`	Re-sync specific tables
`run_connection_setup_tests`	Verify connection config
`create_connect_card`	Create embed token for Fivetran setup UI
`get_connection_url`	Dashboard URL for a connection

Schema / Table / Column Config (9)

Tool	Description
`get_connection_schema_config`	Which tables and columns are enabled
`reload_connection_schema_config`	Discover new tables from source
`modify_connection_schema_config`	Bulk enable/disable schemas and tables
`modify_connection_database_schema_config`	Update a specific database schema
`get_connection_column_config`	Column-level config for a table
`modify_connection_table_config`	Enable or disable a table
`modify_connection_column_config`	Enable/disable or hash a column
`delete_connection_column_config`	Remove a blocked column config entry
`delete_multiple_columns_connection_config`	Remove multiple blocked column entries

Destinations (6)

Tool	Description
`list_destinations`	All destinations (auto-paginates)
`create_destination`	Create a new destination
`get_destination_details`	Config for a specific destination
`modify_destination`	Update destination config
`delete_destination`	Destructive. Delete a destination
`run_destination_setup_tests`	Verify destination connectivity

Groups (11)

Tool	Description
`list_groups`	All groups (auto-paginates)
`create_group`	Create a new group
`get_group_details`	Details for a specific group
`modify_group`	Update a group
`delete_group`	Destructive. Delete a group
`list_connections_in_group`	Connections in a group (auto-paginates)
`list_users_in_group`	Users in a group (auto-paginates)
`add_user_to_group`	Add a user to a group
`delete_user_from_group`	Destructive. Remove a user from a group
`get_group_ssh_public_key`	SSH public key for a group
`get_group_service_account`	Service account email for a group

Log Services (6)

Tool	Description
`list_log_services`	All external log services
`create_log_service`	Create a new log service
`get_log_service_details`	Details for a specific log service
`update_log_service`	Update a log service
`delete_log_service`	Destructive. Delete a log service
`run_log_service_setup_tests`	Test a log service

Hybrid Deployment Agents (6)

Tool	Description
`list_hybrid_deployment_agents`	All hybrid agents
`create_hybrid_deployment_agent`	Create a new agent
`get_hybrid_deployment_agent`	Details for a specific agent
`re_auth_hybrid_deployment_agent`	Regenerate agent credentials
`reset_hybrid_deployment_agent_credentials`	Reset agent credentials
`delete_hybrid_deployment_agent`	Destructive. Delete an agent

Connector Metadata (3)

Tool	Description
`list_metadata_connectors`	All connector types with metadata
`get_metadata_connector_config`	Detailed config schema for a connector type
`list_public_connectors`	Public connector list (no auth required)

Transformations (16)

Tool	Description
`list_transformation_projects`	All transformation projects
`create_transformation_project`	Create a new project
`get_transformation_project_details`	Details for a specific project
`modify_transformation_project`	Update a project
`delete_transformation_project`	Destructive. Delete a project
`test_transformation_project`	Run project tests
`list_transformations`	All transformations
`create_transformation`	Create a new transformation
`get_transformation_details`	Details for a specific transformation
`update_transformation`	Update a transformation
`delete_transformation`	Destructive. Delete a transformation
`run_transformation`	Trigger a transformation run
`cancel_transformation`	Cancel a running transformation
`upgrade_transformation_package`	Upgrade dbt package version
`list_transformation_package_metadata`	Quickstart package metadata
`get_transformation_package_metadata_details`	Details for a quickstart package

Webhooks (7)

Tool	Description
`list_webhooks`	All webhooks
`create_account_webhook`	Create an account-level webhook
`create_group_webhook`	Create a group-level webhook
`get_webhook_details`	Details for a specific webhook
`modify_webhook`	Update a webhook
`delete_webhook`	Destructive. Delete a webhook
`test_webhook`	Send a test event to a webhook

Example Conversations

Check sync health

You: Are any of my connections failing?

Claude: I'll check all connections...
[calls list_connections]

Found 1 issue:
• mysql_orders — Last failed 3 hours ago (connection timeout)
  Recommendation: Check database firewall rules

Create a new connector

You: Create a Calendly connection syncing to the marketing group

Claude: I'll check the Calendly connector config first...
[calls get_metadata_connector_config with service="calendly"]
[calls list_groups to find group_id]
[calls create_connection]
[calls modify_connection to set auth.access_token]
[calls run_connection_setup_tests]

Created connection "calendly_marketing" in the marketing destination.
Setup test: PASSED. First sync will begin within the hour.

Pause for maintenance

You: Pause all production connections for database maintenance

Claude: [calls list_connections, filters by name pattern]
[calls modify_connection for each with paused=true]

Paused 4 connections:
• postgres_production
• mysql_orders
• mongodb_events
• redis_sessions

Development

# Install dependencies
make install

# Run tests
make test

# Lint + type-check + test + coverage
make verify

# Format code
make format

Test coverage target: ≥ 85% on src/.

Security

Credentials are never logged
All Fivetran API communication uses HTTPS
Set FIVETRAN_ALLOW_WRITES=false to run in read-only mode (blocks all mutating tools)

Rotate the JWT secret periodically:

NEW_SECRET=$(openssl rand -base64 32)
echo -n "${NEW_SECRET}" | gcloud secrets versions add fivetran-mcp-jwt-secret --data-file=-
gcloud run services update fivetran-mcp-server --region ${CLOUD_RUN_REGION}

Troubleshooting

Issue	Solution
Claude can't find tools	Check `mcp_settings.json`, restart Claude Code
400 on every request	Verify `X-Fivetran-API-Key` and `X-Fivetran-API-Secret` headers are set
Connection setup test fails	Call `get_metadata_connector_config` to check correct field names; OAuth connectors need `auth.access_token` not `config.api_token`
Service unavailable	Check `gcloud run services list`; view logs with `gcloud logging read "resource.labels.service_name=fivetran-mcp-server" --limit=20`
Deployment fails	Ensure billing is enabled; run `gcloud auth login`; check Cloud Build logs

Acknowledgements

Built on the Model Context Protocol by Anthropic
Powered by the Fivetran REST API v1
Based on the official Fivetran MCP Server by Fivetran

This is an unofficial community project and is not affiliated with or endorsed by Fivetran Inc.

Name		Name	Last commit message	Last commit date
Latest commit History 4 Commits
.claude/skills/fivetran		.claude/skills/fivetran
docs		docs
examples		examples
src		src
tests		tests
.dockerignore		.dockerignore
.gitattributes		.gitattributes
.gitignore		.gitignore
CONTRIBUTING.md		CONTRIBUTING.md
Dockerfile		Dockerfile
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md
deploy.sh		deploy.sh
pytest.ini		pytest.ini
requirements.txt		requirements.txt
setup-service-account.sh		setup-service-account.sh

Uh oh!

Folders and files

Latest commit

History

Repository files navigation

Fivetran MCP Server (Cloud Run Hosted)

Origin and Extensions

What This Enables

Deploy Your Own Instance

Prerequisites

1. Clone and configure

2. Set up a service account

3. Deploy to Cloud Run

4. Verify

Updating

Cost estimate

Setting Up in Claude Code

Option A: Direct header auth (recommended)

Option B: OAuth 2.1 flow

Verifying the connection

Using the Claude Code Skill

Available Tools (78)

Account (1)

Connections (13)

Schema / Table / Column Config (9)

Destinations (6)

Groups (11)

Log Services (6)

Hybrid Deployment Agents (6)

Connector Metadata (3)

Transformations (16)

Webhooks (7)

Example Conversations

Check sync health

Create a new connector

Pause for maintenance

Development

Security

Troubleshooting

Acknowledgements

About

Resources

License

Contributing

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors

Uh oh!

Languages

Packages