Can the specification be loaded from a local file?

Yes. The --spec option accepts either a local path or a remote URL.

How is authentication configured?

Set environment variables for Bearer tokens, API keys, or Basic authentication, depending on the API.

Can I limit which API operations are exposed?

Yes. Use --filter with a path, tag, or operationId pattern.

Which MCP clients are supported?

The README lists Claude Desktop, Cursor, Cline, Claude Code, and other MCP clients as compatible.

MCP Openapi

openapiapideveloper-toolsmcp

Converts OpenAPI 3.x specifications into callable MCP tools with generated schemas and configurable authentication.

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": {
    "saurav61091-mcp-openapi": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-openapi-runner"
      ]
    }
  }
}

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

Overview

mcp-openapi-runner reads local or remote OpenAPI 3.x specifications in JSON or YAML and exposes their operations as MCP tools. Use it to let an MCP client discover and call an API without writing custom tool definitions. It supports endpoint filtering, custom headers, server URL overrides, and Bearer, API key, or Basic authentication.

Use cases

Connect an OpenAPI-described internal API to an MCP client

Expose selected GitHub or Jira endpoints through natural language

Test API operations from a local or remote OpenAPI specification

Switch an API integration between staging and production server URLs

Key features

Generates tools from OpenAPI 3.x JSON or YAML

Resolves $ref references automatically

Generates operationIds when specifications omit them

Supports Bearer, API key, and Basic authentication

Filters exposed endpoints by path, tag, or operationId

Provides list_endpoints and call_endpoint tools

Capabilities & Tool Schemas (2)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by MCP Openapi.

list_endpoints

Returns all operations grouped by tag with operationIds, methods, paths, and parameters

call_endpoint

Executes any operation by `operationId` with path/query/header/body parameters

Documentation Overview

mcp-openapi

Turn any OpenAPI spec into MCP tools for Claude — zero config, instant API access.

Point mcp-openapi-runner at any OpenAPI 3.x spec and Claude can call every endpoint through natural language. No custom integration code. No manual tool definitions. One line of config.

Why mcp-openapi?

Without mcp-openapi	With mcp-openapi
Write custom MCP server per API	One config line per API
Define tool schemas manually	Auto-generated from OpenAPI spec
Handle auth, params, body yourself	Built-in auth + parameter handling
Maintain code as API evolves	Spec changes = tools update automatically

Quick start

Add to your Claude Desktop / Claude Code / Cursor / Cline MCP config:

config.json

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

That's it. Claude can now discover and call every endpoint in that API.

Example conversation

You: What pets are available? Add a new dog named Buddy.

Claude: Let me check what's available. [calls list_endpoints → discovers findPetsByStatus, addPet, ...] [calls call_endpoint → findPetsByStatus with status=available]

There are 3 pets currently available. Now I'll add Buddy... [calls call_endpoint → addPet with {"name":"Buddy","status":"available"}]

Done! Buddy has been added with ID 12345.

Features

Zero config — just point at a spec URL or file
Any OpenAPI 3.x spec — JSON or YAML, local or remote, $ref auto-resolved
Auto-generated operationIds — works even when the spec doesn't define them
Built-in auth — Bearer, API key, Basic auth via environment variables
Endpoint filtering — only expose the endpoints you need with --filter
Custom headers — pass arbitrary headers with --header
Server URL override — point at staging/local with --server-url
Two-tool design — simple list_endpoints → call_endpoint workflow
Works everywhere — Claude Desktop, Claude Code, Cursor, Cline, any MCP client

Ready-to-use configs

Stripe

config.json

{
  "mcpServers": {
    "stripe": {
      "command": "npx",
      "args": ["-y", "mcp-openapi-runner", "--spec", "https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.json"],
      "env": {
        "OPENAPI_BEARER_TOKEN": "sk_test_..."
      }
    }
  }
}

GitHub REST API

config.json

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "mcp-openapi-runner",
        "--spec", "https://raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api.github.com.json",
        "--filter", "repos"],
      "env": {
        "OPENAPI_BEARER_TOKEN": "ghp_..."
      }
    }
  }
}

Your internal API

config.json

{
  "mcpServers": {
    "internal": {
      "command": "npx",
      "args": ["-y", "mcp-openapi-runner", "--spec", "http://localhost:8080/openapi.json"],
      "env": {
        "OPENAPI_API_KEY": "dev-key-123"
      }
    }
  }
}

Jira (Atlassian)

config.json

{
  "mcpServers": {
    "jira": {
      "command": "npx",
      "args": ["-y", "mcp-openapi-runner",
        "--spec", "https://dac-static.atlassian.com/cloud/jira/platform/swagger-v3.v3.json",
        "--server-url", "https://your-domain.atlassian.net",
        "--filter", "issue"],
      "env": {
        "OPENAPI_BASIC_USER": "you@company.com",
        "OPENAPI_BASIC_PASS": "your-api-token"
      }
    }
  }
}

Authentication

Pass credentials via environment variables:

config.json

{
  "mcpServers": {
    "my-api": {
      "command": "npx",
      "args": ["-y", "mcp-openapi-runner", "--spec", "https://api.example.com/openapi.json"],
      "env": {
        "OPENAPI_BEARER_TOKEN": "your-token-here"
      }
    }
  }
}

Variable	Description
`OPENAPI_BEARER_TOKEN`	Bearer token → `Authorization: Bearer <token>`
`OPENAPI_API_KEY`	API key value
`OPENAPI_API_KEY_HEADER`	Header name for API key (default: `X-Api-Key`)
`OPENAPI_BASIC_USER`	HTTP Basic auth username
`OPENAPI_BASIC_PASS`	HTTP Basic auth password

CLI options

Terminal

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

Options:
  --spec         Path or URL to an OpenAPI 3.x spec (JSON or YAML)
  --server-url   Override the base URL from the spec
  --filter       Only expose endpoints matching a pattern (path, tag, or operationId)
  --header       Add custom header to all requests ("Name: Value", repeatable)
  --help         Show help

Examples

bash

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

# Only pet-related endpoints
npx mcp-openapi-runner --spec ./openapi.yaml --filter pets

# Point at local dev server
npx mcp-openapi-runner --spec ./openapi.yaml --server-url http://localhost:3000

# Custom headers
npx mcp-openapi-runner --spec ./openapi.yaml --header "X-Tenant: acme" --header "X-Debug: true"

# With auth
OPENAPI_BEARER_TOKEN=mytoken npx mcp-openapi-runner --spec https://api.example.com/openapi.json

Tools

mcp-openapi-runner exposes exactly two tools:

Tool	Description
`list_endpoints`	Returns all operations grouped by tag with operationIds, methods, paths, and parameters
`call_endpoint`	Executes any operation by `operationId` with path/query/header/body parameters

The two-tool design means Claude always has a clear workflow: discover → call.

How it works

Loads the OpenAPI spec from the given URL or file path
Dereferences all $ref schemas using @apidevtools/swagger-parser
Applies endpoint filter if --filter is set
Registers two MCP tools with the connected client
list_endpoints generates a human+LLM-readable summary of all operations
call_endpoint resolves params, builds the URL, attaches auth + custom headers, returns the response

Requirements

Node.js 18+
OpenAPI 3.x spec (JSON or YAML, local file or URL)

Contributing

Contributions welcome! See CONTRIBUTING.md for guidelines.

License

MIT

Read the full README →View source on GitHub →

Related MCP Servers

View all in Security View all alternatives

Adoption & maintenance

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

GitHub stars

Stargazers on the source repository.

npm downloads

195

Package downloads in the last 30 days.

Last commit

5mo ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

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 MCP Openapi

The server supports OpenAPI 3.x specifications in JSON or YAML format.

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/saurav61091-mcp-openapi?style=directory)](https://allmcps.com/mcp/saurav61091-mcp-openapi)

HTML Embed

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

Technical Specs & Signals

CategorySecurity

PricingFree

55Quality signal: Good · 55/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 & tools27/30

Adoption & activity4/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 27d ago via OSV.dev · mcp-openapi-runner (npm)

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore 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 🔒 Security →Best MCP servers for Security →Alternatives to MCP Openapi →Install in Claude Desktop Install in Cursor Install in VS Code

MCP Openapi

openapiapideveloper-toolsmcp

Converts OpenAPI 3.x specifications into callable MCP tools with generated schemas and configurable authentication.

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": {
    "saurav61091-mcp-openapi": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-openapi-runner"
      ]
    }
  }
}

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

Overview

Use cases

Connect an OpenAPI-described internal API to an MCP client

Expose selected GitHub or Jira endpoints through natural language

Test API operations from a local or remote OpenAPI specification

Switch an API integration between staging and production server URLs

Key features

Generates tools from OpenAPI 3.x JSON or YAML

Resolves $ref references automatically

Generates operationIds when specifications omit them

Supports Bearer, API key, and Basic authentication

Filters exposed endpoints by path, tag, or operationId

Provides list_endpoints and call_endpoint tools

Capabilities & Tool Schemas (2)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by MCP Openapi.

list_endpoints

Returns all operations grouped by tag with operationIds, methods, paths, and parameters

call_endpoint

Executes any operation by `operationId` with path/query/header/body parameters

Documentation Overview

mcp-openapi

Turn any OpenAPI spec into MCP tools for Claude — zero config, instant API access.

Point mcp-openapi-runner at any OpenAPI 3.x spec and Claude can call every endpoint through natural language. No custom integration code. No manual tool definitions. One line of config.

Why mcp-openapi?

Without mcp-openapi	With mcp-openapi
Write custom MCP server per API	One config line per API
Define tool schemas manually	Auto-generated from OpenAPI spec
Handle auth, params, body yourself	Built-in auth + parameter handling
Maintain code as API evolves	Spec changes = tools update automatically

Quick start

Add to your Claude Desktop / Claude Code / Cursor / Cline MCP config:

config.json

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

That's it. Claude can now discover and call every endpoint in that API.

Example conversation

You: What pets are available? Add a new dog named Buddy.

Claude: Let me check what's available. [calls list_endpoints → discovers findPetsByStatus, addPet, ...] [calls call_endpoint → findPetsByStatus with status=available]

There are 3 pets currently available. Now I'll add Buddy... [calls call_endpoint → addPet with {"name":"Buddy","status":"available"}]

Done! Buddy has been added with ID 12345.

Features

Zero config — just point at a spec URL or file
Any OpenAPI 3.x spec — JSON or YAML, local or remote, $ref auto-resolved
Auto-generated operationIds — works even when the spec doesn't define them
Built-in auth — Bearer, API key, Basic auth via environment variables
Endpoint filtering — only expose the endpoints you need with --filter
Custom headers — pass arbitrary headers with --header
Server URL override — point at staging/local with --server-url
Two-tool design — simple list_endpoints → call_endpoint workflow
Works everywhere — Claude Desktop, Claude Code, Cursor, Cline, any MCP client

Ready-to-use configs

Stripe

config.json

{
  "mcpServers": {
    "stripe": {
      "command": "npx",
      "args": ["-y", "mcp-openapi-runner", "--spec", "https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.json"],
      "env": {
        "OPENAPI_BEARER_TOKEN": "sk_test_..."
      }
    }
  }
}

GitHub REST API

config.json

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "mcp-openapi-runner",
        "--spec", "https://raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api.github.com.json",
        "--filter", "repos"],
      "env": {
        "OPENAPI_BEARER_TOKEN": "ghp_..."
      }
    }
  }
}

Your internal API

config.json

{
  "mcpServers": {
    "internal": {
      "command": "npx",
      "args": ["-y", "mcp-openapi-runner", "--spec", "http://localhost:8080/openapi.json"],
      "env": {
        "OPENAPI_API_KEY": "dev-key-123"
      }
    }
  }
}

Jira (Atlassian)

config.json

{
  "mcpServers": {
    "jira": {
      "command": "npx",
      "args": ["-y", "mcp-openapi-runner",
        "--spec", "https://dac-static.atlassian.com/cloud/jira/platform/swagger-v3.v3.json",
        "--server-url", "https://your-domain.atlassian.net",
        "--filter", "issue"],
      "env": {
        "OPENAPI_BASIC_USER": "you@company.com",
        "OPENAPI_BASIC_PASS": "your-api-token"
      }
    }
  }
}

Authentication

Pass credentials via environment variables:

config.json

{
  "mcpServers": {
    "my-api": {
      "command": "npx",
      "args": ["-y", "mcp-openapi-runner", "--spec", "https://api.example.com/openapi.json"],
      "env": {
        "OPENAPI_BEARER_TOKEN": "your-token-here"
      }
    }
  }
}

Variable	Description
`OPENAPI_BEARER_TOKEN`	Bearer token → `Authorization: Bearer <token>`
`OPENAPI_API_KEY`	API key value
`OPENAPI_API_KEY_HEADER`	Header name for API key (default: `X-Api-Key`)
`OPENAPI_BASIC_USER`	HTTP Basic auth username
`OPENAPI_BASIC_PASS`	HTTP Basic auth password

CLI options

Terminal

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

Options:
  --spec         Path or URL to an OpenAPI 3.x spec (JSON or YAML)
  --server-url   Override the base URL from the spec
  --filter       Only expose endpoints matching a pattern (path, tag, or operationId)
  --header       Add custom header to all requests ("Name: Value", repeatable)
  --help         Show help

Examples

bash

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

# Only pet-related endpoints
npx mcp-openapi-runner --spec ./openapi.yaml --filter pets

# Point at local dev server
npx mcp-openapi-runner --spec ./openapi.yaml --server-url http://localhost:3000

# Custom headers
npx mcp-openapi-runner --spec ./openapi.yaml --header "X-Tenant: acme" --header "X-Debug: true"

# With auth
OPENAPI_BEARER_TOKEN=mytoken npx mcp-openapi-runner --spec https://api.example.com/openapi.json

Tools

mcp-openapi-runner exposes exactly two tools:

Tool	Description
`list_endpoints`	Returns all operations grouped by tag with operationIds, methods, paths, and parameters
`call_endpoint`	Executes any operation by `operationId` with path/query/header/body parameters

The two-tool design means Claude always has a clear workflow: discover → call.

How it works

Loads the OpenAPI spec from the given URL or file path
Dereferences all $ref schemas using @apidevtools/swagger-parser
Applies endpoint filter if --filter is set
Registers two MCP tools with the connected client
list_endpoints generates a human+LLM-readable summary of all operations
call_endpoint resolves params, builds the URL, attaches auth + custom headers, returns the response

Requirements

Node.js 18+
OpenAPI 3.x spec (JSON or YAML, local file or URL)

Contributing

Contributions welcome! See CONTRIBUTING.md for guidelines.

License

MIT

Read the full README →View source on GitHub →

Related MCP Servers

View all in Security View all alternatives

Adoption & maintenance

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

GitHub stars

Stargazers on the source repository.

npm downloads

195

Package downloads in the last 30 days.

Last commit

5mo ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

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 MCP Openapi

The server supports OpenAPI 3.x specifications in JSON or YAML format.

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/saurav61091-mcp-openapi?style=directory)](https://allmcps.com/mcp/saurav61091-mcp-openapi)

HTML Embed

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

Technical Specs & Signals

CategorySecurity

PricingFree

55Quality signal: Good · 55/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 & tools27/30

Adoption & activity4/15

Community engagement0/10

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

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

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore 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 🔒 Security →Best MCP servers for Security →Alternatives to MCP Openapi →Install in Claude Desktop Install in Cursor Install in VS Code