Summary
Schema first, then anything — which is also the whole security model.
Introspection is what makes the second tool usable: without it a model guesses field names and gets back a syntax error it cannot diagnose. Worth knowing that executeGraphQLOperation runs mutations too, so whatever the token you configure is allowed to do is the actual boundary.
What it is
A bridge between an MCP client and one GraphQL API. It fetches the schema by introspection so the model can see what exists, then executes whatever operation you write against the same endpoint.
What you get
- introspectGraphQLSchema — the target API's schema as JSON, so operations are written against what is really there
- executeGraphQLOperation — any query or mutation, with variables and an operation name
- Nothing is specific to one API; it works against whichever endpoint you configure
Requirements
Node. The endpoint URL is required. A bearer token is optional and only needed if the API authenticates.
Setup effort
One command plus a key — npx -y mcp4gql, then supply credentials