Connect Postman to Claude Code
Read Postman workspaces, collections and environments, and run the monitors that test an API on a schedule. Add Toolspoke to Claude Code once and it can use 16 Postman actions. Your Postman credential stays in Toolspoke, and you choose which actions Claude Code may call.
Set it up in Claude Code
Three steps, the first one once for every toolkit you will ever add.
Add Toolspoke to Claude Code
Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcpThe sign-in opens in your browser, and Toolspoke asks you to approve it.
Install Postman and connect it
Add Postman to a project in your Toolspoke workspace.
API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.
- API key
- Postman → your avatar → Settings → API keys → Generate API Key. The key acts as you, in every workspace you can open.
Choose what Claude Code may do
All 16 actions start on. Switch off any of the 6 actions that change something in Postman, and Claude Code gets a refusal if it tries.
What you can ask Claude Code for
A few of the Postman actions that only read, so they are safe to try first.
- Return the user the API key belongs to, with their team and API usage limits
- Retrieve one workspace with the collections, environments, monitors, mocks and APIs in it
- List the collections in one workspace, with each collection's uid
- Retrieve one collection in full, its folders, requests, scripts, variables and auth settings
What Claude Code can do in Postman
10 actions read, 4 write and 2 delete or permanently change something.
Reads
Get me
Return the user the API key belongs to, with their team and API usage limits.
List workspaces
List the workspaces this key can open, with the workspace id the collection, environment and monitor lists take. Also the install's connection test, it proves the key reaches workspace data, not just an account.
Get workspace
Retrieve one workspace with the collections, environments, monitors, mocks and APIs in it.
List collections
List the collections in one workspace, with each collection's uid.
Get collection
Retrieve one collection in full, its folders, requests, scripts, variables and auth settings. Collections often carry tokens in headers or variables, so the response is not written to the audit log.
Get collection request
Retrieve one request from a collection, method, URL, headers, body and scripts.
List environments
List environments, optionally in one workspace, with each environment's uid. Values are not included; get_environment returns them.
Get environment
Retrieve one environment with its variables and their values. Environment values are usually secrets, base URLs, API keys, passwords, so the response is not written to the audit log.
List monitors
List monitors, collections Postman runs on a schedule against a live API, with each monitor's uid and whether it is active.
Get monitor
Retrieve one monitor with its schedule, collection, environment and the result of its last run.
Writes
Run monitor
Run a monitor now and return its results, passed and failed assertions, response times and errors. A write rather than destructive: it does exactly what the monitor's own schedule already does, against the API it already targets. Runs longer than 300 seconds return 202 before they finish; set async to true for a long collection and read the result later with get_monitor.
Create collection
Create a collection in a workspace from a Postman Collection v2.1 document. delete_collection undoes it.
Create environment
Create an environment in a workspace. Values are masked in the audit log.
Update environment
Replace an environment's name and variables. The variables sent become the whole list, any variable left out is removed. Values are masked in the audit log.
Deletes or permanently changes
Delete collection
Delete a collection. Destructive because it removes the collection for everyone in the workspace, and any monitor or mock built on it stops working.
Delete environment
Delete an environment and every value in it. Destructive because the values, often the only copy of a secret someone pasted in, cannot be recovered.
Postman in Claude Code: questions
Does Claude Code see my Postman credential?
No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.
Can I stop Claude Code from changing things in Postman?
Yes. Each of the 16 actions can be switched off for a project. Turn off the 6 that change something and Claude Code can only read.
Will 16 actions crowd Claude Code's context?
No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Postman action it needs when it needs it. Adding more toolkits does not add more tools to its list.
Can I add it once for every project?
Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.
What does it cost?
Tool calls are free on every plan, and a Postman call does not run in a sandbox, so it bills nothing.
Postman in your other apps
Try Postman in Claude Code
Free to start, and tool calls cost nothing on any plan.