PluginInstalls cleanly
Test and mock your API with Postman
Postman Plugin
Postman's official plugin lets your assistant design, mock and test the API behind your app as plain files you can review, then share them with Postman.
- Works with
- Claude Code, Codex CLI
- Good for
- Web developers, Build an app
What it does
An API is the part of an app that other programs talk to, for example the address your website calls to load products. Postman is a popular tool for trying and testing APIs, and this plugin comes from Postman itself.
With it, your assistant keeps API requests, test collections and settings as small files in your project folder, so every change is easy to read and undo with git. It can make a pretend version of an API (a mock) so you can build the website before the real API is ready, run your tests, and check an API description for mistakes. Most of this uses the Postman CLI, which the plugin's setup skill installs if you do not have it.
With a Postman account, it can also ask Postman's Context Graph what could break before you change an API. That part sends questions to Postman.
In Claude Code the plugin adds a hook that runs each time a session starts. It reminds the assistant to use the Postman skills for API work. It runs on your computer and sends nothing.
Example prompts
- "Make Postman requests for every endpoint in this project and run them."
- "Create a mock of this API from openapi.yaml so I can build the frontend now."
- "Lint my API spec and explain each problem in plain words."
- "What happens to my app if the payments API is down? Simulate it."
How to install
claude plugin marketplace add anthropics/claude-plugins-officialclaude plugin install postman@claude-plugins-officialHow to use it
Ask: Write Postman tests for the API in this project and run them. The plugin's skills load by themselves when the task is about an API.
Other assistants
Codex (from the README):
codex plugin marketplace add postmanlabs/postman-plugin --ref main
codex plugin marketplace upgrade postman
codex plugin add postman@postmanThese commands track main, and Codex updates the plugin from it when a session starts. Since installer 0.8.0 (10 November 2026) the Codex route has no session-start hook, so there is no hook to review.
Every supported assistant on your computer at once (from the README): npx @postman/postman-plugin@latest. Add status to see what is installed, remove to uninstall, or --agent <id> to limit it to one assistant. Since 0.8.0 remove also removes the Postman marketplace and the Codex hook approval that older versions left behind; run it again to clean up after an older remove.
We have not tested the Codex routes.
Check it works
In Claude Code, run /plugin and check that postman is listed as installed. Type / and look for the skills, for example /postman:api-engineer (our reading, not tested). The npx installer also has a status command that shows where Postman is installed (README).
Common problems
claude plugin installcannot find postman — the official marketplace is not registered yet on a fresh Claude Code — run the marketplace add line first, as the README explains — https://github.com/postmanlabs/postman-plugin- Codex asks you to approve the Postman hook again — an older plugin version from main still had the hook — run
codex plugin marketplace upgrade postman; since 0.8.0 the Codex route has no session-start hook (release 0.8.0) — https://github.com/postmanlabs/postman-plugin/pull/149 removeleft the Postman marketplace or a Codex approval behind — you ran an older installer copy — runnpx @postman/postman-plugin@latest remove(README, release 0.8.0) — https://github.com/postmanlabs/postman-plugin/pull/148- Simulation commands fail — the Postman CLI is older than 1.70.0 — update the Postman CLI (README) — https://github.com/postmanlabs/postman-plugin
What to watch out for
- Sends data to Postman: once a folder is connected to a Postman workspace (postman init), run results, lint results and request activity are published to it by default; pass --report-events=false to stop that (README). The assistant can run postman init itself, so approve that step yourself (our reading)
- Telemetry: the Postman CLI records anonymous command usage counts; the README gives no way to turn this off (README)
- The plugin also registers Postman's hosted MCP server (mcp.postman.com) as a fallback, and those calls always reach Postman (README); in Claude Code you can turn the server off in /mcp (our reading)
- In Claude Code it adds a session-start hook: at every start, clear and compact it puts a note into the chat that tells the assistant to load the Postman api-engineer skill for any non-trivial API task (hooks/hooks.json); it runs locally and sends nothing
- If the Postman CLI is missing, the setup skill installs it globally with npm install -g postman-cli or Postman's curl install script (cli-install skill; it replaced the bootstrap skill in 0.6.0)
- The one-line installer (npx @postman/postman-plugin@latest) sets up every agent it finds on your computer; use the per-agent lines for more control. Before 0.8.0 (10 November 2026) it also approved a Codex session-start hook for you. Since 0.8.0 the Codex route has no session-start hook, and the installer approves none (release 0.8.0, pull request #149)
- Since 0.8.0, npx @postman/postman-plugin@latest remove also removes the Postman marketplace it added and, for Codex, the old hook approval. Keep @latest: the README says without it npx can run an older copy of the installer that removes less. Sign-in tokens for the Postman MCP server stay in each assistant (release 0.8.0, pull request #148)
- Postman has a free plan and paid plans (Solo $9, Team $19 per user a month, billed yearly); Context Graph questions are free up to 1,000 to 5,000 a month by plan, then $0.01 each (pricing page)
Licence and author
- Licence
- Apache-2.0
- Author
- Postman
- Source code
- github.com/postmanlabs/postman-plugin
How we tested it
We installed it on an empty test computer on 23 Oct 2026. Installed and started in a clean test system. Not yet used in a real AI session.
Not run: "codex plugin marketplace add postmanlabs/postman-plugin --ref main" (not a form the sandbox runs). Not run: "codex plugin marketplace upgrade postman" (not a form the sandbox runs). Not run: "codex plugin add postman@postman" (not a form the sandbox runs). Not yet used on real work. The official marketplace installs commit c6352ef (2026-10-13, plugin 2.0.1); no Postman sign-in, so nothing was sent to a workspace.
Technical details of the test
- Date
- 23 Oct 2026
- Method
- Intake sandbox run on 2026-10-23 in a clean container with no account: cloned the repository and checked its skill, agent and plugin files; installed postman@claude-plugins-official with the Claude Code command line.
Checked again on 10 Nov 2026
Alternatives
- Playwright MCP — tests your website in a real browser instead of the API behind it
- Chrome DevTools MCP — shows the network calls a page makes while you test it
FAQ
- Q: Do I need to know what an API is? A: It helps. Ask the assistant to explain each request it writes.
- Q: Does it cost money? A: The plugin is free (Apache-2.0). Postman has a free plan and paid plans from $9 a month; Context Graph questions above your plan's free amount cost $0.01 each (pricing page).
- Q: Does it work in Gemini CLI? A: The README does not list Gemini CLI.
- Q: Is my data sent to Postman? A: The CLI records anonymous command usage counts (README). Your results go to Postman when a folder is connected to a Postman workspace, when the MCP server is used, or when you ask the Context Graph; see the risks.
Sources
- github.com/postmanlabs/postman-plugin
- github.com/postmanlabs/postman-plugin/blob/main/hooks/session-start-context.md
- github.com/postmanlabs/postman-plugin/blob/e5f3170/skills/cli-install/SKILL.md
- postman.com/pricing/
- github.com/postmanlabs/postman-plugin/releases/tag/%40postman%2Fpostman-plugin%400.8.0
- github.com/postmanlabs/postman-plugin/pull/148
- github.com/postmanlabs/postman-plugin/pull/149
- github.com/postmanlabs/postman-plugin/blob/e5f3170/README.md