GraphQL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug mode | |
| NODE_ENV | No | Node environment (development, production, etc.) | |
| GRAPHQL_API_KEY | No | API key for the GraphQL API if needed | |
| ENABLE_MUTATIONS | No | Enable GraphQL mutations (disabled by default for security) | false |
| WHITELISTED_QUERIES | No | JSON array string or comma-separated list of allowed GraphQL queries | |
| GRAPHQL_API_ENDPOINT | Yes | URL of the GraphQL API endpoint | https://your-graphql-api.com/graphql |
| WHITELISTED_MUTATIONS | No | JSON array string or comma-separated list of allowed GraphQL mutations |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| continentD | GraphQL continent query |
| continentsC | GraphQL continents query |
| countriesC | GraphQL countries query |
| countryC | GraphQL country query |
| languageC | GraphQL language query |
| languagesC | GraphQL languages query |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose targeting a specific GraphQL query type (continent vs. continents, country vs. countries, language vs. languages), with no overlap or ambiguity in functionality. The singular/plural pairs are well-defined and intuitive for querying individual items versus lists.
All tool names follow a perfectly consistent pattern using singular and plural nouns (e.g., continent/continents, country/countries, language/languages) with no deviations in style or convention. This uniformity makes the set predictable and easy to navigate.
With 6 tools, the count is reasonable and well-scoped for a GraphQL server focused on geographic and linguistic data queries. It slightly leans toward being minimal but covers core query types effectively without feeling bloated or incomplete.
The tool set provides basic query capabilities for continents, countries, and languages, but lacks obvious operations like mutations (e.g., create, update, delete) or more advanced GraphQL features. While the query surface is coherent, it is limited to read-only operations, leaving gaps for full lifecycle management.