Skip to main content
Glama
tableau-graphql-mcp

tableau-graphql-mcp

by tdries

Related Servers

Alternatives to tableau-graphql-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to discover schemas, keys, and lineage across bronze, silver, and gold tables, and to run guarded read-only SQL queries against the lakehouse.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables agents to query governed metrics through MCP, including describing metrics, running deterministic SQL against a warehouse, explaining join path preferences, and searching semantically ambiguous terms.
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to ask bilingual data questions, inspect database tables and schemas, and execute validated read-only SQL through exposed tools.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Lets any MCP client query a Tableau Cloud knowledge graph in plain language — semantic search, node and edge lookup, lineage tracing, and impact analysis — plus reading and writing the business semantic contexts attached to it. Ships nine read tools and three guarded context-writing tools over stdio with PAT authentication.
      23
      186 PyPI
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only, guarded access to business databases via MCP. Enables natural language querying with built-in security barriers like table allowlists, PII masking, and audit logging.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides MCP tools to query Tableau Server/Cloud datasources via REST API and VizQL Data Service, with support for Gemini or OpenAI as the LLM backend. Enables a natural language chat interface that can be embedded in Tableau dashboards, automatically including dashboard filter context.
      -

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    The tools are mostly distinct: graphql_query is a general-purpose escape hatch, while where_used and impact_analysis are specialized lineage tools with clearly differentiated one-hop versus transitive semantics. Some overlap remains because graphql_query can answer nearly any lineage question, but the descriptions give clear selection guidance.

    Naming Consistency3/5

    All names use snake_case, which is readable and consistent at the casing level. However, the set mixes verb_noun names like introspect_schema and search_content with noun-phrase names like lineage_examples, impact_analysis, where_used, and server_info, so there is no predictable action-oriented pattern throughout.

    Tool Count5/5

    Seven tools is well-scoped for a read-only Tableau Metadata GraphQL server. The set provides a general query tool plus targeted helpers without excessive fragmentation.

    Completeness4/5

    The surface covers the important read-only metadata workflows: arbitrary GraphQL querying, schema introspection, examples, content search, direct usage lookup, transitive impact analysis, and environment info. Minor gaps are acceptable because graphql_query can handle less common shapes, though agents must compose those queries themselves.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data