executeGraphQLOperation
Executes an arbitrary GraphQL query or mutation against the target API. Use introspectGraphQLSchema first to understand the available operations.
LABSCO 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 — npx -y mcp4gql
USE CASES
01
Exploring an API you have not used before
Pull the schema by introspection and read what types and operations exist before writing anything.
02
Answering a question that needs a query you have not written
Read the schema, compose the query with variables, and run it in the same conversation.
03
Making a change through an API instead of its interface
Run the mutation directly, scoped by whatever the configured token is permitted to do.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
introspectGraphQLSchema
Fetches the schema of the target GraphQL API using introspection. Returns the schema in JSON format.
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected.
Requires
- npx on PATH
- GRAPHQL_ENDPOINT in your environment
Optional
AUTH_TOKEN in your environment
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y mcp4gqlMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"mcp4gql": {
"command": "npx",
"type": "stdio",
"args": [
"-y",
"mcp4gql"
],
"env": {
"GRAPHQL_ENDPOINT": "<YOUR_GRAPHQL_ENDPOINT>",
"AUTH_TOKEN": "<YOUR_AUTH_TOKEN>"
}
}
}
}Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mcp4gql": {
"command": "npx",
"args": [
"-y",
"mcp4gql"
],
"env": {
"GRAPHQL_ENDPOINT": "<YOUR_GRAPHQL_ENDPOINT>",
"AUTH_TOKEN": "<YOUR_AUTH_TOKEN>"
}
}
}
}
