MCP.Market

Graphql Bridge MCP server

by murilojrpereira·io.github.murilojrpereira/mcp-graphql-bridge·v2.1.0·1 stars
No reviews yet

Bridges any GraphQL API to Claude Code — auto-generates MCP tools via schema introspection.

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

1 stars32 downloads/wk

Reviews

Write one

Nobody has reviewed Graphql Bridge yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Graphql Bridge tools (2, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • execute_graphqlwrite action

    Execute any GraphQL query or mutation against the API. Use this when no specific tool exists for your operation.

  • get_type_details

    Get fields of a specific GraphQL type to know what to put in __fields

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan18 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 5 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Graphql Bridge compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Tools
2
the typical server has 7
Tools that change things
50%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
32
more than 20% of 12,191 servers with a package

What its tools let an agent do: 1 read · 1 run or deploy

Install Graphql Bridge in Claude Code, Cursor or VS Code

Runs npx -y mcp-graphql-bridge on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-graphql-bridge -- npx -y mcp-graphql-bridge
Add to Cursor

What the publisher says

From the Graphql Bridge repository's README, as published. We do not edit it. Read it on GitHub

mcp-graphql-bridge

A generic MCP (Model Context Protocol) server that bridges any GraphQL API to Claude Code. It introspects your GraphQL schema and exposes each query and mutation as an individual tool, letting Claude interact with your API directly.

How it works

On startup the server will:

  1. Look for a schema-introspection.json file in the working directory (fast, no network call)
  2. If not found, run live introspection against GRAPHQLINTROSPECTIONURL
  3. Register one tool per query (query) and one per mutation (mutation)
  4. Always register a generic executegraphql fallback tool and a gettype_details explorer tool

Requirements

  • Node.js >= 20

Setup

Step 1: Install

Option A: Install from npm (recommended)

npm install -g mcp-graphql-bridge

Option B: Clone and build from source

git clone https://github.com/murilojrpereira/mcp-graphql-bridge.git
cd mcp-graphql-bridge
npm install
npm run build

Step 2: Configure environment variables

For schemas with hundreds of fields (GitHub's GraphQL API has 284 root fields — 32 queries, 252 mutations), GRAPHQLMAXTOOLS and GRAPHQLINCLUDEMUTATIONS are what keep registration bounded and predictable. If the cap truncates the schema, stderr logs exactly how many queries/mutations were registered vs. available.

No configuration is required to try the server — with nothing set, it starts against the public demo API above and logs that it's doing so. See docs/architecture.md for the full token model and why the GraphQL endpoint is fixed per deployment rather than a per-request parameter.

You can set these in a .env file at the project root:

GRAPHQL_API_URL=https://your-api.example.com/graphql
GRAPHQL_INTROSPECTION_URL=https://your-api.example.com/graphql
GRAPHQL_TOKEN=your-bearer-token

Or pass them directly via the claude mcp add command (see below).

Step 3: (Optional) Pre-generate schema snapshot

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Graphql Bridge: common questions

Is Graphql Bridge MCP server safe?
Mostly: it is graded B (83/100). Read the Graphql Bridge safety report
How do I install Graphql Bridge?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Graphql Bridge need an API key?
Yes. The registry entry asks for GRAPHQL_TOKEN, GRAPHQL_INTROSPECTION_TOKEN.
Is Graphql Bridge maintained?
The last commit was 45 days ago (2026-09-19). The latest release is v2.1.0.
How does Graphql Bridge compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 50% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.