OpenAPI to MCP Converter

Convert any OpenAPI specification into MCP tool definitions automatically.

OpenAPI source

Paste OpenAPI 3.x or Swagger 2.0 in JSON or YAML.

Detected endpoints

Paste an OpenAPI document and click Convert to generate MCP tools.

MCP preview

0 selected tools

{
  "tools": []
}

How to Use This Tool

Paste an OpenAPI or Swagger document into the source editor. JSON and YAML are both supported.
Click Convert to detect endpoints and generate MCP tool definitions automatically.
Rename any tool before export if you want cleaner function names for your MCP server.
Uncheck endpoints you do not want to expose to the model, then copy the generated manifest JSON.
Use the output as a starting point alongside the MCP Manifest Generator or Validator before shipping.

Why convert OpenAPI into MCP?

If you already have a documented REST API, you usually do not need to design every MCP tool by hand. The faster route is to translate your existing endpoints into MCP tool definitions, then refine the generated schema where needed.

This works especially well for internal APIs, admin dashboards, and CRUD-heavy services. Your OpenAPI document already describes parameters, request bodies, and operation names. MCP needs almost the same information to expose tools to an AI client.

The output here is intentionally conservative: it keeps parameters in a single input schema, nests request bodies under body, and marks GET requests as read-only hints. That keeps the generated tools predictable and easy to review before you wire them into a real server.

Last updated: April 2026

FAQ

What does this tool do?

It takes an OpenAPI (Swagger) specification and converts each API endpoint into an MCP tool definition. This lets AI assistants use your existing APIs as MCP tools without manual configuration.

Which OpenAPI versions are supported?

OpenAPI 3.0, 3.1, and Swagger 2.0 are all supported. The tool auto-detects the version and handles the conversion accordingly.

How are parameters mapped?

Path parameters, query parameters, and request body schemas are mapped to MCP tool input_schema properties. Response schemas are used to generate tool descriptions. Required parameters are preserved.

Do I still need to review the generated tools?

Yes. Conversion saves setup time, but you should still review tool names, descriptions, and exposed endpoints before putting them behind an MCP server. The best MCP tools are curated, not blindly generated.

Will this modify my existing API?

No. The converter runs in the browser and only transforms your OpenAPI document into MCP-flavored JSON. It does not call your API or change any backend code.