Skip to main content
Glama

TheGraph MCP Server

An MCP server that powers AI agents with indexed blockchain data from The Graph.

GitHub License GitHub Last Commit Python Version

Available Tools

1. getSubgraphSchema

Fetches the schema of a specified subgraph, providing AI agents with the context needed to generate GraphQL queries.

Parameters:

  • subgraphId: The subgraph ID (e.g., "QmZBQcF...")

  • asText: Output format flag

    • true: Returns human-readable GraphQL schema

    • false: Returns JSON schema (default)

2. querySubgraph

Executes GraphQL queries against a specified subgraph. While queries are typically generated by AI, you can also manually craft your own.

Parameters:

  • subgraphId: The subgraph ID

  • query: GraphQL query string

Related MCP server: Subgraph Registry MCP

Installation

  1. Clone the Repository

    git clone https://github.com/kukapay/thegraph-mcp.git
  2. Client Configuration

    {
      "mcpServers": {
        "thegraph-mcp": {
          "command": "uv",
          "args": ["--directory", "path/to/thegraph-mcp", "run", "main.py"],
          "env": {
            "THEGRAPH_API_KEY": "your_api_key_here"
          }
        }
      }
    }

Example Prompts

Here are some natural language prompts to trigger the tools:

Schema Queries

  • "Show me the schema for subgraph QmZBQcF... in a readable format"

  • "What's the structure of the QmZBQcF... subgraph? Please display it in GraphQL format"

  • "I need to understand the data model of subgraph QmZBQcF..., can you fetch its schema?"

Data Queries

  • "Find the top 5 tokens by trading volume in the last 24 hours from subgraph QmZBQcF..."

  • "Show me all pairs with liquidity greater than 1 million USD in subgraph QmZBQcF..."

  • "Get the latest 10 swap events from the QmZBQcF... subgraph, including token symbols and amounts"

Analysis Tasks

  • "Analyze the trading volume of USDT pairs in the last week using subgraph QmZBQcF..."

  • "Compare the liquidity of ETH and USDC pairs in subgraph QmZBQcF..."

  • "Find unusual trading patterns in the last 24 hours from subgraph QmZBQcF..."

Combined Tasks

  • "First get the schema of QmZBQcF..., then help me write a query to find high-value transactions"

  • "Check the schema of QmZBQcF... and tell me what fields are available for querying token prices"

  • "Using subgraph QmZBQcF..., analyze the market impact of large trades by first understanding the schema and then querying relevant events"

License

This project is licensed under the MIT License. See the LICENSE file for details.

Available Tools

2 tools
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.

Inputs: subgraphId (required), asText.

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.

Inputs: subgraphId (required), query (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: getSubgraphSchema retrieves schema information via introspection, while querySubgraph executes actual GraphQL queries. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the need for metadata versus data retrieval.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (getSubgraphSchema, querySubgraph) using camelCase, which is predictable and readable. The naming convention is uniform across all tools, with no deviations or mixed styles.

    Tool Count2/5

    With only 2 tools, the server feels thin for interacting with The Graph protocol, which typically involves more operations like listing subgraphs, managing deployments, or handling subscriptions. This limited set may restrict agents from performing comprehensive tasks in the domain.

    Completeness2/5

    The tool surface is severely incomplete for a The Graph server, lacking essential operations such as listing available subgraphs, creating or updating subgraphs, and handling mutations or subscriptions. Agents will face dead ends when trying to perform basic lifecycle management or discover subgraphs beyond a known ID.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers