Allows executing any GraphQL query or mutation against any GraphQL API, supporting authentication, variables, and introspection.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@graphql-mcp run query { viewer { id name email } }"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server that exposes any GraphQL API as a single graphql tool. Works with Claude Code, Cursor, and any MCP client.
uv syncRelated MCP server: graphql-mcp-server
All configuration is via environment variables:
Variable | Required | Description |
| Yes | The GraphQL endpoint URL |
| Yes | API key or token for authentication |
| No | Header name for auth (default: |
| No | Request timeout in seconds (default: |
claude --mcp-config mcp.jsonWhere mcp.json contains:
{
"mcpServers": {
"graphql": {
"command": "uv",
"args": ["run", "--directory", "/path/to/graphql-mcp", "python", "main.py"],
"env": {
"GRAPHQL_API_URL": "https://api.example.com/graphql",
"GRAPHQL_API_KEY": "your-api-key"
}
}
}
}graphqlExecute any GraphQL query or mutation.
Parameters:
query (string, required) — A GraphQL query or mutation document
variables (object, optional) — GraphQL variables
Examples:
# Query
query { viewer { id name email } }
# Mutation with variables
mutation($id: String!, $body: String!) {
commentCreate(input: { issueId: $id, body: $body }) {
success
}
}
# Introspection
query { __type(name: "Mutation") { fields { name } } }Execute a GraphQL query or mutation.
Args: query: A GraphQL query or mutation document. variables: Optional GraphQL variables object.
Inputs: query (required), variables. Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clear: execute GraphQL queries or mutations.
The single tool name 'graphql' is not a verb_noun pattern, but there is no inconsistency to penalize. It is readable and directly reflects the tool's function.
One tool feels thin compared to a typical MCP server, but for a generic GraphQL executor, a single tool can be sufficient. It is slightly under the standard range but reasonable.
The tool can execute any GraphQL query or mutation, including introspection, covering the full domain of GraphQL operations. There are no obvious gaps for the server's stated purpose.
Query your OpsLevel internal developer portal: catalog, maturity data, and tech docs.
One gateway, every app: Gmail, GitHub, Notion and more. Connect once, call any tool. Managed auth.
Remote MCP for 1,500+ APIs. Vault-managed credentials; OAuth or API key. Search, load, and execute.
Run read-only GraphQL queries and list documents and media assets in Caisy.
