Skip to main content
Glama
jorgeraad

mcp4gql

by jorgeraad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp4gql

No user-submitted related servers found.

    Related Servers

    • mcp-graphql-bridge

      murilojrpereira
      A
      license
      A
      quality
      A
      maintenance
      A generic MCP (Model Context Protocol) server that bridges any GraphQL API to Claude Code. It introspects your GraphQL schema and exposes each query and mutation as an individual tool, letting Claude interact with your API directly.
      2
      38 npm
      1
      MIT

    • mcp-graphql-schema

      hannesj
      A
      license
      Not graded
      quality
      F
      maintenance
      A MCP server that exposes GraphQL schema information to LLMs like Claude. This server allows an LLM to explore and understand large GraphQL schemas through a set of specialized tools, without needing to load the whole schema into the context
      23 npm
      46
      MIT

    • 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.
      889 npm
      3
      MIT

    • Apollo MCP Demo

      mabdullah679
      F
      license
      Not graded
      quality
      D
      maintenance
      This MCP server exposes approved GraphQL operations from an Apollo GraphQL API as AI-accessible tools. It sits between MCP clients and the GraphQL API, translating tool calls into GraphQL queries and returning results in MCP format.
      -

    • graphql-mcp

      simoncrypta
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes GraphQL operations as typed tools for AI models, with schema exploration, validation, execution, hot reload, OAuth, prompts, MCP Apps widgets, and OpenTelemetry support.
      11 npm
      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 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: introspectGraphQLSchema fetches the schema, while executeGraphQLOperation executes queries/mutations. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool.

    Naming Consistency4/5

    Both tools follow a verb_noun pattern (introspectGraphQLSchema, executeGraphQLOperation), but they use camelCase instead of snake_case. This is a minor deviation from a common convention, but the pattern is consistent and readable across the set.

    Tool Count2/5

    With only 2 tools, the server feels thin for a GraphQL client purpose. While the tools cover introspection and execution, typical GraphQL interactions might benefit from additional utilities like schema validation or query building, making this count borderline too few.

    Completeness3/5

    The tools cover core GraphQL operations (introspection and execution), but there are notable gaps. For example, there are no tools for schema exploration, query validation, or handling subscriptions, which could limit an agent's ability to fully interact with a GraphQL API.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources