Overview
The Swagger Import feature reads a Swagger 2.0 specification and converts every operation into a GetMCP tool. It works the same way as OpenAPI Import but handles the older 2.0 format — includingsecurityDefinitions, body parameters with in: body, and base URL construction from schemes + host + basePath.
For OpenAPI 3.x specs, use OpenAPI Import. For Postman collections, use Postman Import.
How to Use
1
Open the Import Dialog
Navigate to your server’s Tools tab and click the Import dropdown, then select OpenAPI / Swagger. When you paste or upload a Swagger 2.0 spec (identified by
"swagger": "2.0"), GetMCP routes it to the Swagger parser automatically.2
Provide the Spec
Choose how to provide the spec — paste text, upload a file, or fetch from a URL.
.json, .yaml, or .yml file (up to 10 MB).Fetch from URL — enter the public URL of your Swagger spec (e.g. https://api.example.com/swagger.json).Then click Parse.3
Select Operations to Import
GetMCP shows a preview table of all discovered operations. Check the ones you want to import, set the conflict behavior, and click Import N tools.
4
Review Results
The result screen shows created, skipped, and failed tools. Click Done to return to the tools list.
What Gets Imported
Differences from OpenAPI 3.x
Swagger 2.0 uses an older structure that differs in a few ways:
GetMCP handles all of these differences automatically.