MCP Gateway · Claude
Connect Postman to Claude
Product managers and API program owners can ask Claude how the company's APIs are used and what changed, without opening Postman. Claude reads analytics, collection comments and documentation through the Speakeasy MCP Gateway, and each person only sees the servers their role can reach.
- Category
- Developer tools
- Tools
- 113
- Authentication
- API key
- Claude
- Web, desktop and mobile
Behind the MCP Gateway
Run Postman MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Postman call inspected and logged.
Set up
Add Postman to Claude in 4 steps
- 01
Add Postman from the catalog
An admin finds Postman in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Postman authenticates with an API key. Enter it under Upstream headers in the install dialog, or later on the server's Settings tab. The key is stored on the server, sent with every upstream request, and never reaches anyone's client configuration.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Postman
Give teams the
mcp:connectscope on the Postman server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Postman to their gateway on the next call, and removing it takes it away. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Postman from Claude
The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
From then on, Postman's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Postman
Report on API usage this quarter
Ask Claude which analytics resources and metrics are available, pull the numbers for your team and partner workspaces, and turn them into a short usage summary.
Catch up on collection feedback
Before a design review, have Claude collect the comment threads on a collection and its folders and list the open questions by owner.
Publish docs for a partner launch
Once a collection is reviewed, Claude publishes its documentation so anyone with the link can read it, ready to send to the partner.
Tools
113 tools
Each Postman tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.
addWorkspaceToPrivateNetwork
Publishes a workspace to your team's Private API Network.
createCollection
Creates a collection using the [Postman Collection v2.1.0 schema format](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html).
createCollectionComment
Creates a comment on a collection. To create a reply on an existing comment, include the \threadId\ property in the request body.
createCollectionFolder
Creates a folder in a collection. For a complete list of properties, refer to the Folder entry in the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html).
createCollectionFork
Creates a [fork](https://learning.postman.com/docs/collaborating-in-postman/version-control/#creating-a-fork) from an existing collection into a workspace.
createCollectionRequest
Creates a request in a collection. For a complete list of properties, refer to the Request entry in the [Postman Collection Format documentation](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html).
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.
Tool logs
Gateway
Every Postman call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Postman tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Postman can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Can Claude publish Postman documentation without approval?
Are Claude prompts about Postman checked before they run?
How do Claude users get Postman?
Are Postman calls from Claude logged?
Connect more