How does authentication work?

Supports bearer tokens and OAuth2 flows including client credentials, password, and refresh token.

Can I customize tool names and descriptions?

Yes, via OpenAPI extensions like operation.x-mcp-tool-name and operation.x-mcp-tool-description.

What transport protocol does this MCP server use?

Only STDIO transport is supported.

Can I use remote OpenAPI specifications?

Yes, both local files and remote URLs are supported for the OpenAPI spec.

Openapi To MCP

openapioauth2code-executionapimcp

Lightweight MCP server exposing any OpenAPI-defined API endpoints with OAuth2 and JSON schema support.

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.

One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.

Manual Client & Custom JSON ConfigExpand JSON ▾

No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for ouvreboite/openapi-to-mcp, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.

Overview

This server converts OpenAPI 2.0 and 3.0 specifications into MCP tools, exposing API endpoints as strongly typed tools accessible via STDIO transport. It supports local or remote JSON/YAML specs, OAuth2 authentication flows, and custom tool naming and descriptions via OpenAPI extensions. Use it to integrate any OpenAPI-described API into an MCP-compatible AI agent environment.

Use cases

Expose REST API endpoints as MCP tools from OpenAPI specs

Integrate OAuth2-secured APIs using client credentials, password, or refresh token flows

Customize tool names and descriptions via OpenAPI extensions

Call API endpoints with full JSON schema parameter validation

Override API host URL for testing or proxying

Key features

Supports OpenAPI 2.0 and 3.0 specifications (JSON/YAML, local or remote)

OAuth2 authentication with client credentials, password, or refresh token flows

Customizable tool naming strategies including operationId and path-based names

Full JSON schema support for query, path, and request body parameters

Exposes API operations as MCP tools with response passthrough

STDIO transport protocol for MCP communication

Capabilities & Tool Schemas (4)Self-reported

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

operation.x-mcp-tool-name

Callable MCP tool function

operation.x-mcp-tool-description

Callable MCP tool function

operation.description

Callable MCP tool function

path.description

Callable MCP tool function

Documentation Overview

openapi-to-mcp

Use your OpenAPI specification to expose your API's endpoints as strongly typed tools.

Basic example for https://petstore3.swagger.io/ 🎉

config.json

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

More complex example, using Github's API:

JSON Config

{
    "mcpServers": {
        "github": {
            "command": "openapi-to-mcp",
            "args": [
                "https://raw.githubusercontent.com/github/rest-api-description/refs/heads/main/descriptions/api.github.com/api.github.com.yaml",
                "--bearer-token",
                "github_pat_xxxxxx",
                "--tool-naming-strategy",
                "verbandpath"
            ]
        }
    }
}

This example use the bearer token auth (with a Github Personal Access Token) and force the tool naming strategy to "verb and path", as Github's operation ids are not valid tool names.

Github demo

Install

As a Nuget tool: openapi-to-mcp

dotnet tool install --global openapi-to-mcp

Or download the executables from the releases

Usage

bash

Usage:
  openapi-to-mcp <open-api> [options]

Arguments:
  <open-api>  You OpenAPI specification (URL or file) [required]

Options:
  -t, --tool-naming-strategy <extension|extension_or_operationid_or_verbandpath|operationid|verbandpath>  How the tool name should be computed [default: extension_or_operationid_or_verbandpath]
  -h, --host-override                                                                                     Host override
  -b, --bearer-token                                                                                      Bearer token
  -o2, --oauth-2-grant-type <client_credentials|password|refresh_token>                                   OAuth2 flow to be used
  -o2_tu, --oauth-2-token-url                                                                             OAuth2 token endpoint URL (override the one defined in your OpenAPI for your chosen OAuth2 flow)
  -o2_ci, --oauth-2-client-id                                                                             OAuth2 client id (for the client_credentials grant_type)
  -o2_cs, --oauth-2-client-secret                                                                         OAuth2 client secret (for the client_credentials grant_type)
  -o2_rt, --oauth-2-refresh-token                                                                         OAuth2 refresh token (for the refresh_token grant_type)
  -o2_un, --oauth-2-username                                                                              OAuth2 username (for the password grant_type)
  -o2_pw, --oauth-2-password                                                                              OAuth2 password (for the password grant_type)
  -i, --instructions                                                                                      MCP instruction to be advertised by the server
  --verbose                                                                                               Log more info (in sdterr) [default: False]
  -?, -h, --help                                                                                          Show help and usage information
  --version                                                                                               Show version information

OpenAPI support

Currently, OpenAPI 2.0 and 3.0 are supported.
- 3.1 is not (at least not until microsoft/OpenAPI.NET supports it)
Specifications can be JSON/YAML and local (file) or remote (URL)
Only local $refs are supported

OpenAPI custom extensions

A set of custom extensions is available to customize how your API should be exposed:

info.x-mcp-instructions (string): Textual instructions exposed by the MCP server during the initialize handshake
operation.x-mcp-tool-name (string): Custom tool name
operation.x-mcp-tool-description (string): Custom tool description
operation.x-mcp-tool-enabled (boolean): Enabled/disabled a specific operation (enabled by default)

MCP features

Only STDIO transport is currently supported.

Tools

Operations ("endpoints") from your OpenAPI specification are translated to MCP tools

All path/query/JSON body parameters are exposed (using their JSON schema)
Response is returned as-is
By default, the tool name is computed using first the operation.x-mcp-tool-name extension, then the operation.operationId and then {httpMethod}_{escaped_path}
- The tool naming strategy can be defined via the --tool-naming-strategy option.
- ⚠️Tools are discarded if their name don't match ^[a-zA-Z0-9_-]{1,64}$
Tools description are extracted as follows: operation.x-mcp-tool-description ?? operation.description ?? path.description

Tool call and host

When a tool is called, the MCP server will call the underlying endpoint. To determine which host to call a combination of parameters are used:

the --host-override option
your specification first server's URL if it's an absolute URL
the host of the remote OpenAPI provided
otherwise, an error is thrown

For example running openapi-to-mcp https://petstore3.swagger.io/api/v3/openapi.json:

https://petstore3.swagger.io/api/v3/openapi.json defines a server, but its URL is relative (/api/v3)
so the host of the specification's own URL is used: https://petstore3.swagger.io and the relative path of the server is appended to it

Authorization

Bearer token

A token can be provided as option --bearer-token. It'll be provided to all calls as the Authorization: Bearer {token} header. It'll also be provided when fetching a remote specification.

OAuth2

ClientCredentials, RefreshToken, Password are supported. If your OpenAPI specification declare securitySchemes for those flows, the corresponding tokenUrl will be used.

How to publish

Create a new tag/release 🤷

Read the full README →View source on GitHub →

Related MCP Servers

View all in Code Execution 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

1y ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

2 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 To MCP

OpenAPI 2.0 and 3.0 are supported; 3.1 is not currently supported.

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

HTML Embed

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

Technical Specs & Signals

CategoryCode Execution

PricingFree

48Quality signal: Fair · 48/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 & tools23/30

Adoption & activity3/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.

★ Featured

AllMCPs Server

The official MCP server for AllMCPs.com - submit and manage tools directly from your AI. The open directory for MCP servers. Connect Claude, Cursor, Windsurf, and AI agents to databases, tools, files, and APIs. Explore 10,000+ servers. AllMCPs is the premier, open directory for discovering, evaluating, and installing Model Context Protocol (MCP) servers to equip AI agents and LLMs with real-world superpowers.

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 👨‍💻 Code Execution →Best MCP servers for Code Execution →Alternatives to Openapi To MCP →Install in Claude Desktop Install in Cursor Install in VS Code

Openapi To MCP

openapioauth2code-executionapimcp

Lightweight MCP server exposing any OpenAPI-defined API endpoints with OAuth2 and JSON schema support.

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.

Manual Client & Custom JSON ConfigExpand JSON ▾

Overview

Use cases

Expose REST API endpoints as MCP tools from OpenAPI specs

Integrate OAuth2-secured APIs using client credentials, password, or refresh token flows

Customize tool names and descriptions via OpenAPI extensions

Call API endpoints with full JSON schema parameter validation

Override API host URL for testing or proxying

Key features

Supports OpenAPI 2.0 and 3.0 specifications (JSON/YAML, local or remote)

OAuth2 authentication with client credentials, password, or refresh token flows

Customizable tool naming strategies including operationId and path-based names

Full JSON schema support for query, path, and request body parameters

Exposes API operations as MCP tools with response passthrough

STDIO transport protocol for MCP communication

Capabilities & Tool Schemas (4)Self-reported

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

operation.x-mcp-tool-name

Callable MCP tool function

operation.x-mcp-tool-description

Callable MCP tool function

operation.description

Callable MCP tool function

path.description

Callable MCP tool function

Documentation Overview

openapi-to-mcp

Use your OpenAPI specification to expose your API's endpoints as strongly typed tools.

Basic example for https://petstore3.swagger.io/ 🎉

config.json

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

More complex example, using Github's API:

JSON Config

{
    "mcpServers": {
        "github": {
            "command": "openapi-to-mcp",
            "args": [
                "https://raw.githubusercontent.com/github/rest-api-description/refs/heads/main/descriptions/api.github.com/api.github.com.yaml",
                "--bearer-token",
                "github_pat_xxxxxx",
                "--tool-naming-strategy",
                "verbandpath"
            ]
        }
    }
}

This example use the bearer token auth (with a Github Personal Access Token) and force the tool naming strategy to "verb and path", as Github's operation ids are not valid tool names.

Github demo

Install

As a Nuget tool: openapi-to-mcp

dotnet tool install --global openapi-to-mcp

Or download the executables from the releases

Usage

bash

Usage:
  openapi-to-mcp <open-api> [options]

Arguments:
  <open-api>  You OpenAPI specification (URL or file) [required]

Options:
  -t, --tool-naming-strategy <extension|extension_or_operationid_or_verbandpath|operationid|verbandpath>  How the tool name should be computed [default: extension_or_operationid_or_verbandpath]
  -h, --host-override                                                                                     Host override
  -b, --bearer-token                                                                                      Bearer token
  -o2, --oauth-2-grant-type <client_credentials|password|refresh_token>                                   OAuth2 flow to be used
  -o2_tu, --oauth-2-token-url                                                                             OAuth2 token endpoint URL (override the one defined in your OpenAPI for your chosen OAuth2 flow)
  -o2_ci, --oauth-2-client-id                                                                             OAuth2 client id (for the client_credentials grant_type)
  -o2_cs, --oauth-2-client-secret                                                                         OAuth2 client secret (for the client_credentials grant_type)
  -o2_rt, --oauth-2-refresh-token                                                                         OAuth2 refresh token (for the refresh_token grant_type)
  -o2_un, --oauth-2-username                                                                              OAuth2 username (for the password grant_type)
  -o2_pw, --oauth-2-password                                                                              OAuth2 password (for the password grant_type)
  -i, --instructions                                                                                      MCP instruction to be advertised by the server
  --verbose                                                                                               Log more info (in sdterr) [default: False]
  -?, -h, --help                                                                                          Show help and usage information
  --version                                                                                               Show version information

OpenAPI support

Currently, OpenAPI 2.0 and 3.0 are supported.
- 3.1 is not (at least not until microsoft/OpenAPI.NET supports it)
Specifications can be JSON/YAML and local (file) or remote (URL)
Only local $refs are supported

OpenAPI custom extensions

A set of custom extensions is available to customize how your API should be exposed:

info.x-mcp-instructions (string): Textual instructions exposed by the MCP server during the initialize handshake
operation.x-mcp-tool-name (string): Custom tool name
operation.x-mcp-tool-description (string): Custom tool description
operation.x-mcp-tool-enabled (boolean): Enabled/disabled a specific operation (enabled by default)

MCP features

Only STDIO transport is currently supported.

Tools

Operations ("endpoints") from your OpenAPI specification are translated to MCP tools

All path/query/JSON body parameters are exposed (using their JSON schema)
Response is returned as-is
By default, the tool name is computed using first the operation.x-mcp-tool-name extension, then the operation.operationId and then {httpMethod}_{escaped_path}
- The tool naming strategy can be defined via the --tool-naming-strategy option.
- ⚠️Tools are discarded if their name don't match ^[a-zA-Z0-9_-]{1,64}$
Tools description are extracted as follows: operation.x-mcp-tool-description ?? operation.description ?? path.description

Tool call and host

When a tool is called, the MCP server will call the underlying endpoint. To determine which host to call a combination of parameters are used:

the --host-override option
your specification first server's URL if it's an absolute URL
the host of the remote OpenAPI provided
otherwise, an error is thrown

For example running openapi-to-mcp https://petstore3.swagger.io/api/v3/openapi.json:

https://petstore3.swagger.io/api/v3/openapi.json defines a server, but its URL is relative (/api/v3)
so the host of the specification's own URL is used: https://petstore3.swagger.io and the relative path of the server is appended to it

Authorization

Bearer token

A token can be provided as option --bearer-token. It'll be provided to all calls as the Authorization: Bearer {token} header. It'll also be provided when fetching a remote specification.

OAuth2

ClientCredentials, RefreshToken, Password are supported. If your OpenAPI specification declare securitySchemes for those flows, the corresponding tokenUrl will be used.

How to publish

Create a new tag/release 🤷

Read the full README →View source on GitHub →

Related MCP Servers

View all in Code Execution 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

1y ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

2 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 To MCP

OpenAPI 2.0 and 3.0 are supported; 3.1 is not currently supported.

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

HTML Embed

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

Technical Specs & Signals

CategoryCode Execution

PricingFree

48Quality signal: Fair · 48/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 & tools23/30

Adoption & activity3/15

Community engagement0/10

★ Featured

AllMCPs Server

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 👨‍💻 Code Execution →Best MCP servers for Code Execution →Alternatives to Openapi To MCP →Install in Claude Desktop Install in Cursor Install in VS Code