MCP Server

GraphQL MCP server for AI assistants

Local serverstdio

What is the MCP MCP server?

MCP MCP server exists for a simple reason — assistants are far more useful when they can act on MCP directly instead of describing what you should do. GraphQL MCP server for AI assistants.

What you get

A Model Context Protocol (MCP) server implementation that provides GraphQL API interaction capabilities. This server enables AI assistants to interact with GraphQL APIs through a set of standardized tools.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What the assistant can call

Once MCP is connected, these are the calls the assistant has available:

  • graphql_query — Execute GraphQL queries against any endpoint
  • Input — - query (string): The GraphQL query to execute
  • graphql_introspect — Retrieve and explore GraphQL schema information
  • Tools — The Tools tool exposed by this server

Configuration and credentials

You will need one environment variable: YOUR_GITHUB_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP's toolset — graphql_query, Input, graphql_introspect and 1 more — is a fair guide to whether it matches your workflow. It is maintained by saewoohan; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
graphql_queryExecute GraphQL queries against any endpoint
Input- query (string): The GraphQL query to execute
graphql_introspectRetrieve and explore GraphQL schema information
ToolsThe Tools tool exposed by this server.

How to install the MCP MCP server

{
  "mcpServers": {
    "graphql": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-graphql-tools",
        "--endpoint=https://api.github.com/graphql",
        "--headers={\"Authorization\":\"Bearer YOUR_GITHUB_TOKEN\"}",
        "--timeout=30000",
        "--maxComplexity=100"
      ]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
YOUR_GITHUB_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP to graphql query.
  • Use MCP to Input.
  • Use MCP to graphql introspect.

Frequently asked questions

It connects MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (graphql_query, Input, graphql_introspect, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP directly.