Postman MCP
Sync your API code into Postman collections — body, params, auth, responses, tests, and examples — with zero manual fill, straight from Claude Code.
README
<div align="center">
<img src="assets/logo/logo.svg" alt="Postman MCP" width="96" height="96">
Postman MCP
Sync your API code into Postman collections — body, params, auth, responses, tests, and examples — with zero manual fill, straight from Claude Code.
OpenAPI-first · code-parsing fallback · a diff before every write.
Documentation · Quickstart · Commands · Roadmap
</div>
Demo — an animated
syncapi→ diff → write recording goes here at launch (seeassets/README.md).
/postman:syncapi createPayment --into payments
SYNC PREVIEW — POST /payments → collection / payments [NEW] [openapi]
+ Request POST {{base_url}}/payments
+ Auth Bearer {{token}} (from require_auth middleware)
+ Body { "amount": 4200, "currency": "USD", "method": "card" }
+ Responses 201 Created, 400, 401, 422, 500
+ Tests status(201) · schema(PaymentResponse) · business(amount > 0)
+ Examples 1 success, 4 error
Write? [y / n]
The problem
API code and Postman drift apart the moment you ship. Every new route, changed body shape, or added error response means going back into Postman by hand — re-typing fields, re-writing example data, re-doing test scripts. The work is mechanical, constant, and easy to skip, so collections rot. A rotten collection is worse than none: teammates trust it, then get burned by a stale endpoint.
The code already contains everything Postman needs — routes, types, middleware, comments. There's no reason a human should be the copy machine between them.
Why Postman MCP
- Zero manual fill. Body, params, auth headers, every response, examples, and test scaffolds — all generated from your code.
- OpenAPI-first. When your framework emits a spec, one mapper covers FastAPI, NestJS, and Django REST Framework. No spec? It falls back to parsing your code.
- Diff before every write. Nothing reaches Postman until you've seen exactly what changes. There is no skip flag.
- Never destroys your work. Test scripts, manual examples, and edited descriptions are read back and preserved on every sync.
- Secrets never touch the repo. Your Postman API key is stored by reference — OS keychain, env var, or a gitignored file.
- Low token cost.
syncchangesparses only what you changed and reads just the collection's basic structure — never a full re-scan.
Features
| Five sync commands | from one route to the whole codebase |
| Frameworks | FastAPI · Django REST Framework · Express · NestJS |
| Input | OpenAPI 3.x spec (preferred) or framework code parsing, decided per route |
| Output | complete Postman Collection v2.1 items — request, responses, scripts, examples, docs |
| Tests | status + schema tiers (deterministic); business-logic tier gated/opt-in |
| Safety | diff-before-write, soft deletes, preserved human work, secret masking |
Architecture
Claude Code ──slash commands──▶ Postman MCP Server (local)
◀──diffs/prompts───
│
┌──────────┬──────────┬───────────┼──────────┬───────────┐
▼ ▼ ▼ ▼ ▼ ▼
Command Input Engine Postman Git Config +
router resolver (builder) client reader Secret store
(OpenAPI/ (REST) (diff since
code) commit)
The five sync commands are one engine plus five selectors — the engine turns a normalized route model into a complete Postman request; the selectors decide which code goes in and where it lands. Full write-up in the architecture docs.
Installation
pip install postman-mcp
Requires Python ≥ 3.10, Claude Code, and a Postman personal API key. See Installation.
Quick start
# 1. install
pip install postman-mcp
# 2. set up this project (once)
cd my-api-project
postman-mcp init
# → paste your Postman API key
# → pick workspace + collection
# → done: server registered, commands installed
# 3. open Claude Code in this project, then:
/postman:syncall # first full sync
/postman:syncchanges # from now on, after each change
# anytime something looks off:
postman-mcp doctor # checks the whole setup chain
How it works
| Step | Where | What |
|---|---|---|
pip install postman-mcp |
terminal | CLI + MCP server + slash commands + engine |
postman-mcp init |
terminal | key handshake, pick workspace + collection, write config, register MCP server, install slash commands |
/postman:* |
Claude Code | sync APIs into the collection |
Three actions — install, init, then use inside Claude Code. After init, you never touch the terminal again for normal work.
Commands
| Command | What it does |
|---|---|
/postman:syncapi <fn|"METHOD /route"|code> [--into path] |
Sync one API (the kernel). |
/postman:syncchanges [--last N] [--since ref] |
Sync what changed since last sync (daily driver). |
/postman:sync -<file|module|dir> [--into path] |
Sync everything in one file/module/dir. |
/postman:syncall [--into path] |
Sync the whole codebase. |
/postman:createenv [name] |
Generate a Postman environment from code. |
/postman:status [--since ref] |
Read-only drift check. No writes. |
Terminal-only: postman-mcp init, postman-mcp doctor, postman-mcp serve,
postman-mcp version.
Examples
Runnable examples per framework live in examples/:
| Example | Framework | Input path |
|---|---|---|
fastapi-basic/ |
FastAPI | code parsing |
fastapi-openapi/ |
FastAPI | OpenAPI spec |
django-rest-framework/ |
Django REST Framework | OpenAPI |
express-api/ |
Express | code parsing |
nestjs-api/ |
NestJS | OpenAPI |
Configuration
All config lives in a small, committable, secret-free postman-mcp.json at your project
root. See Configuration.
Framework support
OpenAPI-first for FastAPI, NestJS (@nestjs/swagger), and DRF (drf-spectacular);
code-parsing fallback for all four, with Express as the primary code-path case. Details and
known limits in the framework guides.
Roadmap
0.1.0 MVP → 0.2.0 hardening → 0.3.0 CI + Newman → 1.0.0 stable. See
ROADMAP.md.
Contributing
Contributions welcome! See CONTRIBUTING.md, the Code of Conduct, and the development docs.
git clone https://github.com/logesh-works/postman-mcp
cd postman-mcp
python -m venv .venv && pip install -e ".[dev]"
pytest --cov
Security
The API key is stored by reference only and every write is gated behind a diff. Report vulnerabilities privately — see SECURITY.md.
License
MIT © Logesh Kumar (logeshkumar.in).
<div align="center"> <sub>Code is the source of truth for what an API <em>is</em>; Postman for what <em>exists</em>.</sub> </div>
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.