Skip to main content
Glama
Sign In
mcp-graphql-enhanced

mcp-graphql-enhanced

by letoribo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to mcp-graphql-enhanced

Related Servers

  • mcp4gql

    jorgeraad
    A
    license
    A
    quality
    D
    maintenance
    GraphQL MCP Server that acts as a bridge allowing MCP clients (like Cursor or Claude Desktop) to interact with target GraphQL APIs through standard tools for schema introspection and operation execution.
    2
    8 npm
    3
    MIT

  • graphql-mcp

    simoncrypta
    A
    license
    Not graded
    quality
    D
    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.
    16 npm
    MIT

  • mcp-graphql-schema

    hannesj
    A
    license
    Not graded
    quality
    D
    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
    33 npm
    46
    MIT

  • mcp-graphql-forge

    toolprint
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP that can proxy any GraphQL API and expose graphql operations as mcp tools.
    35 npm
    18
    Apache 2.0
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 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: introspect-schema is read-only metadata discovery, while query-graphql executes queries and mutations. The descriptions explicitly contrast their roles and even recommend using one before the other.

Naming Consistency5/5

Both names use a consistent kebab-case verb-noun pattern (introspect-schema, query-graphql). The convention is predictable and easy to parse.

Tool Count3/5

Two tools is thin for a GraphQL server, even an enhanced one. The surface is minimal but arguably sufficient for introspection plus execution, though it feels under-scoped for broader GraphQL workflows.

Completeness4/5

The pair covers the core GraphQL lifecycle: schema discovery and operation execution, including mutations. Minor gaps exist, such as dedicated subscription support or validation utilities, but agents can work around them.

Maintenance

ActivityActive
ResponsivenessLimited data

Resources