mcp-openapi-schema-explorer

Name: mcp-openapi-schema-explorer
Rating: 2.3 (71 reviews)
Author: kadykov

by kadykov·★ 71·Score 46

An MCP server for token-efficient exploration of OpenAPI/Swagger specs via MCP Resource Templates.

developer-toolsai-llmapi

Forks

Open issues

this month

Last commit

2d ago

Indexed

Overview

The MCP OpenAPI Schema Explorer provides a way for MCP clients like Claude Desktop to access OpenAPI specifications without loading entire files into context windows. It uses MCP Resource Templates to expose parameterized access patterns for API documentation exploration. The server supports both OpenAPI v3.0 and Swagger v2.0 specifications, loading them from local file paths or remote HTTP/HTTPS URLs, with automatic conversion of v2.0 to v3.0 format.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Exploring large API documentation without context window limitations

you:Analyzing API endpoints and parameters programmatically

you:Generating client code or documentation snippets based on API specs

you:What's the difference between Resources and Tools in this server?

you:How do I access specific API endpoints?

When to choose this

Choose this when you need efficient token-based access to OpenAPI/Swagger specs in AI clients without loading entire specification files into context.

When NOT to choose this

Don't choose this if you need write access to API specifications or require direct API endpoint interaction rather than documentation exploration.

Comparable tools

openapi-mcpswagger-mcpapi-docs-mcppostman-mcp

Installation

For Claude Desktop, add the following to your config.json:

{
  "mcpServers": {
    "My API Spec (npx)": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-openapi-schema-explorer@latest",
        "<path-or-url-to-spec>",
        "--output-format",
        "yaml"
      ],
      "env": {}
    }
  }
}

Replace <path-or-url-to-spec> with your API specification file path or URL.

FAQ

What's the difference between Resources and Tools in this server?: This server provides Resource Templates for read-only exploration of API specs, rather than executable Tools. This is more token-efficient for large APIs as it doesn't require pre-enumerating all possible endpoints.
How do I access specific API endpoints?: Use the template patterns like `openapi://paths/{path}/{method}` with your MCP client. The client will call `resources/templates/list` first to discover available templates, then `resources/read` with specific parameters.

Compare mcp-openapi-schema-explorer with

mcp-openapi-schema-explorer vs ultimate_mcp_server mcp-openapi-schema-explorer vs mcp-server-chart mcp-openapi-schema-explorer vs everything mcp-openapi-schema-explorer vs filesystem mcp-openapi-schema-explorer vs time

GitHub →

Last updated 2026-05-17 · Auto-generated from public README + GitHub signals.