# kadykov/mcp-openapi-schema-explorer [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/kadykov/mcp-openapi-schema-explorer  
**GitHub Stars:** 76  
**npm Downloads (last month):** 665  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/kadykov-mcp-openapi-schema-explorer

## Description
Token-efficient access to OpenAPI/Swagger specs via MCP Resources.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-openapi-schema-explorer": {
    "command": "npx",
    "args": ["-y","mcp-openapi-schema-explorer@latest"]
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/kadykov-mcp-openapi-schema-explorer/readme_