GraphQL IDE for better development workflows (GraphQL Subscriptions, interactive docs & collaboration).
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).
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Graphql is connected, these are the calls the assistant has available:
Express — ** See [packages/graphql-playground-middleware-express/examples/basic](https://github.com/prismagraphql/graphql-playground/tree/main/packages/graphql-Hapi — ** See [packages/graphql-playground-middleware-hapi](https://github.com/prismagraphql/graphql-playground/tree/main/packages/graphql-playground-middlewKoa — ** See [packages/graphql-playground-middleware-koa](https://github.com/prismagraphql/graphql-playground/tree/main/packages/graphql-playground-middlewaImpact — The only reason this vulnerability exists is because we are using template strings in renderPlaygroundPage() with potentially unsanitized userProperties — The React component and all middlewares expose the following options:Usage — exports.graphqlHandler = function graphqlHandler(event, context, callback) { function callbackFilter(error, output) { // eslint-disable-next-lineVersions — The Versions tool exposed by this serverPackages — In the folder packages you'll find the following packages: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.
| Tool | What 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) |
| Impact | The 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 |
| Properties | The React component <Playground /> and all middlewares expose the following options: |
| Usage | exports.graphqlHandler = function graphqlHandler(event, context, callback) { function callbackFilter(error, output) { // eslint-disable-next-line no-param-reassign output.headers['Access-Control-Allow-Origin'] = '*' call |
| Versions | The Versions tool exposed by this server. |
| Packages | In the folder packages you'll find the following packages: |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.