Log inSubmit server
MCP Graphql Enhanced logo

MCP Graphql Enhanced

GraphQL MCP gateway with scoped introspection, dynamic endpoints, federated queries, and optional HTTP access.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Graphql Enhanced

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-graphql-enhanced": {
      "command": "npx",
      "args": [
        "-y",
        "@letoribo/mcp-graphql-enhanced"
      ],
      "env": {
        "ENDPOINT": "YOUR_VALUE_HERE",
        "ENABLE_HTTP": "YOUR_VALUE_HERE",
        "ALLOW_MUTATIONS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The mcp-graphql-enhanced MCP server connects MCP clients to GraphQL APIs, including large GitHub and Neo4j-based schemas. It provides tools for scoped schema introspection and GraphQL query execution, with runtime endpoint and header selection. Reach for it when full-schema introspection exceeds an agent’s context or when several GraphQL nodes must be queried through one MCP connection. STDIO and HTTP/JSON-RPC transports are supported, with mutations disabled by default.

Use cases

  • Inspect selected types from a large GraphQL schema
  • Query GitHub or Neo4j-backed GraphQL APIs
  • Aggregate results from multiple GraphQL endpoints
  • Switch GraphQL targets during an agent session
  • Test GraphQL operations through the GraphiQL interface

Key features

  • Scoped schema introspection
  • GraphQL query execution with variables
  • Dynamic endpoints and headers
  • Federated multi-node querying
  • STDIO and HTTP/JSON-RPC transport
  • Optional Cypher extraction

Tools2

What MCP Graphql Enhanced lets your agent do. Expand a tool for its parameters.

Self-reported~61 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

4/4 checks healthy over the last 21d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · @letoribo/mcp-graphql-enhanced (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars6Stargazers on the source repository.
npm downloads72kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed2Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Graphql Enhanced works

What mcp-graphql-enhanced does

The mcp-graphql-enhanced MCP server exposes GraphQL endpoints to AI agents through MCP. Its main use is making large or changing schemas easier to explore without returning the entire schema at once. The server is listed in the 💻 Developer Tools category and is suited to GraphQL APIs such as GitHub’s or systems built with @neo4j/graphql.

Two MCP tools are available:

  • introspect-schema retrieves the schema, or a selected portion of it.
  • query-graphql sends GraphQL queries to the configured endpoint.

Introspection can be narrowed with type names and recursive depth controls. This lets an agent inspect selected parts of a graph instead of producing a potentially oversized schema response. Query variables are handled as objects, addressing a common variables-parsing failure described by the project.

How it works

The mcp-graphql-enhanced MCP server can use one GraphQL URL or multiple comma-separated URLs. With multiple endpoints, it performs federated introspection, sends queries across the configured nodes, and combines returned objects with deep deduplication. Differences between matching type names on separate nodes are identified rather than silently treated as identical.

An endpoint can also be supplied to either MCP tool at request time. This allows a client to change GraphQL targets during an existing session without restarting the server. Headers such as authorization or API keys can likewise be passed through tool arguments. These options are useful when an agent must work with different environments or credentials during one connection.

For GraphQL implementations that include Cypher details in response extensions, the server detects and cleans the extensions.cypher value and adds the resulting Cypher block to the tool output. The upstream GraphQL service must provide that debug information for this behavior to work.

Setup and configuration

Configure the GraphQL target with ENDPOINT. A single URL preserves the ordinary single-node behavior; comma-separated URLs enable the federated mode. Set ENABLE_HTTP=true to expose the HTTP/JSON-RPC transport and the browser-based GraphiQL interface. The HTTP service uses port 6274, with GraphiQL available at /, /graphql, or /graphiql.

The server also supports standard STDIO communication for local MCP clients. GraphiQL receives headers configured for the server, allowing the same credentials to be used while testing queries in a browser. Set ALLOW_MUTATIONS=true only when mutation execution is intended; mutation operations are otherwise blocked.

Tools and capabilities

The mcp-graphql-enhanced MCP server supports:

  • Filtered introspection by selected type names.
  • Recursive introspection depth limits.
  • GraphQL queries with variables.
  • Runtime endpoint switching.
  • Runtime request headers.
  • Single-node and multi-node GraphQL operation.
  • Federated schema inspection and result aggregation.
  • Optional Cypher extraction from GraphQL response extensions.
  • STDIO and HTTP/JSON-RPC transports.
  • GraphiQL access when HTTP mode is enabled.

Limitations and notes

Scoped introspection reduces response size but does not make capacity unlimited; selecting too much schema can still exceed client or context limits. Federated behavior depends on the configured endpoints and may expose structural conflicts when nodes define the same type differently.

Mutations are disabled unless explicitly enabled with ALLOW_MUTATIONS. Cypher output depends on debug extensions from the upstream GraphQL server. The project describes compatibility with Claude Desktop, Gemini CLI, and standard MCP clients; other named platforms in the README are not represented by dedicated client identifiers in this listing.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Graphql Enhanced

mcp-graphql-enhanced is an MCP server that connects AI clients to GraphQL endpoints through schema introspection and query execution tools. It supports scoped introspection for large schemas, runtime endpoint and header changes, federated queries across multiple URLs, and optional HTTP/JSON-RPC access alongside STDIO.

It documents configuration through the GraphQL endpoint and support for STDIO or HTTP/JSON-RPC transports, so consult the repository for the exact installation procedure.

Use the introspect-schema tool with type-name and type-depth filters. These parameters restrict the returned schema to selected types and recursion depth, reducing unnecessary context and avoiding the all-at-once introspection behavior that can produce oversized results.

Set ALLOW_MUTATIONS to true before running the server. Mutations remain disabled by default, so explicitly enabling this setting is required for query-graphql to execute mutation operations.

Yes. The server supports STDIO for local client tools, and it can also expose HTTP/JSON-RPC when ENABLE_HTTP is enabled.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Graphql Enhanced AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-graphql-enhanced?style=directory)](https://allmcps.com/mcp/mcp-graphql-enhanced)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-graphql-enhanced"><img src="https://allmcps.com/api/badge/mcp-graphql-enhanced?style=directory" alt="MCP Graphql Enhanced on AllMCPs" /></a>