Swagger to MCP server
Swagger 2.0 and OpenAPI 3.x both accepted — the old format is upgraded automatically.
Open the converter →Swagger 2.0 and OpenAPI 3.x describe the same thing — your API — in different dialects, and openapi2mcp accepts both. Upload a swagger.json or swagger.yaml from Swagger UI, Swagger Editor, or your repository, and the older format is upgraded automatically before conversion: every operation becomes an MCP tool, every parameter an input field, and Swagger 2.0 securityDefinitions are treated exactly like 3.x securitySchemes.
Nothing is kept: the document is parsed in memory and never stored. Auth is included, mapped to environment variables in the generated project's .env; and the output is read-only by default, with write operations hidden until you explicitly allow them.
For the generic flow see convert OpenAPI to MCP, or browse MCP server examples of what teams expose first.