thegraph-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THEGRAPH_API_KEY | Yes | Your API key from The Graph Studio |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getSubgraphSchemaA | Fetch the schema of a specified subgraph using GraphQL introspection. Args: subgraphId (str): The ID of the subgraph to query. asText (bool): If True, return schema as GraphQL text; otherwise, return JSON. Returns: str: Schema in JSON or GraphQL text format, or an error message. |
| querySubgraphA | Execute a GraphQL query against a specified subgraph. Args: subgraphId (str): The ID of the subgraph to query. query (str): The GraphQL query string to execute. Returns: str: Query result in JSON format, or an error message. |
| searchSubgraphsC | Search for subgraphs on The Graph Network by name or description. Args: searchQuery (str): The search term to find matching subgraphs. Returns: str: A concise list of matching subgraphs with their IDs, names, networks, and signal, or an error message. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: getSubgraphSchema retrieves schema metadata, querySubgraph executes queries, and searchSubgraphs finds subgraphs. There is no overlap in functionality, making tool selection unambiguous for an agent.
All tool names follow a consistent verb_noun pattern with camelCase styling (getSubgraphSchema, querySubgraph, searchSubgraphs). The naming is predictable and readable throughout the set.
With only 3 tools, the set feels thin for a GraphQL subgraph interaction server. While the core operations are covered, additional tools for mutations, subscriptions, or subgraph management could enhance completeness, placing it in the borderline range.
The tools cover essential read operations (schema fetching, querying, searching) well, but there are minor gaps such as lacking mutation support or subgraph lifecycle management (e.g., create/update/delete). Agents can work around these for basic querying tasks.