MCP OpenAPI Schema Explorer

Name: MCP OpenAPI Schema Explorer
Author: kadykov

@kadykov

关于 MCP OpenAPI Schema Explorer

MCP server providing token-efficient access to OpenAPI/Swagger specs via MCP Resource Templates for client-side exploration.

#nodejs #development #node #typescript #mcp #swagger #openapi #developer-tools #node-js #api-specification #model-context-protocol #mcp-server

基本信息

分类

其他

许可证

MIT

运行时

node

传输方式

stdio

发布者

kadykov

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "My API Spec (npx)": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-openapi-schema-explorer@latest",
        "https://petstore3.swagger.io/api/v3/openapi.json",
        "--output-format",
        "yaml"
      ],
      "env": {}
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is MCP OpenAPI Schema Explorer?

MCP OpenAPI Schema Explorer is an MCP (Model Context Protocol) server that provides token-efficient access to OpenAPI v3.0 and Swagger v2.0 specifications via MCP Resource Templates. It allows MCP clients like Cline or Claude Desktop to explore large API specifications without loading the entire file into an LLM’s context window.

How to use MCP OpenAPI Schema Explorer?

Add a configuration entry to your MCP client’s mcpServers settings, using either npx (recommended), Docker, a global npm install, or a local build. The server takes a path or URL to a specification and optional flags like --output-format. Multiple specifications can be added as separate server entries.

Key features of MCP OpenAPI Schema Explorer

Exposes OpenAPI specs via parameterized MCP resource templates (openapi://...).
Loads local files and remote HTTP/HTTPS URLs.
Converts Swagger v2.0 to OpenAPI v3.0 automatically.
Supports JSON, YAML, and minified JSON output formats.
Transforms internal $refs into clickable MCP URIs.
Server name in clients reflects the specification’s info.title.

Use cases of MCP OpenAPI Schema Explorer

Explore a 500+ endpoint API without blowing the LLM context window.
Let an AI agent dynamically discover and read specific path or component details.
Compare multiple API specifications by adding separate server entries.
Integrate with Claude Desktop, Cline, or Windsurf for interactive API understanding.

FAQ from MCP OpenAPI Schema Explorer

How does this server differ from tool-based OpenAPI servers?

This server uses MCP Resource Templates instead of tools, providing read-only, on-demand access to specific parts of the spec without pre-enumerating thousands of paths. This can be more token-efficient for LLM interactions.