GraphQL gateway for LLMs. Handles huge GitHub GraphQL & @neo4j/graphql schemas without crashing
Connect MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. GraphQL gateway for LLMs. Handles huge GitHub GraphQL & @neo4j/graphql schemas without crashing. The mcp mcp server is what makes that connection.
An enhanced MCP (Model Context Protocol) server for GraphQL that fixes real-world interoperability issues between LLMs and GraphQL APIs. > Drop-in replacement for mcp-graphql — with dynamic headers, robust variables parsing, and zero breaking changes.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Arguments — **Note — ** Filtered introspection is only available when querying a live GraphQL endpointBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: ENDPOINT, HEADERS, ALLOW_MUTATIONS, YOUR_GITHUB_TOKEN, YOUR_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP's toolset — Arguments, Note — is a fair guide to whether it matches your workflow. It is maintained by letoribo; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Arguments | ** |
| Note | ** Filtered introspection is only available when querying a live GraphQL endpoint. |
{
"mcpServers": {
"graphql-enhanced": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"ENDPOINT": "your-value",
"HEADERS": "your-value",
"ALLOW_MUTATIONS": "your-value",
"YOUR_GITHUB_TOKEN": "your-value",
"YOUR_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ENDPOINT | Configuration value read at startup. | Optional |
| HEADERS | Configuration value read at startup. | Optional |
| ALLOW_MUTATIONS | Configuration value read at startup. | Optional |
| YOUR_GITHUB_TOKEN | Credential the server authenticates with. | Yes |
| YOUR_TOKEN | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.