Loading...

A Model Context Protocol server that enables LLMs to interact with GraphQL APIs, allowing for schema introspection and query execution.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
A Model Context Protocol server that enables LLMs to interact with GraphQL APIs, allowing for schema introspection and query execution.
This server is relatively safe in its default configuration with mutations disabled. Enabling mutations significantly increases the risk. Using a specific schema file instead of introspection reduces the attack surface.
Performance depends on the complexity of the GraphQL queries and the performance of the underlying GraphQL API. Introspection can be slow for large schemas.
Cost depends on the number of API calls made to the GraphQL endpoint and any associated data transfer costs.
npx -y @smithery/cli install mcp-graphql --client claude{
"mcpServers": {
"mcp-graphql": {
"command": "npx",
"args": ["mcp-graphql"],
"env": {
"ENDPOINT": "http://localhost:3000/graphql"
}
}
}
}ENDPOINTHEADERSALLOW_MUTATIONSSCHEMAintrospect-schemaRetrieves the GraphQL schema from the endpoint via introspection or a provided schema file.
Read-only operation that retrieves schema information.
query-graphqlExecutes GraphQL queries against the specified endpoint.
Can potentially modify data if mutations are enabled.
None
This server is relatively safe in its default configuration with mutations disabled. Enabling mutations significantly increases the risk. Using a specific schema file instead of introspection reduces the attack surface.
Autonomy depends on the configuration of ALLOW_MUTATIONS. If enabled, the agent can modify data. Exercise caution when granting full autonomy.
Production Tip
Monitor GraphQL API performance and implement rate limiting to prevent abuse.
The server will likely return an error, and the LLM will need to handle the failure gracefully.
Set the `ALLOW_MUTATIONS` environment variable to `true`.
Yes, you can set the `HEADERS` environment variable to include the necessary authentication headers.
Set the `SCHEMA` environment variable to the path or URL of your schema file.
No, rate limiting needs to be implemented at the GraphQL endpoint level.
It should support any GraphQL API that adheres to the GraphQL specification.
Check the logs of the GraphQL API and the MCP server for error messages.