Convert OpenAPI to MCP server
Every operation becomes a tool, every parameter an input field — auth mapped automatically, nothing stored.
Open the converter →Conversion is mechanical, and that is the point. openapi2mcp reads your OpenAPI document and maps every operation to exactly one MCP tool: path, method, summary and description carry over, and each parameter — path, query, header or body — becomes a field in that tool's input schema. Your API's shape does the describing; there is nothing to hand-write and nothing to keep in sync. When the API changes, you regenerate and the tools follow.
Authentication is included, not bolted on. securitySchemes declared in the spec are detected and mapped to environment variables in the generated project's .env file, so Bearer tokens, API keys and HTTP Basic all work without writing glue code. Your spec is parsed entirely in memory and never stored, and the result is read-only by default: only GET operations are exposed until you explicitly allow writes.
New to the protocol? Read what an MCP server is, or see what the MCP server generator produces.