GraphMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GRAPHMCP_MAX_DEPTH | No | Max query nesting depth (fragment-cycle safe). | 10 |
| GRAPHMCP_ALLOW_MUTATIONS | No | Set to '1' to enable graphql_mutate tool. | off |
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 |
|---|---|
| graphql_schemaA | Return the GraphQL schema (SDL). Call this before writing queries. |
| graphql_validateA | Validate a GraphQL query without executing it. Returns {"valid": bool, "errors": [...], "depth": int}. Use this to catch typos and invalid fields cheaply before calling graphql_query. |
| graphql_queryA | Execute a read-only GraphQL query and return {"data", "errors"}. Select only the fields you need. Example: with variables {"role": "ADMIN"}. Mutations are rejected here. |
| graphql_mutateA | Execute a GraphQL mutation (write operation). Only permitted when the server is started with GRAPHMCP_ALLOW_MUTATIONS=1. Example: |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema_resource | The GraphQL schema (SDL) served by this server. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: retrieving the schema, validating queries, executing read-only queries, and performing mutations. No overlap or ambiguity between them.
All tools share the 'graphql_' prefix and follow a predictable pattern, though 'schema' is a noun while the others are verbs. The minor inconsistency does not impede readability.
Four tools perfectly cover the core GraphQL workflow (introspect, validate, query, mutate) without unnecessary redundancy. The count is well-scoped for the server's purpose.
The tool surface is complete for a GraphQL client: schema access, validation, read and write operations. No obvious missing functionality for typical use cases.