CommunityAbandoned· 9mo★ 4.3by blurrah

MCP GraphQL

Lets agents discover and call GraphQL APIs with schema introspection and dynamic query execution.

View repo

Safety & Trust

Delv Safety Grade: C

Score 58/100 · assessed 2026-04-28

Maintainer40

Permissions65

Supply chain70

Transparency55

Incidents100

MCP GraphQL is a community server by solo developer blurrah that enables Claude to introspect and query arbitrary GraphQL endpoints. The tool is distributed via npm with a standard npx install, which is reasonably safe from a supply chain perspective. However, the maintainer appears to be a single individual with limited public profile, raising bus factor concerns. The permissions model is moderately scoped: it reads environment variables for the endpoint URL and makes outbound network requests to that endpoint, but doesn't write to filesystems or execute shell commands. The repository exists and appears functional, though documentation is minimal. The main risk is that you're pointing Claude at potentially sensitive GraphQL APIs with full query capabilities, and the tool's behaviour depends entirely on what endpoint you configure. No known security incidents, but limited community vetting given the solo maintainer and niche use case.

Lethal Trifecta (prompt-injection exposure)

ONE OF THREE

Private dataNo

Reads secrets, credentials, private files

Untrusted inputNo

Ingests web pages, PRs, issues, emails

External commsYes

Can send data outbound

Generic GraphQL caller. 1/3 unless you give it private endpoints (then 2/3).

Green flags

Standard npm distribution with npx install reduces supply chain risk
Read-only operations against external APIs, no filesystem writes
Schema introspection is a legitimate GraphQL feature, not a hack
No known security incidents or malicious behaviour
Scoped to single domain: GraphQL querying only

Red flags

Solo maintainer with limited public profile and unclear maintenance commitment
Minimal documentation and thin community review
Grants full query access to whatever GraphQL endpoint you configure
No apparent rate limiting or query complexity controls
Could expose sensitive API data if endpoint misconfigured

Permissions requested

Outbound networkRead env

Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

npx mcp-graphql

Env vars needed: ENDPOINT

Review

MCP GraphQL is a server that lets Claude introspect and query any GraphQL endpoint you point it at. You set an ENDPOINT environment variable, and Claude can then discover the schema, browse types, and build queries on the fly. It's the kind of thing that sounds niche until you're three hours into manually writing GraphQL queries against a headless CMS or some third-party API you barely understand. I'd reach for this when I'm working with a GraphQL API I don't know well. The schema introspection means Claude can tell you what fields exist, what arguments they take, and what types they return. It's faster than tab-completing through GraphQL Playground or reading stale docs. The server handles the HTTP layer, so you're not wrestling with headers or auth tokens in every query. For prototyping against something like Shopify's API or a custom backend, it's genuinely useful. The workflow is straightforward: you ask Claude to explore the schema, it lists the available queries and mutations, then you ask it to fetch specific data. Claude builds the query, executes it, and returns the result. If you're iterating on a query shape or trying to understand what data is actually available, this beats the usual copy-paste-refresh loop. Quirks: it's a single-endpoint tool. If you're working with multiple GraphQL APIs in one session, you'll need to restart the server with a different ENDPOINT value. There's no auth configuration shown in the repo, so if your endpoint needs OAuth or complex headers, you'll be adding that yourself. The repo is light on examples, so you'll spend a few minutes figuring out what Claude can actually do with it. It's also worth noting that this is a community server, not an official MCP, so expect rough edges. Who shouldn't bother: if you're only querying one or two known endpoints and you've already got Postman collections set up, this won't save you time. If you need to handle subscriptions or complex batching, this isn't built for that. But if you're exploring unfamiliar GraphQL APIs or prototyping queries, it's a solid addition to your MCP setup.

Verdict

Install this if you regularly work with GraphQL APIs you don't know inside out. It's faster than manual introspection and saves you from context-switching to external tools. Skip it if you're only hitting familiar endpoints or need advanced features like subscriptions.

Good at

Schema introspection means Claude can discover available queries and types without you reading docs.
Saves time when prototyping against unfamiliar APIs or headless CMS platforms.
Handles the HTTP layer so you're not manually crafting requests in every query.
Works well for exploratory work where you don't know what data is available upfront.

Watch out

Single-endpoint limitation means you can't switch between multiple GraphQL APIs in one session without restarting.
No built-in auth configuration, so OAuth or custom headers require manual setup.
Light documentation means you'll spend time figuring out what Claude can actually do with it.
Community-maintained, so expect slower updates and less polish than official MCPs.

Use cases

GraphQL exploration
API prototyping
schema-aware queries
headless CMS access

Getting started

1. Run `npx mcp-graphql` to install the server. 2. Add it to your Claude Desktop config under `mcpServers` with the key `mcp-graphql`, command `npx`, args `["mcp-graphql"]`, and an `env` object containing `ENDPOINT` set to your GraphQL URL. 3. Restart Claude Desktop and ask Claude to list available GraphQL queries to verify the connection. 4. Try asking Claude to fetch a specific piece of data, like "Get the first 5 products with their names and prices." 5. Watch out: if your endpoint requires authentication, you'll need to handle that outside this server or modify the setup.

Works with

Claude DesktopClaude CodeCursor