Log inSubmit server
MCP Openapi Schema Explorer logo

MCP Openapi Schema Explorer

by kadykov

Explore local or remote OpenAPI and Swagger specifications through token-efficient MCP resource templates.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Openapi Schema Explorer

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "kadykov-mcp-openapi-schema-explorer": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-openapi-schema-explorer@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y mcp-openapi-schema-explorer@latest

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 25d ago.

Overview

The kadykov/mcp-openapi-schema-explorer MCP server exposes OpenAPI and Swagger specifications through parameterized MCP Resource Templates. It loads a specification from a local file or HTTP/HTTPS URL, converts Swagger 2.0 to OpenAPI 3.0, and serves selected parts on demand. Use it when an MCP client needs to inspect a large API definition without placing the entire document in the model context. The server provides read-only resources rather than executable tools.

Use cases

  • Inspect a large OpenAPI definition without loading the full file
  • Explore API paths and methods from an MCP client
  • Load a remote Swagger specification for schema review
  • Convert Swagger 2.0 input to OpenAPI 3.0 during exploration

Key features

  • Supports OpenAPI 3.0 specifications
  • Supports Swagger 2.0 specifications
  • Loads local files and HTTP/HTTPS URLs
  • Exposes parameterized MCP Resource Templates
  • Offers JSON, YAML, and minified JSON output
  • Uses read-only, on-demand specification access

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

20/20 checks healthy over the last 77d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · mcp-openapi-schema-explorer@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars76Stargazers on the source repository.
npm downloads665Package downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Openapi Schema Explorer works

What kadykov/mcp-openapi-schema-explorer MCP server does

The kadykov/mcp-openapi-schema-explorer MCP server lets MCP clients inspect OpenAPI 3.0 and Swagger 2.0 specifications without loading a complete document into the model context. It accepts either a local file path or a remote HTTP/HTTPS URL. When a Swagger 2.0 document is loaded, the server converts it to OpenAPI 3.0 before exposing its contents.

The project belongs in the 💻 Developer Tools category and is intended for read-only exploration. It does not execute API operations or mutate the source specification. Instead, clients request portions of the loaded definition through MCP Resource Templates.

How it works

Rather than publishing every possible resource in a large API definition, kadykov/mcp-openapi-schema-explorer MCP server publishes parameterized URI patterns. An MCP client discovers these patterns through the resources/templates/list protocol method and supplies values when it needs a particular part of the specification. The README gives openapi://paths/{path}/{method} as an example of this access style.

This design avoids pre-enumerating potentially thousands of API paths and lets a client retrieve structured details on demand. The server is designed to run as an MCP process launched by a client, with the specification location supplied as a command-line argument.

Setup and configuration

The kadykov/mcp-openapi-schema-explorer MCP server can be started with npx, Docker, a globally installed npm package, or a locally built checkout. The recommended client configuration uses npx with mcp-openapi-schema-explorer@latest; Docker users can run the published kadykov/mcp-openapi-schema-explorer image. A local setup can be built with npm after cloning the repository.

Configuration requires a specification path or URL. Local files should be supplied with an absolute path. When Docker reads a local file, the file must be mounted into the container and the container path passed to the server. Multiple specifications can be configured as separate MCP server entries.

The optional --output-format argument accepts json, yaml, or json-minified, with JSON as the default.

Tools and capabilities

  • Load OpenAPI specifications from local paths.
  • Load specifications from HTTP or HTTPS URLs.
  • Convert Swagger 2.0 documents to OpenAPI 3.0.
  • Expose parameterized MCP Resource Templates for on-demand inspection.
  • Explore specification data without preloading the entire document.
  • Return resource output as JSON, YAML, or minified JSON.

The interface is based on resources, not conventional MCP tools. This distinction matters for clients that display or discover tools separately from resource templates.

Limitations and notes

kadykov/mcp-openapi-schema-explorer MCP server is focused on specification discovery and does not provide operations for calling the described API. Its access model is read-only, and clients must support MCP Resource Templates to use the parameterized resources as intended. The documented client examples include Claude Desktop, Cline, Windsurf, and Claude Code. The source specification must be available as a local file or reachable through HTTP or HTTPS.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Openapi Schema Explorer

kadykov/mcp-openapi-schema-explorer is an MCP server that connects MCP clients to local files or HTTP/HTTPS URLs containing OpenAPI or Swagger specifications. Its main capabilities are parameterized MCP Resource Templates for read-only exploration, Swagger 2.0 conversion to OpenAPI 3.0, and selectable JSON or YAML output.

Install it by configuring an MCP client to run it with npx, Docker, a global npm installation, or a locally built checkout. The recommended npx configuration downloads the package automatically; Docker users can run the published image.

Pass the specification's absolute local path or full HTTP/HTTPS URL as the server command-line argument. For a local file in Docker, mount the host file into the container and pass the mounted container path.

Yes, Claude Desktop is listed as a supported MCP client example. Add a server entry to its MCP configuration and provide the specification path or URL as the configured command argument.

No, it only provides read-only access to specification data through MCP Resource Templates. It does not execute the API operations described by the OpenAPI or Swagger document.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Openapi Schema Explorer AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/kadykov-mcp-openapi-schema-explorer?style=directory)](https://allmcps.com/mcp/kadykov-mcp-openapi-schema-explorer)
HTML Embed
<a href="https://allmcps.com/mcp/kadykov-mcp-openapi-schema-explorer"><img src="https://allmcps.com/api/badge/kadykov-mcp-openapi-schema-explorer?style=directory" alt="MCP Openapi Schema Explorer on AllMCPs" /></a>