How to Turn a Postman Collection into an MCP Server
Plenty of APIs are described by a Postman collection and nothing else. The team tests in Postman, shares the collection with partners and never got around to writing an OpenAPI spec. Now users want to call that API from Claude, Cursor or ChatGPT, and most MCP tutorials start with "take your OpenAPI file". You don't need one. This guide shows how to turn a Postman collection into a hosted MCP…
Postman collections are a popular way to document and share APIs. Often, teams have an existing Postman collection but lack an OpenAPI specification. This guide explains how to transform a Postman collection into a hosted MCP (Managed API) server, along with configuring sign-in and describing endpoints for easy access by AI assistants.
The process outlines three methods to move from Postman to MCP, with the first method focusing on generating a server using DocStar, a popular MCP platform. The steps include exporting the collection from Postman, importing it into DocStar, reviewing endpoints and authentication, and finally publishing the server URL. DocStar handles the conversion and server generation, and the resulting URL remains stable.
Users can then sign in using OAuth or API keys and integrate the server with popular AI assistants like Claude, Cursor, and ChatGPT. Additional tips are provided for writing effective tool descriptions to ensure assistants pick the right endpoints.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
