Converts Postman Collections (v2.0 and v2.1) into MCP tools, automatically detecting collection format and transforming requests into callable tools with support for nested folders, path variables, and various body types.
Parses OpenAPI 3.0/3.1 specifications and converts each endpoint into MCP tools, enabling programmatic access to any REST API with OpenAPI documentation including authentication, request filtering, and safety controls.
OpenAPI to MCP
Turn any OpenAPI spec or Postman Collection into an MCP server. Like, instantly.
Got a REST API with an OpenAPI spec or a Postman Collection? Cool, now Claude can use it directly. No code required.
Quick Start
Point Claude Desktop at it:
Done. Your API is now available as MCP tools. Go grab a coffee.
What's the Deal?
OpenAPI 3.0 / 3.1 - We parse your spec and turn each endpoint into an MCP tool
Postman Collections - Got a Postman collection instead? Works the same way
Auto-detection - We figure out what format you're using. You just point, we parse
Zero code - Just point at your spec, we handle the rest
Safe by default - DELETE methods are disabled unless you say otherwise
Auth built-in - API Key, Bearer, Basic - all supported
Filter tools - Use globs to include/exclude specific operations
Production-ready - Health checks, graceful shutdown, structured logging
Installation
Docker (the easy way)
From Source (if you're into that)
Usage
OpenAPI
Postman Collections
Same deal, just point at your collection. We auto-detect the format:
Want to be explicit? Use --format:
Postman v2.0 and v2.1 collection formats are both supported. Nested folders become tags, path variables (:id) become OpenAPI-style ({id}), and all body types (raw JSON, form-data, urlencoded) just work.
With Auth
With a Config File
For more complex setups, use a YAML config:
Then run:
CLI Options
Flag | What it does | Default |
| Fetch spec from URL | - |
| Load spec from local file | - |
| Force format: openapi or postman | auto |
| Base URL for API requests | - |
| Server port | 8080 |
| Host to bind | 0.0.0.0 |
| Config file path | - |
| Only include matching tools | - |
| Exclude matching tools | - |
| debug/info/warn/error | info |
| json/pretty | json |
Environment Variables
Everything can be set via env vars too:
Variable | What it does |
| Spec URL (OpenAPI or Postman) |
| Path to spec file |
| Force format: openapi or postman |
| Upstream API base URL |
| Server port |
| Log level |
| none/apiKey/bearer/basic |
| Header or query param name |
| The actual auth value |
| Comma-separated include patterns |
| Comma-separated exclude patterns |
Endpoints
Endpoint | What's there |
| Health check (for load balancers) |
| List all available tools as JSON |
| The MCP protocol endpoint |
Dynamic Tool Filtering
Different AI agents need different tools? No problem:
Only those tools will be available in that session. Pretty handy.
System Variables
You can use these in your upstream headers config:
Variable | Value |
| Unix timestamp in ms |
| UUID for request tracing |
| ISO 8601 formatted date |
| Client IP address |
Tool Naming
We convert your operationId to snake_case:
getPetById→get_pet_by_idlistUsers→list_userscreateNewOrder→create_new_order
No operationId? We generate from method + path:
GET /pets/{id}→get_pets_id
For Postman collections, the request name becomes the tool name:
"Get All Users"→get_all_users"Create New Post"→create_new_post
Safety Stuff
Auto-disabled Methods
DELETE operations are disabled by default. Enable them explicitly if you need them.
Tool Count Warning
We'll warn you if you enable more than 10 tools. LLMs tend to get confused with too many options.
Development
Don't Want to Self-Host?
Check out MCPize - we'll host it for you. Deploy from your OpenAPI spec in 60 seconds, no infrastructure needed.
Contributing
See CONTRIBUTING.md. We're friendly, promise.
License
Apache 2.0 - do what you want, just keep the license.