Connect Postman to Claude Code

Let Claude create requests and run collections in Postman. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Postman to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Postman, you add a Postman MCP server: a small hosted service that exposes Postman's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Postman account. No API keys pasted into config files.

claude mcp add --transport http postman https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Postman once connected?

Full read-write Postman access lets Claude create and edit requests inside a collection, update environment variables, run a collection or folder, build mock servers, and organize workspaces. The API design and test setup that used to mean clicking through the app happen where your collections already live, with you approving anything that changes shared state.

Create a new request in a collection with headers, body, and auth
Update environment variables across a workspace
Run a collection or folder and report the test results
Add or edit tests and pre-request scripts on a request
Create a mock server from an existing collection
Organize requests into folders and rename collections

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Postman access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Postman API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Postman changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Postman connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Postman connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Postman account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Postman's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Postman?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Postman account it signs in with. Revoking access is one click in Postman.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.