Log inSubmit server
MCP Graphql logo

MCP Graphql

by blurrah

Connects MCP clients to GraphQL endpoints for schema discovery and query execution, with mutations disabled by default.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Graphql

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": {
    "blurrah-mcp-graphql": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-graphql"
      ]
    }
  }
}

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

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y mcp-graphql

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The blurrah/mcp-graphql MCP server lets AI clients inspect a GraphQL schema and execute queries against a configured endpoint. It can obtain the schema through GraphQL introspection, a local file, or a URL, and exposes the result as an MCP resource. Configure the endpoint and optional request headers through environment variables; enable mutations separately when write operations are appropriate. Reach for it when an agent needs dynamic access to an existing GraphQL API rather than a narrowly scoped custom MCP server.

Use cases

  • Inspect a GraphQL schema before generating queries
  • Execute read-only GraphQL queries from an MCP client
  • Load a schema from a local file or URL
  • Send custom authorization headers to a GraphQL endpoint

Key features

  • GraphQL schema introspection
  • GraphQL query execution
  • Schema resource exposure
  • Custom request headers
  • Optional mutation support
  • Local or remote schema sources

Tools2

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

Self-reported~65 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.

9/9 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · mcp-graphql (npm)

Adoption & maintenance

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

GitHub stars407Stargazers on the source repository.
npm downloads8.2kPackage downloads in the last 30 days.
Last commit1y agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed2Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Graphql works

What blurrah/mcp-graphql does

The blurrah/mcp-graphql MCP server connects an MCP client to a GraphQL API. It provides schema discovery and query execution so a model can learn the available types and fields before constructing requests. The server is intended for generic GraphQL access rather than an API-specific set of fixed tools.

A graphql-schema resource is also exposed to clients. Its contents can come from a local schema file, a schema file available at a URL, or an introspection request sent to the configured GraphQL endpoint.

How it works

The blurrah/mcp-graphql MCP server uses the configured ENDPOINT value as the target for GraphQL requests. The introspect-schema tool retrieves the schema when the client does not already have it as a resource. The query-graphql tool then sends GraphQL queries to the same endpoint.

Request headers are supplied as a JSON string through HEADERS. A schema can be supplied independently with SCHEMA, using either a local path or a URL, instead of relying solely on endpoint introspection.

Setup and configuration

Run the package with the target endpoint supplied through environment variables. The endpoint defaults to http://localhost:4000/graphql, while headers default to an empty JSON object. NAME changes the MCP server name and defaults to mcp-graphql.

Relevant configuration includes:

  • ENDPOINT: GraphQL service URL.
  • HEADERS: JSON-encoded request headers.
  • SCHEMA: Local schema path or remote schema URL.
  • ALLOW_MUTATIONS: Set to true to permit mutation operations; it is false by default.
  • NAME: MCP server name.

For noninteractive execution, use the package runner with its confirmation flag.

Tools and capabilities

The blurrah/mcp-graphql MCP server exposes two tools:

  • introspect-schema obtains the GraphQL schema from the configured schema source or through an introspection query.
  • query-graphql executes GraphQL queries against the endpoint.

The schema is additionally available through the graphql-schema resource. This gives clients a way to read schema information without invoking the introspection tool when the resource is already available.

Limitations and notes

Mutations are blocked unless ALLOW_MUTATIONS=true is configured. This default reduces the risk of an agent changing data in the connected service, but enabling mutations should be evaluated carefully for production use.

The server offers broad GraphQL access rather than restricting clients to selected fields or operations. The README recommends creating a more specific MCP implementation when clients need tightly controlled queries or variables.

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

Run it with the npm package using npx, for example `npx -y mcp-graphql`. Configure `ENDPOINT` and any other environment variables required by your GraphQL service.

Yes. The README provides a Claude Desktop configuration using the `mcp-graphql` package and also documents installation through Smithery.

Set the `ENDPOINT` environment variable to the GraphQL URL. If it is omitted, the server uses `http://localhost:4000/graphql`.

Set `ALLOW_MUTATIONS=true`. Mutations are disabled by default.

Yes. Set `SCHEMA` to the local schema path. The variable can also point to a schema file hosted at a URL.

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 AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/blurrah-mcp-graphql?style=directory)](https://allmcps.com/mcp/blurrah-mcp-graphql)
HTML Embed
<a href="https://allmcps.com/mcp/blurrah-mcp-graphql"><img src="https://allmcps.com/api/badge/blurrah-mcp-graphql?style=directory" alt="MCP Graphql on AllMCPs" /></a>