Graphql MCP Server

GraphQL IDE for better development workflows (GraphQL Subscriptions, interactive docs & collaboration).

Remote serverstreamable-http

What is the Graphql MCP server?

Graphql MCP server exists for a simple reason — assistants are far more useful when they can act on Graphql directly instead of describing what you should do. GraphQL IDE for better development workflows (GraphQL Subscriptions, interactive docs & collaboration).

What you get

  • ✨ Context-aware autocompletion & error highlighting
  • 📚 Interactive, multi-column docs (keyboard support)
  • ⚡️ Supports real-time GraphQL Subscriptions
  • ⚙ GraphQL Config support with multiple Projects & Endpoints
  • 🚥 Apollo Tracing support

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Graphql is connected, these are the calls the assistant has available:

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the graphql mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Graphql's toolset — Express, Hapi, Koa and 5 more — is a fair guide to whether it matches your workflow. It is maintained by apollo-bot; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Graphql's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
Express** See [packages/graphql-playground-middleware-express/examples/basic](https://github.com/prismagraphql/graphql-playground/tree/main/packages/graphql-playground-middleware-express/examples/basic)
Hapi** See [packages/graphql-playground-middleware-hapi](https://github.com/prismagraphql/graphql-playground/tree/main/packages/graphql-playground-middleware-hapi)
Koa** See [packages/graphql-playground-middleware-koa](https://github.com/prismagraphql/graphql-playground/tree/main/packages/graphql-playground-middleware-koa)
ImpactThe only reason this vulnerability exists is because we are using template strings in renderPlaygroundPage() with potentially unsanitized user defined variables. This allows an attacker to inject html and javascript into
PropertiesThe React component <Playground /> and all middlewares expose the following options:
Usageexports.graphqlHandler = function graphqlHandler(event, context, callback) { function callbackFilter(error, output) { // eslint-disable-next-line no-param-reassign output.headers['Access-Control-Allow-Origin'] = '*' call
VersionsThe Versions tool exposed by this server.
PackagesIn the folder packages you'll find the following packages:

Example prompts to try

  • Use Graphql to Express.
  • Use Graphql to Hapi.
  • Use Graphql to Koa.

Frequently asked questions

It connects Graphql to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (Express, Hapi, Koa, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Graphql directly.