MCP Gateway · Codex
Connect Postman to Codex
Codex can treat Postman as part of the build. It runs monitors, keeps specs and generated collections in step, and sets up environments for the services it is working on. Calls go through the Speakeasy MCP Gateway, where agent hooks allow or deny each one, and an [otel] block in the Codex config sends telemetry so activity is attributed.
- Category
- Developer tools
- Tools
- 113
- Authentication
- API key
- Codex
- CLI and ChatGPT desktop app
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 Codex 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 Codex
Add the gateway as an MCP server, then log in.
Run the first command with your organization gateway URL.
Run the second command to sign in.
codex mcp add 'speakeasy' \ --url 'https://<organization host>/mcp/gateway/<organization slug>' codex mcp login 'speakeasy' - 04
Sign in and use Postman from Codex
The first time Codex 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 Codex, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.
Use cases
What Codex users do with Postman
Run a monitor after a deploy
Once a change ships, ask Codex to run the Postman monitor for that service and report which requests failed, then trace the failures back to the diff it just made.
Keep the collection in sync with the spec
After Codex edits the API specification, it syncs the generated collection so the requests your QA team runs reflect the new schema.
getSpecCollectionssyncCollectionWithSpecgetStatusOfAnAsyncApiTask
Create an environment for a new service
When Codex scaffolds a service, it creates a Postman environment with the base URL and variables the requests expect, ready for the next person to test against.
Tools
113 tools
Each Postman tool can be allowed or denied per team and role at the MCP Gateway before Codex 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 Codex
The gateway covers every client the same way. The rest depends on what Codex 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 Codex. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Codex
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Codex runs it.
User attribution
Codex
An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.
Budgets
Codex
Spend limits can block Codex traffic once a budget is reached.
Device agent and MDM
Codex
The device agent keeps Codex's configuration in sync on managed laptops.
- Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
- The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.
Questions
Frequently asked questions
Are Postman calls from Codex cloud tasks covered?
Can I limit which Postman tools Codex can call?
How do Codex users get Postman?
Are Postman calls from Codex logged?
Connect more