How to use Postman with Claude Code
You want Postman inside Claude Code so it can audit workspace API assets, organize a collection for handoff, create a mock for client development, and watch an API for failures — without you copy-pasting between tabs. Here is the whole setup, once.
Create your Postman gateway
The gateway is the thing Claude Code connects to, and it is where you decide which Postman tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your Postman tools
In the dashboard, create a gateway and pick the Postman tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Claude Code
-
Add the gateway as a remote HTTP MCP server
claude mcp add arcade --transport http "<YOUR_ARCADE_GATEWAY_URL>"
-
Verify it was added
claude mcp get arcade claude mcp list
-
Try it out
Open Claude Code in your project and ask it to use one of your Postman tools.
Full Claude Code guide in the docs steps verified 2026-08-13
Try these Postman prompts
Claude Code can now act on your Postman account. Click a prompt to copy it.
Use a shared Postman API key with scoped permissions, and require approval before deleting collections or environments, changing variables, or updating requests. Pair it with Contextual Access policies to keep sensitive environment values and destructive actions behind explicit controls.