An MCP server for Claude Code that generates and updates Postman requests from your API code, with a diff before every write.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"postman-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
<div align="center"> <img src="https://raw.githubusercontent.com/logesh-works/postman-mcp/main/assets/logo/logo.svg" alt="Postman MCP" width="96" height="96"> # Postman MCP **Generate and update Postman requests from your API code, from inside Claude Code.** [](https://pypi.org/project/postman-mcp/) [](https://pypi.org/project/postman-mcp/) [](LICENSE) [](https://github.com/logesh-works/postman-mcp/actions/workflows/ci.yml) [](https://logesh-works.github.io/postman-mcp/) [Documentation](https://logesh-works.github.io/postman-mcp/) · [Quickstart](https://logesh-works.github.io/postman-mcp/getting-started/quickstart/) · [Commands](https://logesh-works.github.io/postman-mcp/commands/) · [Roadmap](ROADMAP.md) </div> --- ## Why does this exist? Once you ship an endpoint, the Postman collection for it starts going stale immediately. You add a field, Postman doesn't know. You add a new error response, Postman doesn't know. Nobody updates Postman by hand consistently, because it's pure busywork: open the request, retype the body you already wrote in code, guess at example values, repeat for every route. The information Postman needs already exists in your code: the route, the request body type, the auth dependency, the declared responses. Postman MCP reads that and writes the request for you, so the only thing you do by hand is review a diff and say yes. ## How does it work? Postman MCP runs two things: a CLI (`postman-mcp`) for one-time setup, and an MCP server that Claude Code talks to while you work. You install it once per machine, run `init` once per project, and after that you only ever type slash commands inside Claude Code. **Cl…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.