Skip to main content
0mcp can convert a Postman Collection v2 JSON document into MCP tools. Use this source when your API workflow already lives in Postman and you want to create a hosted MCP server without manually writing an OpenAPI document first.

​
Import methods

You can import a Postman collection in three ways:

​
File

Upload a Postman collection .json file up to 10 MB.

​
URL

Import from a publicly accessible http:// or https:// URL that returns the collection JSON directly.
The URL must be reachable without requiring a browser login.

​
Paste

Paste the full Postman collection JSON document into the editor.

​
Optional environment file

You can upload a Postman environment JSON file during import. Environment values help 0mcp resolve collection variables while converting requests into MCP tools.

​
Upstream base URL

If the collection does not provide a clear upstream base URL, enter one during import. Use the public API origin that 0mcp should call, such as:

​
What happens during import?

0mcp converts the collection into an OpenAPI document, then shows an import preview. The preview lets you:
  • Review the detected base URL, authentication, and operation count.
  • Select which requests should become MCP tools.
  • Rename tools and improve descriptions before creating the server.
  • Review validation findings before publishing.
  • Download the generated OpenAPI document for inspection or future reuse.
Review write, delete, administrative, and payment requests carefully before exposing them as tools.

​
When to use OpenAPI instead

If your API already has an OpenAPI 3.x or Swagger 2.0 document, use the OpenAPI source. Use Postman import when the collection is your best available API description.