Openapi

Turn any OpenAPI/Swagger spec into MCP tools. Zero config, zero code.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "openapi": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-openapi"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

mcp-openapi

Turn any OpenAPI/Swagger spec into MCP tools — so Claude and other AI assistants can call your REST APIs.

Point mcp-openapi at any OpenAPI 3.x or Swagger 2.0 spec URL and it generates Model Context Protocol (MCP) tools automatically. No code generation, no config files, no boilerplate. Your AI assistant gets callable tools for every API endpoint in seconds.

Quick Start

1. Run it (no install required):

Terminal

npx mcp-openapi --spec https://petstore3.swagger.io/api/v3/openapi.json

2. Add it to Claude Desktop (claude_desktop_config.json):

config.json

{
  "mcpServers": {
    "petstore": {
      "command": "npx",
      "args": [
        "mcp-openapi",
        "--spec", "https://petstore3.swagger.io/api/v3/openapi.json"
      ]
    }
  }
}

3. Ask Claude to use it:

"List all available pets in the store"

Claude sees MCP tools like find_pets_by_status, get_pet_by_id, add_pet and calls them directly.

Why mcp-openapi?

Most MCP-to-API bridges require you to write tool definitions by hand or generate code from a spec. mcp-openapi skips all of that.

Feature	mcp-openapi	Hand-written MCP servers	Generic HTTP tools
Zero config setup	Yes	No	Partial
OpenAPI 3.x + Swagger 2.0	Yes	N/A	N/A
Flat parameter schemas (LLM-optimized)	Yes	Manual	No
Smart tool naming from operationId	Yes	Manual	No
Auth (API key, Bearer, OAuth2)	Built-in	DIY	DIY
Retry with exponential backoff	Built-in	DIY	DIY
Response truncation for LLM context	Built-in	DIY	No

Flat parameter schemas are the key differentiator. Instead of passing nested JSON objects (which LLMs frequently get wrong), mcp-openapi flattens path, query, header, and body parameters into a single flat object. This dramatically improves tool-calling accuracy.

How It Works

Code

OpenAPI/Swagger Spec          mcp-openapi               AI Assistant
     (URL or file)                                      (Claude, etc.)
          |                         |                         |
          |   1. Parse & validate   |                         |
          |------------------------>|                         |
          |                         |                         |
          |   2. Generate MCP tools |                         |
          |   (one per endpoint)    |                         |
          |------------------------>|                         |
          |                         |                         |
          |                         |   3. Register tools     |
          |                         |   via stdio transport   |
          |                         |------------------------>|
          |                         |                         |
          |                         |   4. AI calls a tool    |
          |                         |<------------------------|
          |                         |                         |
          |   5. Build & execute    |                         |
          |   HTTP request          |                         |
          |<------------------------|                         |
          |                         |                         |
          |   6. Return truncated   |                         |
          |   response to AI        |                         |
          |------------------------>|------------------------>|

Each API endpoint becomes one MCP tool:

Tool name is derived from operationId (converted to snake_case) or from method + path
Parameters are flattened into a single input schema (path, query, header, and body params merged)
Responses are truncated to ~50KB to stay within LLM context limits
Errors (429, 5xx) trigger automatic retries with exponential backoff (up to 3 retries)

Claude Desktop Integration

Add any API to Claude Desktop by editing your config file:

Location:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Public API (no auth)

config.json

{
  "mcpServers": {
    "petstore": {
      "command": "npx",
      "args": [
        "mcp-openapi",
        "--spec", "https://petstore3.swagger.io/api/v3/openapi.json"
      ]
    }
  }
}

API with Bearer Token

config.json

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": [
        "mcp-openapi",
        "--spec", "https://raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api.github.com.json",
        "--auth-type", "bearer",
        "--auth-token", "$GITHUB_TOKEN",
        "--prefix", "github",
        "--include", "listReposForAuthenticatedUser,getRepo,listIssues,createIssue"
      ],
      "env": {
        "GITHUB_TOKEN": "ghp_your_token_here"
      }
    }
  }
}

API with API Key

config.json

{
  "mcpServers": {
    "weather": {
      "command": "npx",
      "args": [
        "mcp-openapi",
        "--spec", "https://api.weather.example.com/openapi.json",
        "--auth-type", "api-key",
        "--auth-name", "X-API-Key",
        "--auth-value", "$WEATHER_API_KEY",
        "--auth-in", "header"
      ],
      "env": {
        "WEATHER_API_KEY": "your_key_here"
      }
    }
  }
}

CLI Reference

Terminal

npx mcp-openapi --spec <url-or-path> [options]

General Options

Option	Short	Default	Description
`--spec <url\|path>`	`-s`	required	OpenAPI spec URL or local file path
`--config <path>`	`-c`		JSON config file path
`--base-url <url>`		from spec	Override the API base URL
`--prefix <name>`			Prefix for all tool names (e.g. `github` -> `github_list_repos`)
`--include <patterns>`		all	Comma-separated operationIds to include
`--exclude <patterns>`		none	Comma-separated operationIds to exclude
`--timeout <ms>`		`30000`	HTTP request timeout in milliseconds
`--max-retries <n>`		`3`	Max retries on 429/5xx responses
`--header <name:value>`	`-H`		Custom header (repeatable)
`--transport <type>`		`stdio`	Transport type: `stdio` or `sse`
`--port <n>`		`3000`	Port for SSE transport
`--help`	`-h`		Show help
`--version`	`-v`		Show version
`--license-key <key>`			Pro license key (or `$MCP_OPENAPI_LICENSE_KEY` env)
`--server <selector>`		`0`	Select API server by index, partial URL, or exact URL
`--no-doc-warnings`			Suppress doc quality warnings on startup
`--dynamic-discovery`		auto (100+)	Enable dynamic tool discovery for large APIs

Auth Options

Bearer token:

Option	Description
`--auth-type bearer`	Use Bearer token authentication
`--auth-token <token>`	The token value (supports `$ENV_VAR` syntax)

API key:

Option	Description
`--auth-type api-key`	Use API key authentication
`--auth-name <name>`	Header or query parameter name
`--auth-value <value>`	The API key value (supports `$ENV_VAR` syntax)
`--auth-in <header\|query>`	Where to send the key (default: `header`)

OAuth2 client credentials:

Option	Description
`--auth-type oauth2`	Use OAuth2 client credentials flow
`--auth-client-id <id>`	OAuth2 client ID
`--auth-client-secret <secret>`	OAuth2 client secret
`--auth-token-url <url>`	Token endpoint URL
`--auth-scopes <scopes>`	Comma-separated scopes

CLI Examples

bash

# Basic usage with a remote spec
npx mcp-openapi --spec https://petstore3.swagger.io/api/v3/openapi.json

# Local YAML spec with Bearer auth
npx mcp-openapi --spec ./api.yaml --auth-type bearer --auth-token '$API_KEY'

# Filter to specific endpoints with a prefix
npx mcp-openapi --spec ./api.json --prefix myapi --include 'listUsers,getUser'

# Override base URL (useful for local dev)
npx mcp-openapi --spec https://api.example.com/openapi.json --base-url http://localhost:3000

# Add custom headers
npx mcp-openapi --spec ./api.json -H 'X-Custom: value' -H 'X-Another: value2'

# Use a JSON config file
npx mcp-openapi --config ./mcp-config.json

# Select staging server
npx mcp-openapi --spec ./api.json --server staging

# Large API with dynamic discovery
npx mcp-openapi --spec https://api.stripe.com/openapi.json --dynamic-discovery

Config File Format

Instead of CLI flags, you can use a JSON config file:

config.json

{
  "spec": "https://api.example.com/openapi.json",
  "prefix": "myapi",
  "include": ["listUsers", "getUser", "createUser"],
  "auth": {
    "type": "bearer",
    "token": "$API_TOKEN"
  },
  "timeout": 15000,
  "maxRetries": 2,
  "headers": {
    "X-Custom-Header": "value"
  }
}

CLI arguments take precedence over config file values.

Supported Specs

Format	Versions	File types
OpenAPI	3.0.x, 3.1.x	`.json`, `.yaml`, `.yml`
Swagger	2.0	`.json`, `.yaml`, `.yml`

Specs can be loaded from:

Remote URLs (https://...)
Local file paths (./api.yaml, /absolute/path/spec.json)

v0.3.0 Features

Doc Quality Warnings

On startup, mcp-openapi checks each tool's documentation quality. If endpoints have sparse descriptions (under 50 characters), you'll see a warning:

Read the full README →View source on GitHub →

Related MCP Servers

View all in Aggregators View all alternatives

Adoption & maintenance

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

GitHub stars

Stargazers on the source repository.

Last commit

5mo ago

Most recent push to the default branch.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

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

Frequently Asked Questions about Openapi

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "openapi": { "command": "npx", "args": ["-y","mcp-openapi"] } }

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 Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/openapi?style=directory)](https://allmcps.com/mcp/openapi)

HTML Embed

<a href="https://allmcps.com/mcp/openapi"><img src="https://allmcps.com/api/badge/openapi?style=directory" alt="Openapi on AllMCPs" /></a>

Technical Specs & Signals

CategoryAggregators

8/8 checks healthy over the last 32d

36Quality signal: Fair · 36/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools15/30

Adoption & activity2/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 24d ago via OSV.dev · mcp-openapi (npm)

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🔗 Aggregators →Alternatives to Openapi →Install in Claude Desktop Install in Cursor Install in VS Code

Openapi

Turn any OpenAPI/Swagger spec into MCP tools. Zero config, zero code.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "openapi": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-openapi"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

mcp-openapi

Turn any OpenAPI/Swagger spec into MCP tools — so Claude and other AI assistants can call your REST APIs.

Quick Start

1. Run it (no install required):

Terminal

npx mcp-openapi --spec https://petstore3.swagger.io/api/v3/openapi.json

2. Add it to Claude Desktop (claude_desktop_config.json):

config.json

{
  "mcpServers": {
    "petstore": {
      "command": "npx",
      "args": [
        "mcp-openapi",
        "--spec", "https://petstore3.swagger.io/api/v3/openapi.json"
      ]
    }
  }
}

3. Ask Claude to use it:

"List all available pets in the store"

Claude sees MCP tools like find_pets_by_status, get_pet_by_id, add_pet and calls them directly.

Why mcp-openapi?

Most MCP-to-API bridges require you to write tool definitions by hand or generate code from a spec. mcp-openapi skips all of that.

Feature	mcp-openapi	Hand-written MCP servers	Generic HTTP tools
Zero config setup	Yes	No	Partial
OpenAPI 3.x + Swagger 2.0	Yes	N/A	N/A
Flat parameter schemas (LLM-optimized)	Yes	Manual	No
Smart tool naming from operationId	Yes	Manual	No
Auth (API key, Bearer, OAuth2)	Built-in	DIY	DIY
Retry with exponential backoff	Built-in	DIY	DIY
Response truncation for LLM context	Built-in	DIY	No

How It Works

Code

OpenAPI/Swagger Spec          mcp-openapi               AI Assistant
     (URL or file)                                      (Claude, etc.)
          |                         |                         |
          |   1. Parse & validate   |                         |
          |------------------------>|                         |
          |                         |                         |
          |   2. Generate MCP tools |                         |
          |   (one per endpoint)    |                         |
          |------------------------>|                         |
          |                         |                         |
          |                         |   3. Register tools     |
          |                         |   via stdio transport   |
          |                         |------------------------>|
          |                         |                         |
          |                         |   4. AI calls a tool    |
          |                         |<------------------------|
          |                         |                         |
          |   5. Build & execute    |                         |
          |   HTTP request          |                         |
          |<------------------------|                         |
          |                         |                         |
          |   6. Return truncated   |                         |
          |   response to AI        |                         |
          |------------------------>|------------------------>|

Each API endpoint becomes one MCP tool:

Tool name is derived from operationId (converted to snake_case) or from method + path
Parameters are flattened into a single input schema (path, query, header, and body params merged)
Responses are truncated to ~50KB to stay within LLM context limits
Errors (429, 5xx) trigger automatic retries with exponential backoff (up to 3 retries)

Claude Desktop Integration

Add any API to Claude Desktop by editing your config file:

Location:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Public API (no auth)

config.json

{
  "mcpServers": {
    "petstore": {
      "command": "npx",
      "args": [
        "mcp-openapi",
        "--spec", "https://petstore3.swagger.io/api/v3/openapi.json"
      ]
    }
  }
}

API with Bearer Token

config.json

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": [
        "mcp-openapi",
        "--spec", "https://raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api.github.com.json",
        "--auth-type", "bearer",
        "--auth-token", "$GITHUB_TOKEN",
        "--prefix", "github",
        "--include", "listReposForAuthenticatedUser,getRepo,listIssues,createIssue"
      ],
      "env": {
        "GITHUB_TOKEN": "ghp_your_token_here"
      }
    }
  }
}

API with API Key

config.json

{
  "mcpServers": {
    "weather": {
      "command": "npx",
      "args": [
        "mcp-openapi",
        "--spec", "https://api.weather.example.com/openapi.json",
        "--auth-type", "api-key",
        "--auth-name", "X-API-Key",
        "--auth-value", "$WEATHER_API_KEY",
        "--auth-in", "header"
      ],
      "env": {
        "WEATHER_API_KEY": "your_key_here"
      }
    }
  }
}

CLI Reference

Terminal

npx mcp-openapi --spec <url-or-path> [options]

General Options

Option	Short	Default	Description
`--spec <url\|path>`	`-s`	required	OpenAPI spec URL or local file path
`--config <path>`	`-c`		JSON config file path
`--base-url <url>`		from spec	Override the API base URL
`--prefix <name>`			Prefix for all tool names (e.g. `github` -> `github_list_repos`)
`--include <patterns>`		all	Comma-separated operationIds to include
`--exclude <patterns>`		none	Comma-separated operationIds to exclude
`--timeout <ms>`		`30000`	HTTP request timeout in milliseconds
`--max-retries <n>`		`3`	Max retries on 429/5xx responses
`--header <name:value>`	`-H`		Custom header (repeatable)
`--transport <type>`		`stdio`	Transport type: `stdio` or `sse`
`--port <n>`		`3000`	Port for SSE transport
`--help`	`-h`		Show help
`--version`	`-v`		Show version
`--license-key <key>`			Pro license key (or `$MCP_OPENAPI_LICENSE_KEY` env)
`--server <selector>`		`0`	Select API server by index, partial URL, or exact URL
`--no-doc-warnings`			Suppress doc quality warnings on startup
`--dynamic-discovery`		auto (100+)	Enable dynamic tool discovery for large APIs

Auth Options

Bearer token:

Option	Description
`--auth-type bearer`	Use Bearer token authentication
`--auth-token <token>`	The token value (supports `$ENV_VAR` syntax)

API key:

Option	Description
`--auth-type api-key`	Use API key authentication
`--auth-name <name>`	Header or query parameter name
`--auth-value <value>`	The API key value (supports `$ENV_VAR` syntax)
`--auth-in <header\|query>`	Where to send the key (default: `header`)

OAuth2 client credentials:

Option	Description
`--auth-type oauth2`	Use OAuth2 client credentials flow
`--auth-client-id <id>`	OAuth2 client ID
`--auth-client-secret <secret>`	OAuth2 client secret
`--auth-token-url <url>`	Token endpoint URL
`--auth-scopes <scopes>`	Comma-separated scopes

CLI Examples

bash

# Basic usage with a remote spec
npx mcp-openapi --spec https://petstore3.swagger.io/api/v3/openapi.json

# Local YAML spec with Bearer auth
npx mcp-openapi --spec ./api.yaml --auth-type bearer --auth-token '$API_KEY'

# Filter to specific endpoints with a prefix
npx mcp-openapi --spec ./api.json --prefix myapi --include 'listUsers,getUser'

# Override base URL (useful for local dev)
npx mcp-openapi --spec https://api.example.com/openapi.json --base-url http://localhost:3000

# Add custom headers
npx mcp-openapi --spec ./api.json -H 'X-Custom: value' -H 'X-Another: value2'

# Use a JSON config file
npx mcp-openapi --config ./mcp-config.json

# Select staging server
npx mcp-openapi --spec ./api.json --server staging

# Large API with dynamic discovery
npx mcp-openapi --spec https://api.stripe.com/openapi.json --dynamic-discovery

Config File Format

Instead of CLI flags, you can use a JSON config file:

config.json

{
  "spec": "https://api.example.com/openapi.json",
  "prefix": "myapi",
  "include": ["listUsers", "getUser", "createUser"],
  "auth": {
    "type": "bearer",
    "token": "$API_TOKEN"
  },
  "timeout": 15000,
  "maxRetries": 2,
  "headers": {
    "X-Custom-Header": "value"
  }
}

CLI arguments take precedence over config file values.

Supported Specs

Format	Versions	File types
OpenAPI	3.0.x, 3.1.x	`.json`, `.yaml`, `.yml`
Swagger	2.0	`.json`, `.yaml`, `.yml`

Specs can be loaded from:

Remote URLs (https://...)
Local file paths (./api.yaml, /absolute/path/spec.json)

v0.3.0 Features

Doc Quality Warnings

On startup, mcp-openapi checks each tool's documentation quality. If endpoints have sparse descriptions (under 50 characters), you'll see a warning:

Read the full README →View source on GitHub →

Related MCP Servers

View all in Aggregators View all alternatives

Adoption & maintenance

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

GitHub stars

Stargazers on the source repository.

Last commit

5mo ago

Most recent push to the default branch.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

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

Frequently Asked Questions about Openapi

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "openapi": { "command": "npx", "args": ["-y","mcp-openapi"] } }

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 Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/openapi?style=directory)](https://allmcps.com/mcp/openapi)

HTML Embed

<a href="https://allmcps.com/mcp/openapi"><img src="https://allmcps.com/api/badge/openapi?style=directory" alt="Openapi on AllMCPs" /></a>

Technical Specs & Signals

CategoryAggregators

8/8 checks healthy over the last 32d

36Quality signal: Fair · 36/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools15/30

Adoption & activity2/15

Community engagement0/10

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 24d ago via OSV.dev · mcp-openapi (npm)

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🔗 Aggregators →Alternatives to Openapi →Install in Claude Desktop Install in Cursor Install in VS Code