Labsco
MCP SERVER

GraphQL MCP

by blurrah

Give a model a GraphQL endpoint it has never seen: introspect the schema first, then run queries with variables against the same endpoint.

API Specifications & HTTP ToolingVerified
Summary
An unfamiliar API becomes queryable in two calls.

The order carries the value: introspect-schema first so the types and fields are known, then query-graphql with the document and its variables. There are no per-operation tools and no query builder — one call sends whatever you pass — so the schema is what constrains the model, and whatever guards the endpoint sits outside this server.

What it is

Two tools over one GraphQL endpoint — schema introspection, and query execution.

What you get
  • Full schema introspection, meant to run before the first query when the schema is not already loaded as a resource
  • Queries executed against the endpoint with their variables passed alongside
Requirements

A GraphQL endpoint the server can reach, and a Node runtime. The server itself takes no credentials.

Setup effort

One command — npx -y mcp-graphql