Labsco
MCP SERVER

OpenAPI Schema Explorer

by kadykov ↗

Explore a large OpenAPI or Swagger spec through MCP resource templates — read paths, methods and components on demand, without loading the whole file into context.

API Specifications & HTTP Tooling
Summary
Read the spec a piece at a time.

The deliberate choice here is resources over tools: where other servers hand a model tools to call an API, this one exposes the specification for read-only exploration, so a client can walk a thousand-endpoint document by URI without ever loading it whole. The multi-value parameters — asking for several methods or components in one request — cut the round trips. One thing to know going in: it provides templates, so `resources/list` looks empty by design; the client discovers them through `resources/templates/list`.

What it is

An MCP server that exposes an OpenAPI v3.0 or Swagger v2.0 specification as parameterised resource templates rather than tools. A client fills in a template URI — a path, a method, a component name — and reads just that part, so a model can navigate a huge spec without the whole document entering its context window.

What you get
  • Top-level fields and listings reached through `openapi://{field}`, for `info`, `servers`, `tags`, and the contents of `paths` or `components`
  • The HTTP methods available on a path via `openapi://paths/{path}`, and the full operation detail via `openapi://paths/{path}/{method*}`, where `{method*}` accepts several comma-separated methods at once
  • Component names of a type listed with `openapi://components/{type}`, and full detail via `openapi://components/{type}/{name*}`
  • Swagger v2.0 specs loaded and converted to OpenAPI v3.0 automatically, from a local file or an HTTP/HTTPS URL
  • Output in JSON, YAML or minified JSON, chosen with `--output-format`
  • Internal `$ref`s rewritten into clickable MCP URIs, and dynamic completions for paths and component types drawn from the loaded spec
Requirements

No account and no key. The recommended path needs no install step — the client runs it with `npx -y mcp-openapi-schema-explorer@latest <path-or-url-to-spec>`, or via the Docker image `kadykov/mcp-openapi-schema-explorer`. It can also be installed globally with `npm install -g` or built from a clone. `--output-format` is optional and defaults to JSON. The package.json names it `mcp-openapi-schema-explorer` at 1.3.4. Because it serves resource templates, not pre-enumerated resources, a client that calls `resources/list` gets an empty list — templates are discovered through `resources/templates/list`.

Setup effort

One command — npm install -g mcp-openapi-schema-explorer