Skip to main content
Glama
FabrWill

GraphQL MCP Server

by FabrWill
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to GraphQL MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-graphql

      launchthatbrand
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables LLMs to interact with GraphQL APIs by providing schema introspection and query execution capabilities.
      1,360 npm
      3
      MIT

    • Advanced Hasura GraphQL MCP

      husamabusafa
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to dynamically interact with Hasura GraphQL endpoints through natural language, supporting schema discovery, data querying/manipulation, and aggregations.
      9
      23
      -

    • graphql-mcp-bridge

      zcebupelka
      A
      license
      Not graded
      quality
      D
      maintenance
      This application connects GraphQL APIs with the Model Context Protocol (MCP). It allows you to integrate your GraphQL services with MCP-compatible AI systems effortlessly.
      2 npm
      1
      ISC

    • Unraid MCP

      lemanjo
      A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server that enables AI clients to inspect and manage an Unraid server via its GraphQL API, with read-only defaults and optional enabled mutations.
      88
      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

    C2.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have distinct primary purposes: inspect for server metadata, introspect for schema discovery, and query for executing operations. However, inspect and introspect could be slightly confused as both provide information about the server, though their specific focuses differ enough for agents to distinguish them with careful reading of descriptions.

    Naming Consistency5/5

    All tool names follow a consistent, simple verb-based pattern (inspect, introspect, query) without any mixing of conventions like camelCase or snake_case. The naming is straightforward and predictable across the set.

    Tool Count3/5

    With only 3 tools, this server feels minimal for a GraphQL domain, which typically involves operations like mutations and subscriptions beyond just queries. While it covers basic introspection and querying, the count is borderline thin for a full-featured GraphQL interface.

    Completeness2/5

    The tool set is significantly incomplete for GraphQL operations. It lacks mutation tools for data modification and subscription tools for real-time updates, which are core parts of the GraphQL specification. This gap will likely cause agent failures when trying to perform common GraphQL workflows beyond read-only queries.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources