Log inSubmit server
MCP Openapi logo

MCP Openapi

by ReAPI-com

Loads local OpenAPI 3.x files into an MCP catalog for API discovery, schema lookup, code generation, and mock data.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Openapi

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": {
    "reapi-com-mcp-openapi": {
      "command": "npx",
      "args": [
        "-y",
        "@reapi/mcp-openapi@latest"
      ]
    }
  }
}

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

Automated check passed— started and listed 7 tools correctly (1mo ago).

Overview

ReAPI-com/mcp-openapi MCP server loads multiple local OpenAPI 3.x specifications and exposes their operations and schemas through MCP. It scans a configured directory, dereferences specifications, and maintains a searchable API catalog. LLM-powered IDEs can inspect endpoints, resolve schemas, generate code, and create mock request data from the available API definitions. Reach for it when development tools need structured context from one or more local OpenAPI files.

Use cases

  • Explore operations across multiple OpenAPI specifications
  • Inspect endpoint parameters and response schemas
  • Generate client code from API definitions
  • Create mock request payloads from schemas
  • Refresh catalog data after editing specifications

Key features

  • Loads multiple local OpenAPI 3.x files
  • Supports JSON and YAML specifications
  • Builds a catalog of operations and schemas
  • Dereferences schemas for complete context
  • Searches operations and schemas by specification
  • Loads operations and schemas by identifiers

Tools7

What MCP Openapi lets your agent do. Expand a tool for its parameters.

Verified live~393 tokens of context

Security & health

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

ActiveLast checked Today

Recent health check succeeded.

21/22 checks healthy over the last 84d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · @reapi/mcp-openapi@latest (npm)

Adoption & maintenance

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

GitHub stars90Stargazers on the source repository.
npm downloads156Package downloads in the last 30 days.
Last commit1y agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed7Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Openapi works

What ReAPI-com/mcp-openapi MCP server does

ReAPI-com/mcp-openapi MCP server connects LLM-powered development tools to local OpenAPI 3.x specifications. It reads JSON, YAML, and YML files from a directory, processes their references into dereferenced schemas, and builds a catalog containing specification metadata, operations, and schemas.

The catalog gives an AI assistant a structured way to explore an API before writing integration code. It can identify available endpoints, explain operation parameters and responses, inspect data models, generate API-aware code, and produce mock data or request payloads based on the definitions in the specifications. These capabilities place the project in the 💻 Developer Tools category.

How it works

At startup, the ReAPI-com/mcp-openapi MCP server scans the directory supplied through the command line. It processes each supported specification and creates an in-memory catalog. The refresh-api-catalog tool rescans the directory when files are added or changed.

MCP clients can retrieve the complete catalog or query it selectively. Searches can be limited to a specification ID, which is useful when several APIs contain similar paths, operation IDs, or schema names. A specification ID defaults to the source filename without its extension. An x-spec-id value in the OpenAPI info object can override that default and provide stable names for related specifications.

Setup and configuration

Run the package through npx and pass the directory containing the specifications with --dir. Cursor can load the server from either a project-level .cursor/mcp.json file or a global ~/.cursor/mcp.json file. A project-level configuration allows each project to expose a different group of specifications and helps keep catalog metadata within the model context limit.

The basic command uses npx -y @reapi/mcp-openapi@latest --dir ./specs. The target directory should contain OpenAPI 3.x files with .json, .yaml, or .yml extensions. After enabling the server in Cursor's MCP settings, use the refresh tool whenever the directory's specifications change.

Tools and capabilities

  • refresh-api-catalog rebuilds the catalog from the configured directory.
  • get-api-catalog returns metadata for all loaded specifications, operations, and schemas.
  • search-api-operations finds operations by query, optionally within one specification.
  • search-api-schemas finds schemas by query, optionally within one specification.
  • load-api-operation-by-operationId returns complete details for an operation ID and specification ID.
  • load-api-operation-by-path-and-method loads an operation using its specification ID, endpoint path, and HTTP method.
  • load-api-schema-by-schemaName returns a complete schema using its specification ID and schema name.

Limitations and notes

The documented input is a local directory of OpenAPI 3.x files; remote specification synchronization is listed as future work. Semantic search and MCP-exposed code templates are also roadmap items, so the current search tools are catalog searches rather than the planned natural-language or template features. Multiple specifications with overlapping resource names should use distinct x-spec-id values to avoid ambiguity.

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

ReAPI-com/mcp-openapi is an MCP server that connects LLM-powered development tools to local OpenAPI 3.x specifications. Its main tools refresh and retrieve an API catalog, search operations and schemas, and load complete operation or schema details by specification ID and resource identifier.

Install it by running it with npx and passing the specifications directory, such as `npx -y @reapi/mcp-openapi@latest --dir ./specs`. In Cursor, place this command in a project or global `.cursor/mcp.json` configuration, then enable the server in MCP settings.

Yes, ReAPI-com/mcp-openapi works with Cursor through its MCP configuration. Add the server to `.cursor/mcp.json` for a project-specific setup or `~/.cursor/mcp.json` for global availability, then enable it under Cursor Settings > Cursor Settings > MCP.

Place the OpenAPI files in the configured directory and assign distinct `x-spec-id` values when paths, operation IDs, or schema names overlap. The server uses filenames as IDs by default, while custom IDs let tools target the intended specification.

Related MCP servers

All in Developer Tools 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 AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/reapi-com-mcp-openapi?style=directory)](https://allmcps.com/mcp/reapi-com-mcp-openapi)
HTML Embed
<a href="https://allmcps.com/mcp/reapi-com-mcp-openapi"><img src="https://allmcps.com/api/badge/reapi-com-mcp-openapi?style=directory" alt="MCP Openapi on AllMCPs" /></a>