Developer · Local MCP server
MCP Graphql Bridge
Bridges any GraphQL API to Claude Code - auto-generates MCP tools via schema introspection.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.murilojrpereira/mcp-graphql-bridge- Version
- 2.1.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-28
- Updated
- 2026-07-28
- Publisher
- murilojrpereira (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/murilojrpereira) · how
- Listed under
- GraphQL MCP servers
- Repository
- github.com/murilojrpereira/mcp-graphql-bridge
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | mcp-graphql-bridge | 2.1.0 | stdio |
How to connect MCP Graphql Bridge
MCP Graphql Bridge runs locally from a Node.js package published to the npm registry: mcp-graphql-bridge version 2.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y mcp-graphql-bridge@2.1.0. It reads these environment variables: GRAPHQL_API_URL, GRAPHQL_INTROSPECTION_URL, GRAPHQL_TOKEN (secret), GRAPHQL_INTROSPECTION_TOKEN (secret), GRAPHQL_MAX_TOOLS, GRAPHQL_INCLUDE_MUTATIONS and GRAPHQL_MAX_RETRIES; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-graphql-bridge": {
"command": "npx",
"args": [
"-y",
"mcp-graphql-bridge@2.1.0"
],
"env": {
"GRAPHQL_API_URL": "<value>",
"GRAPHQL_INTROSPECTION_URL": "<value>",
"GRAPHQL_TOKEN": "<secret>",
"GRAPHQL_INTROSPECTION_TOKEN": "<secret>",
"GRAPHQL_MAX_TOOLS": "<value>",
"GRAPHQL_INCLUDE_MUTATIONS": "<value>",
"GRAPHQL_MAX_RETRIES": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| MCP GitlabSecure MCP server for GitLab projects, merge requests, issues, and pipelines. | Local · stdio |
| MCP GitlabGitLab MCP server for MCP 2026-07-28: projects, MRs, pipelines, CI/CD, approvals, issues. | Local · stdio |
| MCP GrafanaSearch & edit Grafana dashboards, query datasources (PromQL/LogQL/SQL), inspect alerts. | Local · stdio |
| MCP GrantiqSearch US grants + federal contracts (Grants.gov + SAM.gov) from any LLM. | Remote · HTTPLive check: ✓ handshake |
| MCP Graphql EnhancedGraphQL gateway for LLMs. Handles huge GitHub GraphQL & @neo4j/graphql schemas without crashing. | Local · stdio |
| MCP Gtags ServerIndexed C/C++ code navigation for AI agents - GNU Global (gtags) lookups over MCP, not grep scans. | Local · stdio |
| MCP GuardianSecurity, cost, and health governance proxy for MCP infrastructure. | Local · stdio |
| MCP Health MonitorMonitor MCP server health, uptime, response times, and Azure DevOps pipeline status. | Local · stdio |