Labsco
MCP SERVER

GraphQL Schema

by hannesj

Let the model explore a GraphQL schema — types, fields, arguments — instead of pasting the whole SDL into context.

API Specifications & HTTP Tooling
Summary
A large schema becomes something the model can look things up in.

Shopify-sized SDL does not fit in a context window, and pasting a fragment leaves the model inventing fields. Listing first and fetching one field at a time keeps the lookups small enough to stay accurate.

What it is

A server that loads one GraphQL schema file and exposes it as navigable structure. Queries, mutations and subscriptions can be listed or fetched one field at a time; types can be looked up whole or by their fields; and everything is searchable by pattern. Internal GraphQL types are filtered out.

What you get
  • Every query, mutation and subscription field, listed
  • One field at a time in detail, with its type and arguments
  • Every type in the schema, and any single type's definition
  • A type's fields on their own, when the full definition is more than you need
  • Pattern search across types and fields, for when you know part of a name
  • Internal GraphQL introspection types filtered out of results
Requirements

A GraphQL schema file — the server takes its path as a command line argument and defaults to schema.graphqls in the working directory. Runs through npx with no install and no key. It reads a file, so it never touches your live API.

Setup effort

One command — npx -y mcp-graphql-schema