Summary
The schema is discovered, so you do not have to describe the API first.
Introspect, then query: the assistant learns the types on its own and writes against them rather than against your summary of them. Writes stay behind a launch flag, so read-only is the default state rather than something you set up.
What it is
An MCP server for GraphQL APIs. It introspects the endpoint you pass on --endpoint, or reads a local schema file, exposes that schema as a resource named graphql-schema, and executes queries against the service.
What you get
- The endpoint schema retrieved, by introspection or from a local .graphql file
- Queries executed against the endpoint, with results returned
- The schema also available to the client as a resource
- Custom headers passed at launch, so authenticated APIs work
- Mutations available only when the server is started with --enable-mutations
Requirements
Node with npx, and the endpoint URL — it falls back to a local GraphQL endpoint when you do not give one. Any authorization token goes in the headers option at launch, as a JSON string.
Setup effort
One command — npx -y @kailashg101/graphql-mcp-toolkit