Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-yimingyan-fivetran-mcp": {
"args": [
"-y",
"wrangler"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Note: This repository is built and maintained entirely by Claude Code, Anthropic's AI coding assistant.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'wrangler' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Wrangler affected by OS Command Injection in `wrangler pages deploy`
**Summary** A command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. **Root cause** The `commitHash` variable, derived from user input via the `--commit-hash` CLI argument, is interpolated directl
Arbitrary remote code execution within `wrangler dev` Workers sandbox
### Impact The V8 inspector intentionally allows arbitrary code execution within the Workers sandbox for debugging. `wrangler dev` would previously start an inspector server listening on all network interfaces. This would allow an attacker on the local network to connect to the inspector and run arbitrary code. Additionally, the inspector server did not validate `Origin`/`Host` headers, granting an attacker that can trick any user on the local network into opening a malicious website the ability
Arbitrary remote file read in Wrangler dev server
### Impact Sending specially crafted HTTP requests and inspector messages to Wrangler's dev server could result in any file on the user's computer being accessible over the local network. An attacker that could trick any user on the local network into opening a malicious website could also read any file. ### Patches This issue was fixed in `wrangler@3.19.0`. Wrangler will now only serve files that are part of your bundle, or referenced by your bundle's source maps. ### Workarounds Configure Wr
Cloudflare Wrangler directory traversal vulnerability
### Impact The Wrangler command line tool (<=wrangler@3.1.0 or <=wrangler@2.20.1) was affected by a directory traversal vulnerability when running a local development server for Pages (wrangler pages dev command). This vulnerability enabled an attacker in the same network as the victim to connect to the local development server and access the victim's files present outside of the directory for the development server. ### Patches Wrangler2: Upgrade to v2.20.1 or higher. Wrangler3: Upgrade to v3
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in data
Query and manage PostgreSQL databases directly from AI assistants
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
Manage Supabase projects — databases, auth, storage, and edge functions
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
MCP Security Weekly
Get CVE alerts and security updates for io.github.YimingYAN/fivetran-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Note: This repository is built and maintained entirely by Claude Code, Anthropic's AI coding assistant.
An MCP (Model Context Protocol) server for controlling Fivetran data pipelines. Enables AI assistants like Claude to manage syncs, monitor connection status, and control data pipelines through natural language.
See Fivetran API Getting Started for more details.
Add to your ~/.env.local (or equivalent):
# Fivetran API
export FIVETRAN_API_KEY="your-api-key"
export FIVETRAN_API_SECRET="your-api-secret"
Then reload:
source ~/.env.local
Test that your credentials work:
curl -s -X GET "https://api.fivetran.com/v1/account/info" \
-H "Accept: application/json" \
-H "Authorization: Basic $(echo -n "$FIVETRAN_API_KEY:$FIVETRAN_API_SECRET" | base64)"
Expected response:
{"code":"Success","data":{"account_id":"...","account_name":"..."}}
Add to your ~/.claude.json:
{
"mcpServers": {
"fivetran": {
"type": "stdio",
"command": "uvx",
"args": ["fivetran-mcp@latest"],
"env": {
"FIVETRAN_API_KEY": "${FIVETRAN_API_KEY}",
"FIVETRAN_API_SECRET": "${FIVETRAN_API_SECRET}"
}
}
}
}
Restart Claude Code to load the new MCP server. You should now have access to Fivetran tools.
| Tool | Description |
|---|---|
list_connections | List all connections, optionally filtered by group |
get_connection_status | Get detailed status including tasks, warnings, and sync details |
trigger_sync | Start a sync for a connection (optional force flag) |
trigger_resync | Trigger full historical resync |
resync_tables | Resync specific tables only (e.g., ["schema.table_name"]) |
pause_connection | Pause a connection |
resume_connection | Resume a paused connection |
list_groups | List all groups/destinations |
test_connection | Run diagnostic tests to identify connectivity/configuration issues |
| Tool | Description |
|---|---|
get_connection_schema | Get schema info with optional table filter (includes columns when filtering) |
get_schema | Get complete raw schema configuration for a connection |
list_tables | List al |