Skip to main content
Glama
fivetran

Fivetran MCP Server

Official
by fivetran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Fivetran MCP Server

No user-submitted related servers found.

    Related Servers

    • datadog-mcp

      Vicks9070
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query and manage Datadog observability data including metrics, logs, traces, and monitors through natural language. Supports read-only operations by default for security.
      MIT

    • uniquery

      yashdhingra0
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language querying of Postgres and MongoDB databases in read-only mode, with PII masking and row/timeout guardrails, from any MCP client.
      -

    • MCP Fivetran

      fastmcp-me
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Fivetran users and connections, including inviting users, listing connections, and triggering syncs.
      -

    • airbyte-mcp

      trustxai
      A
      license
      A
      quality
      C
      maintenance
      Enables interaction with an Airbyte instance through natural language, supporting workspaces, sources, destinations, connections, jobs, logs, tags, streams, and connector definitions.
      36
      5
      Apache 2.0

    • Salesforce MCP Server

      boejucci
      A
      license
      A
      quality
      D
      maintenance
      Enables natural language interactions with Salesforce data, metadata, and reports, including report creation, discovery, and schema inspection.
      21
      9 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 22 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources