mcp-graphql-enhanced
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAME | No | Name of the MCP server | mcp-graphql-enhanced |
| SCHEMA | No | Path to a local GraphQL schema file or URL (optional) | |
| HEADERS | No | JSON string containing headers for requests | {} |
| ENDPOINT | No | GraphQL endpoint URL | http://localhost:4000/graphql |
| ALLOW_MUTATIONS | No | Enable mutation operations (disabled by default) | false |
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": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query-graphqlA | Execute GraphQL operations (queries and mutations) against the federated system. WARNING: This tool performs remote operations. 'Mutation' operations will modify persistent state; execute these only when a state change is intended. Prerequisites: Verify schema structure using 'introspect-schema' before executing complex queries. Security: Inherits environment-based authentication. Returns: A JSON object containing the execution result ('data') or a list of 'errors' in case of failure. |
| introspect-schemaA | Retrieve GraphQL schema details or system manifest. READ-ONLY: Non-destructive metadata discovery. Usage: 1. If 'typeNames' is provided: Returns the full SDL (Schema Definition Language) for the requested types, including fields and relations. 2. If 'typeNames' is omitted: Returns a Federated Manifest—a high-level summary of connected nodes, their capabilities, and available domain entities (not the full schema). Use this to navigate the federated graph topology before executing queries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| system-health | Check status of all nodes |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: introspect-schema is read-only metadata discovery, while query-graphql executes queries and mutations. The descriptions explicitly contrast their roles and even recommend using one before the other.
Both names use a consistent kebab-case verb-noun pattern (introspect-schema, query-graphql). The convention is predictable and easy to parse.
Two tools is thin for a GraphQL server, even an enhanced one. The surface is minimal but arguably sufficient for introspection plus execution, though it feels under-scoped for broader GraphQL workflows.
The pair covers the core GraphQL lifecycle: schema discovery and operation execution, including mutations. Minor gaps exist, such as dedicated subscription support or validation utilities, but agents can work around them.