A Model Context Protocol (MCP) server that allows LLMs to interact with Subgraphs available on The Graph Network.
Connect Subgraph MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol (MCP) server that allows LLMs to interact with Subgraphs available on The Graph Network. The subgraph mcp mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Requirements — The Requirements tool exposed by this serverConfiguration — Add the following to your configuration file of your client (e.g.,claude_desktop_config.json):Configuration is passed through the environment: AUTH_HEADER, GATEWAY_API_KEY, SUBGRAPH_REQUEST_TIMEOUT_SECONDS, YOUR_GATEWAY_API_KEY, METRICS_HOST. 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.
Because 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.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Subgraph MCP's toolset — Requirements, Configuration — is a fair guide to whether it matches your workflow. It is maintained by graphops; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Subgraph MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Requirements | The Requirements tool exposed by this server. |
| Configuration | Add the following to your configuration file of your client (e.g.,claude_desktop_config.json): |
{
"mcpServers": {
"subgraph-mcp": {
"command": "npx",
"args": [
"mcp-remote",
"--header",
"Authorization:${AUTH_HEADER}",
"https://subgraphs.mcp.thegraph.com/sse"
],
"env": {
"AUTH_HEADER": "Bearer YOUR_GATEWAY_API_KEY" // <-- Replace with your actual key
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AUTH_HEADER | Configuration value read at startup. | Optional |
| GATEWAY_API_KEY | Credential the server authenticates with. | Yes |
| SUBGRAPH_REQUEST_TIMEOUT_SECONDS | Configuration value read at startup. | Optional |
| YOUR_GATEWAY_API_KEY | Credential the server authenticates with. | Yes |
| METRICS_HOST | Endpoint or connection string the server talks to. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.