Mcp Fivetran

Created By
andrewkkchana year ago
Overview

what is MCP Fivetran?

MCP Fivetran is a server implementation that allows AI assistants to manage Fivetran accounts through a simple API interface, enabling user management and connection operations.

how to use MCP Fivetran?

To use MCP Fivetran, configure your local MCP client with your Fivetran API token and run the server using the provided commands. You can then interact with the server to manage users and connections.

key features of MCP Fivetran?

  • API interface for managing Fivetran accounts
  • User invitation and management
  • Connection listing and sync triggering

use cases of MCP Fivetran?

  1. Inviting new users to a Fivetran account.
  2. Listing all connections in a Fivetran account.
  3. Triggering syncs for specific connections.

FAQ from MCP Fivetran?

  • What is required to use MCP Fivetran?

You need a Fivetran account with API access and a valid API authentication token.

  • Is there a specific Python version required?

Yes, Python 3.12.8 or higher is required to run MCP Fivetran.

  • How do I install MCP Fivetran?

You can install it using the provided installation commands with the uv tool.

Server Config

{
  "mcpServers": {
    "fivetran": {
      "command": "uvx",
      "args": [
        "mcp-fivetran"
      ],
      "env": {
        "FIVETRAN_AUTH_TOKEN": "YOUR_TOKEN"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
andrewkkchan
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago