en es ja ko zh

GraphQL MCP Server

Name: GraphQL MCP Server
Author: ctkadvisors

by ctkadvisors

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Servidor GraphQL MCP

Un servidor de Protocolo de contexto de modelo (MCP) de TypeScript fuertemente tipado que proporciona acceso sin inconvenientes a cualquier API GraphQL a través de Claude AI.

Características

Fuertemente tipado : creado con TypeScript para mejorar la calidad del código y la seguridad de tipos.
Integración dinámica de GraphQL : conéctese a cualquier API de GraphQL con generación automática de herramientas
Introspección de esquema : descubre y expone automáticamente todas las operaciones GraphQL como herramientas
Soporte completo para mutaciones : soporte de primera clase para mutaciones GraphQL con manejo adecuado
Lista blanca de consultas y mutaciones : lista blanca opcional para controlar qué operaciones de GraphQL están expuestas
Compatibilidad con tipos enriquecidos : maneja adecuadamente tipos GraphQL complejos, objetos de entrada y variables
Compatible con el estándar MCP : sigue el formato del Protocolo de contexto de modelo para una integración perfecta con Claude
Generación de consultas inteligentes : crea consultas GraphQL eficientes con la selección de campos adecuada
Compatibilidad con autenticación : autenticación de clave API simple

Related MCP server: Gemini MCP Server

Estructura del repositorio

graphql-mcp/
├── src/
│   └── graphql-mcp-server.ts     # Main server implementation (TypeScript)
├── dist/                         # Compiled JavaScript (generated)
├── docs/
│   ├── GETTING_STARTED.md         # Setup and usage guide
│   ├── PROJECT_STATUS.md          # Current project status
│   └── TECHNICAL.md               # Technical documentation
├── .env.development               # Environment variables
├── .env.sample                    # Sample environment template
├── claude_desktop_sample_config.json  # Sample Claude Desktop config
├── package.json                   # Project dependencies
├── tsconfig.json                  # TypeScript configuration
├── run-graphql-mcp.sh             # Script to run the server
└── README.md                      # This file

Prerrequisitos

Node.js 18 o posterior
TypeScript 5.x o posterior
Claude Desktop con soporte para MCP
Un punto final de API GraphQL (el valor predeterminado es la API de países si no se especifica)

Instalación

Opción 1: Desde npm

# Install globally
npm install -g graphql-mcp

# Run the server
graphql-mcp-server

Opción 2: Clonar repositorio

# Clone the repository
git clone https://github.com/ctkadvisors/graphql-mcp.git
cd graphql-mcp

# Install dependencies
npm install

# Run the server
npm start

Inicio rápido

1. Configurar variables de entorno

Copie el archivo env de muestra y actualícelo con los detalles de su API GraphQL:

cp .env.sample .env.development

Edite .env.development con su punto final de API GraphQL y su clave de API opcional.

2. Construir y ejecutar

Primero compila el código TypeScript:

npm install
npm run build

Luego ejecuta el servidor:

node dist/graphql-mcp-server.js

O utilice el script proporcionado que se compila y se ejecuta en un solo paso:

./run-graphql-mcp.sh

3. Integración de escritorio de Claude

Agregue este servidor a su configuración de Claude Desktop:

Utilice la configuración de muestra como plantilla:

cp claude_desktop_sample_config.json ~/Library/Application\ Support/Claude/claude_desktop_config.json

Edite la configuración y actualice la ruta para que apunte a su instalación:

{
  "mcpServers": {
    "graphql": {
      "command": "node",
      "args": ["/absolute/path/to/dist/graphql-mcp-server.js"],
      "env": {
        "GRAPHQL_API_ENDPOINT": "https://your-graphql-api.com/graphql",
        "GRAPHQL_API_KEY": "your-api-key-if-needed",
        "WHITELISTED_QUERIES": "[\"countries\",\"continent\",\"languages\"]"
      }
    }
  }
}

Reinicie Claude Desktop para conectarse al servidor

¡Ahora deberías ver las operaciones GraphQL como herramientas disponibles en Claude Desktop!

Operación Lista Blanca

Por razones de seguridad o rendimiento, puede que desee limitar las operaciones de GraphQL (consultas y mutaciones) expuestas a Claude. Existen dos enfoques para controlar el acceso:

Habilitar/Deshabilitar Mutaciones : Por seguridad, todas las mutaciones están deshabilitadas de forma predeterminada. Para habilitarlas:

"env": {
  "GRAPHQL_API_ENDPOINT": "https://example-graphql-api.com/graphql",
  "ENABLE_MUTATIONS": "true"
}

Lista blanca de operaciones : puede especificar qué operaciones específicas deben estar disponibles:

"env": {
  "GRAPHQL_API_ENDPOINT": "https://example-graphql-api.com/graphql",
  "ENABLE_MUTATIONS": "true",
  "WHITELISTED_QUERIES": "[\"countries\",\"continent\",\"languages\"]",
  "WHITELISTED_MUTATIONS": "[\"createUser\",\"updateProfile\"]"
}

Las listas blancas se pueden especificar en dos formatos:

Como una cadena de matriz JSON (mostrada arriba): "[\"query1\",\"query2\"]"
Como una lista separada por comas: "query1,query2,query3"

IMPORTANTE : Los valores de la lista blanca deben ser cadenas, no objetos de matriz JSON. Las variables de entorno siempre se pasan como cadenas, por lo que es necesario escapar correctamente las comillas en la cadena JSON, como se muestra arriba.

Ejemplo de formato correcto en la configuración de Claude Desktop :

"graphql-api": {
  "command": "node",
  "args": [
    "/Users/username/Projects/graphql-mcp/dist/graphql-mcp-server.js"
  ],
  "env": {
    "GRAPHQL_API_ENDPOINT": "https://example-graphql-api.com/graphql",
    "NODE_ENV": "development",
    "DEBUG": "true",
    "ENABLE_MUTATIONS": "true",
    "WHITELISTED_QUERIES": "[\"getUser\",\"getProducts\",\"getOrders\"]",
    "WHITELISTED_MUTATIONS": "[\"createOrder\",\"updateProfile\"]"
  }
}

Error común a evitar :

// INCORRECT - Will not work!
"WHITELISTED_QUERIES": ["getUser", "getProducts"],
"WHITELISTED_MUTATIONS": ["createOrder", "updateProfile"]

// CORRECT
"WHITELISTED_QUERIES": "[\"getUser\",\"getProducts\"]",
"WHITELISTED_MUTATIONS": "[\"createOrder\",\"updateProfile\"]"

Si no se proporciona una lista blanca para un tipo de operación en particular, todas las operaciones de ese tipo del esquema GraphQL estarán disponibles.

Ejemplo de uso

Consulta de datos

Una vez conectado a Claude Desktop, puedes usar comandos como:

View result from countries from graphql (local){}

O con parámetros:

View result from country from graphql (local){
  "code": "US"
}

Uso de mutaciones

Para las mutaciones, las herramientas tienen el prefijo mutation_ para distinguirlas de las consultas:

View result from mutation_createUser from graphql (local){
  "name": "John Doe",
  "email": "john.doe@example.com"
}

O una mutación más compleja:

View result from mutation_updateProduct from graphql (local){
  "id": "prod-123",
  "input": {
    "name": "Updated Product Name",
    "price": 29.99,
    "description": "This is an updated product description"
  }
}

Las mutaciones siguen el mismo patrón que las consultas, pero le permiten modificar datos en su API GraphQL.

Documentación

Para obtener información más detallada, consulte:

Desarrollo

Para realizar cambios en el servidor:

Modificar el código fuente de TypeScript en src/graphql-mcp-server.ts
Compilar el código TypeScript: npm run build
Ejecute el servidor compilado: node dist/graphql-mcp-server.js

Publicación en npm

Para publicar este paquete en npm:

# Make sure you're logged in to npm
npm login

# Build the project
npm run build

# Publish to npm
npm publish

El paquete incluirá los archivos JavaScript prediseñados en el directorio dist , lo que lo dejará listo para usar sin pasos de compilación adicionales.

Licencia

Este proyecto está licenciado bajo la Licencia Business Source 1.1 (BSL 1.1), que permite:

Uso no comercial : Puede utilizar este software para cualquier propósito no comercial.
Uso comercial interno : Puede utilizar este software para operaciones comerciales internas que no lo proporcionen a terceros como un servicio alojado o administrado.
Conversión de código abierto : el 14 de marzo de 2029, el código se convertirá automáticamente a la licencia MIT

El uso comercial, incluyendo la oferta de este software como servicio a terceros, requiere una licencia comercial de CTK Advisors. Para más información, contáctenos o consulte el archivo completo de la LICENCIA .

La licencia BSL está diseñada para equilibrar la disponibilidad de código abierto con el desarrollo comercial sustentable, brindando a todos acceso gratuito para fines no comerciales y al mismo tiempo protegiendo nuestra capacidad de respaldar y mejorar el software a largo plazo.

Available Tools

6 tools

continentD

GraphQL continent query

ParametersJSON Schema

Name	Required	Description	Default
`code`	Yes	code parameter (ID)

TDQS

D1.8/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it only states it's a 'GraphQL continent query', which doesn't reveal any behavioral traits such as whether it's read-only, requires authentication, has rate limits, or what the response format might be. This is inadequate for a tool with no annotation support.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single phrase 'GraphQL continent query', which is under-specified rather than concise. It lacks front-loaded information and doesn't earn its place by adding value; it's too brief to be helpful, failing to convey purpose or usage effectively.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a query with one parameter), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., continent details), how to interpret the 'code' parameter, or behavioral aspects. For a tool with minimal structured data, more descriptive context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, with the single parameter 'code' documented as 'code parameter (ID)'. The description adds no additional meaning beyond what the schema provides, such as explaining what the code represents (e.g., continent code like 'AF' for Africa) or format details. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'GraphQL continent query' restates the tool name 'continent' and the generic concept of a query, making it tautological. It doesn't specify what the query actually does (e.g., retrieve continent details by code), nor does it distinguish from sibling tools like 'continents' (plural) which might list all continents. The purpose is vague beyond being a GraphQL operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention when to use 'continent' (singular) versus 'continents' (plural), or how it relates to other sibling tools like 'countries' or 'languages'. There's no context or exclusions stated, leaving the agent with no usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

continentsC

GraphQL continents query

ParametersJSON Schema

Name	Required	Description	Default
`filter`	No	filter - Input type: ContinentFilterInput

TDQS

C2.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It only states this is a 'GraphQL continents query', implying a read-only operation, but doesn't disclose behavioral traits like what data is returned, error conditions, rate limits, or authentication needs. For a tool with no annotations, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient phrase with zero wasted words. It's appropriately sized for a simple query tool, though the brevity contributes to its lack of helpfulness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and a nested object parameter, the description is incomplete. It doesn't explain what the tool returns, how filtering works, or provide any context beyond the basic query nature. For a tool with potential complexity (nested filter), this is inadequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (the 'filter' parameter is documented as 'filter - Input type: ContinentFilterInput'), so the baseline is 3. The description adds no parameter semantics beyond what the schema provides, but doesn't contradict it either.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'GraphQL continents query' restates the tool name 'continents' and adds 'GraphQL query' which is tautological for a query tool. It doesn't specify what the tool actually does (e.g., 'Retrieve continent data with optional filtering'), nor does it distinguish from sibling tools like 'continent' (singular).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like 'continent' (singular) or 'countries'. The description provides no context about use cases, prerequisites, or exclusions, leaving the agent with no usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

countriesC

GraphQL countries query

ParametersJSON Schema

Name	Required	Description	Default
`filter`	No	filter - Input type: CountryFilterInput

TDQS

C2.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states it's a 'GraphQL countries query', which implies a read operation but doesn't clarify if it's safe, what data it returns, or any constraints like rate limits or authentication needs. For a query tool with zero annotation coverage, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise with 'GraphQL countries query', which is efficient and front-loaded. However, it's overly brief to the point of under-specification, lacking necessary details for clarity. It earns a high score for conciseness but loses points for not providing enough substance to be truly helpful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (1 parameter with nested object, no output schema, no annotations), the description is incomplete. It doesn't explain what the tool returns, how to use the filter, or differentiate from siblings. For a query tool with these contextual signals, more detail is needed to be considered adequately complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the schema documenting the 'filter' parameter as an object of type 'CountryFilterInput'. The description adds no additional meaning beyond this, such as examples of filter criteria or usage context. With high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting for parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'GraphQL countries query' restates the tool name 'countries' and adds only the generic term 'GraphQL query', which is tautological. It doesn't specify what the query actually does (e.g., retrieve, list, search countries) or distinguish it from sibling tools like 'country' (singular) or 'continent' tools. The purpose remains vague beyond being a GraphQL operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'country' (likely for a single country) or 'continents', nor does it provide any context for usage scenarios (e.g., filtering, listing all countries). The description lacks any indication of prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

countryC

GraphQL country query

ParametersJSON Schema

Name	Required	Description	Default
`code`	Yes	code parameter (ID)

TDQS

C2.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It mentions 'GraphQL' and 'query', implying a read-only operation, but doesn't disclose behavioral traits like error handling, rate limits, authentication needs, or what happens if the code is invalid. Minimal context beyond the basic operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise with two words, but it's under-specified rather than efficiently informative. It's front-loaded but lacks necessary detail, making it borderline between conciseness and insufficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and a single parameter with full schema coverage, the description is incomplete. It doesn't explain what the query returns, error conditions, or how it differs from sibling tools, leaving significant gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with one parameter 'code' documented as 'code parameter (ID)'. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'GraphQL country query' states the technology and resource but lacks a specific verb and doesn't distinguish from siblings like 'countries' or 'language'. It's vague about what the query actually does (fetch by code vs general query).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus siblings like 'countries' (plural) or 'language'. The description implies it's for querying countries via GraphQL, but doesn't specify use cases, prerequisites, or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

languageC

GraphQL language query

ParametersJSON Schema

Name	Required	Description	Default
`code`	Yes	code parameter (ID)

TDQS

C2.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure but provides minimal information. 'GraphQL language query' suggests a read operation but doesn't specify if it's safe, what permissions might be required, what format the response takes, or any rate limits. It doesn't disclose whether this queries language data or executes GraphQL operations, leaving significant behavioral uncertainty.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at just three words, which could be appropriate if it were more informative. However, the brevity comes at the cost of clarity - it's under-specified rather than efficiently informative. The structure is simple but doesn't effectively front-load the most critical information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no annotations, no output schema, and a minimal description, the contextual information is insufficient. For a tool with one required parameter that presumably returns language data (based on sibling tools), the description should explain what the tool returns, how it relates to the 'languages' sibling, and what the 'code' parameter represents beyond just being an ID.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% description coverage, with the single parameter 'code' documented as 'code parameter (ID)'. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in description, which applies here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'GraphQL language query' is tautological - it essentially restates the tool name 'language' with the addition of 'GraphQL query'. It doesn't specify what the tool actually does (e.g., retrieves language information, validates language codes, etc.) or what resource it operates on. While it mentions 'GraphQL', it doesn't clarify if this executes a GraphQL query or returns GraphQL schema information about languages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus its siblings (continent, continents, countries, country, languages). There's no indication of what differentiates this language tool from the 'languages' sibling tool, nor any context about appropriate use cases, prerequisites, or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

languagesC

GraphQL languages query

ParametersJSON Schema

Name	Required	Description	Default
`filter`	No	filter - Input type: LanguageFilterInput

TDQS

C2.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure but provides almost none. 'GraphQL languages query' implies a read operation but doesn't specify what data is returned, whether there are rate limits, authentication requirements, pagination behavior, or any other operational characteristics. The description adds minimal value beyond the implied query nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at just three words with zero wasted language. While it's under-specified, it's not verbose or poorly structured - it's front-loaded with the essential information that this is a GraphQL query for languages.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a tool with 1 parameter (including a nested object), no annotations, no output schema, and multiple sibling tools, the description is severely incomplete. It doesn't explain what the tool returns, how it differs from similar tools, what the filter parameter actually does, or provide any operational context needed for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (the single 'filter' parameter has a description), so the baseline is 3. The tool description doesn't add any meaningful information about parameters beyond what's already in the schema - it doesn't explain what LanguageFilterInput contains, what filtering capabilities exist, or provide examples of filter usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'GraphQL languages query' is a tautology that essentially restates the tool name 'languages' with the addition of 'GraphQL query' - it doesn't specify what the tool actually does beyond being a query. It doesn't distinguish this from sibling tools like 'language' (singular) or explain what 'languages' refers to in this context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is absolutely no guidance about when to use this tool versus alternatives. The description provides no context about when this query should be used instead of sibling tools like 'language', 'countries', or 'continents', nor does it mention any prerequisites or constraints for usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

6 tool updatesv1.0.0Aug 18, 2025
- First observedcontinent
- First observedcontinents
- First observedcountries
- First observedcountry
- First observedlanguage
- First observedlanguages

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.7/5.0

Scored 2026-04-18 11:10 across 6 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness3/5

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.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

Grafbase
com.grafbase.api
The Grafbase MCP server sits in front of a GraphQL API and exposes an MCP protocol-compliant interface that allows AI agents and LLMs to explore and query GraphQL APIs using natural language. It provides tools to search schemas, introspect types and fields, and execute GraphQL queries while minimizing context bloat by returning only relevant schema subsets, with built-in support for authentication, authorization, and configurable access control.
API Testing Search Developer Tools
2
mcp COAuth
com.wix
A Model Context Protocol server for Wix AI tools
Developer Tools Content Management Systems App Automation
215
hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
238
Apideck MCP A
dev.apideck.mcp
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Developer Tools
42

Related MCP Servers

MPC Tally API Server
Web3 & Decentralized Tech Databases
crazyrabbitLTC
A
license
Not graded
quality
D
maintenance
A server that allows AI agents to interact with the Tally API to access DAO governance data, proposals, and metadata using Model Context Protocol (MCP), built with TypeScript and GraphQL.
Updated 2 years ago (2025-02-06 22:33 UTC)
15 npm
7
MIT
Gemini MCP Server
Autonomous Agents Code Execution
georgejeffers
A
license
A
quality
D
maintenance
A TypeScript server that integrates Google's Gemini Pro model with Claude Desktop through the Model Context Protocol, allowing Claude users to access Gemini's text generation capabilities.
Updated 8 months ago (2026-02-22 01:53 UTC)
7
96 npm
12
MIT
mcp-graphql
Databases API Testing
launchthatbrand
A
license
Not graded
quality
D
maintenance
A Model Context Protocol server that enables LLMs to interact with GraphQL APIs by providing schema introspection and query execution capabilities.
Updated 2 years ago (2025-03-08 21:13 UTC)
758 npm
3
MIT
GraphQL MCP Toolkit
Databases Developer Tools API Testing
kailashGN
A
license
Not graded
quality
D
maintenance
A Model Context Protocol server that enables LLMs to interact with GraphQL APIs by providing schema introspection and query execution capabilities.
Updated a year ago (2025-04-21 04:57 UTC)
8 npm
MIT

Servidor GraphQL MCP

Características

Estructura del repositorio

Prerrequisitos

Instalación

Opción 1: Desde npm

Opción 2: Clonar repositorio

Inicio rápido

1. Configurar variables de entorno

2. Construir y ejecutar

3. Integración de escritorio de Claude

Operación Lista Blanca

Ejemplo de uso

Consulta de datos

Uso de mutaciones

Documentación

Desarrollo

Publicación en npm

Licencia

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches