MCP Gateway · Claude Cowork
Connect Postman to Claude Cowork
An API inventory or a governance review takes many Postman reads in a row, which suits a Cowork task. Cowork can walk every spec in a workspace, check pending Private API Network requests and write the results into one report. Agent hooks send each prompt to Speakeasy before the step runs, and OTLP export ties the session to a person.
- Category
- Developer tools
- Tools
- 113
- Authentication
- API key
- Claude Cowork
- Cowork tab in Claude Desktop
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 Cowork 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. Claude Cowork connects to the Postman server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use Postman from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with Postman
Build an inventory of API specs
Cowork lists every specification in a workspace, reads each definition, and produces a table of services, versions and endpoints for the platform team to review.
Review Private API Network requests
Gather the pending requests to add workspaces to the Private API Network, compare each with the workspaces already listed, and prepare a recommendation for a manager to approve or deny.
Audit monitors across services
Cowork reads every monitor and its configuration, flags services with no monitor or a stale one, and writes the gaps into a follow-up document.
Tools
113 tools
Each Postman tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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 Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
Can Cowork approve Private API Network requests on its own?
Do Cowork members need GitHub access to get Postman?
How do Claude Cowork users get Postman?
Are Postman calls from Claude Cowork logged?
Connect more