Skip to main content
Glama
friendlygeorge

GraphQL MCP Server

by friendlygeorge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to GraphQL MCP Server

No user-submitted related servers found.

    Related Servers

    • graphql-agent-toolkit

      mstuart
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to interact with any GraphQL API by introspecting the schema and exposing queries and mutations as MCP tools, with built-in pagination, semantic search, and framework adapters.
      14 npm
      MIT

    • mcp-graphql-bridge

      k-edge
      A
      license
      C
      quality
      B
      maintenance
      Enables Claude Code to interact with any GraphQL API by introspecting the schema and exposing queries and mutations as individual callable tools.
      8
      21 npm
      MIT

    • Advanced Hasura GraphQL MCP

      vikasversetest-debug
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with Hasura GraphQL endpoints to discover schema structures and execute queries or mutations. It provides specialized tools for table introspection, data previewing, and performing data aggregations through natural language.
      -
    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

    A4.4/5.0

    Scored across 22 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: connection management, authentication, schema introspection, typed execution, and raw execution. There is no overlap or ambiguity between any pair of tools.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern with underscores (e.g., connect_endpoint, list_queries, execute_typed_mutation). Minor variations like 'reload_schema' vs 'introspect_schema' are still consistent in style.

    Tool Count4/5

    At 22 tools, the set is on the higher side of reasonable for a comprehensive GraphQL client server. While each tool serves a justifiable purpose, the count exceeds the typical well-scoped range of 3-15, making it slightly heavy but not excessive.

    Completeness5/5

    The tool surface covers the full lifecycle: connection setup, authentication (token, basic, custom headers), schema introspection, exploration (list, describe, search), query/mutation execution (raw and typed), and cache management. Subscriptions are omitted with a valid explanation. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources