remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Integrations
Converts FastAPI endpoints to Postman collections, enabling automatic synchronization of API definitions with Postman for documentation and testing.
Extracts Flask endpoints and converts them to Postman collections, allowing developers to automatically keep their Postman workspace in sync with their Flask API code.
Parses NestJS controllers to extract REST API endpoints and convert them into Postman collections, maintaining authentication settings and endpoint structures.
REST-to-Postman MCP
A Model Context Protocol (MCP) server that converts REST API code (e.g., NestJS controllers, FastAPI/Flask endpoints) to Postman collections and environments. This tool helps developers automatically sync their REST API endpoints and environment configurations with Postman.
Features
- Convert REST API endpoints to Postman collections
- Sync environment variables with Postman environments
- Support for various authentication methods (e.g., Bearer token)
- Intelligent merging of new endpoints with existing collections
- Automatic handling of sensitive environment variables
- Support for both stdio and SSE transport modes
Prerequisites
- Bun v1.2.2 or later
- Postman API Key
- Postman Workspace ID
Installation & Usage
This is a Model Context Protocol (MCP) stdio server that requires access to your Postman workspace to create/update collections and environments.
Installing via Smithery
To install REST-to-Postman MCP for Claude Desktop automatically via Smithery:
Running the MCP Server with npx
To use the MCP server with npx
:
Or use environment variables:
You can integrate this command with various AI code editors that support MCP:
- Claude Desktop
- Cursor
- Windsurf
- Roo Cline Editor
Important Note: The server requires Postman API credentials to function. Make sure you have both the API key and workspace ID ready before starting the server.
Tool Descriptions
The server provides two main tools:
1. REST to Postman Environment (rest_to_postman_env
)
Creates or updates a Postman environment with your application's environment variables.
Input Parameters:
envName
(string): Name of the Postman environmentenvVars
(object): Key-value pairs of environment variables
Example Input:
2. REST to Postman Collection (rest_to_postman_collection
)
Creates or updates a Postman collection with your REST API endpoints.
Input Parameters:
collectionRequest
(object): Postman collection configuration containing:info
: Collection metadataauth
: Authentication settingsitem
: Array of API endpoints
Example Input:
Response Format
Both tools return a success message confirming the creation/update of the Postman resource:
Use this MCP in Cursor
You can use this MCP server in Cursor. Here's an example which generates a Postman Collection based on a Nest.js Typescript controller.
Prompt:
Here's the automatically generated Postman Collection:
Note all the endpoints from the Campaign
Controller are generated, along with the Bear token setting.
Development
Local Setup
- Clone the repository:
- Install dependencies:
- Create a
.env
file:
Running in Development Mode
For development, you can run the server directly using Bun:
Building
To build the project:
This will create a bundled output in the dist
directory.
Scripts
bun run build
- Build the projectbun run dev
- Run the server in development modebun run startSSE
- Start the server in SSE mode
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
This project is licensed under the MIT License - see the LICENSE file for details.
You must be authenticated.
Converts REST API code (like NestJS controllers or FastAPI endpoints) to Postman collections and environments, helping developers automatically sync their API endpoints with Postman.