MCP Gateway · Cursor
Connect Postman to Cursor
When you are writing code against an internal API in Cursor, the request examples your team already saved in Postman are the fastest reference. Cursor finds them in the Private API Network, reads the request and its saved responses, and writes the client code next to them. Every Cursor hook event carries your email, so each call is attributed.
- Category
- Developer tools
- Tools
- 113
- Authentication
- API key
- Cursor
- Editor and terminal
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 Cursor 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 Cursor
Add the gateway to Cursor in one click from the Organization Gateway page.
On the Organization Gateway page in Speakeasy, choose Cursor under Install.
Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.
- 04
Sign in and use Postman from Cursor
The first time Cursor 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 Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.
For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.
Use cases
What Cursor users do with Postman
Find the internal API to call
Search your organization's Private API Network for the service you need, then open the matching request to see its method, URL, headers and body.
Write client code from saved examples
Cursor fetches Postman's code generation instructions and the request's saved response, then writes a typed client function and test fixture in the file you have open.
Save a new request you just tested
After you get a new endpoint working, have Cursor add the request and an example response to the team collection so the next developer can find it.
Tools
113 tools
Each Postman tool can be allowed or denied per team and role at the MCP Gateway before Cursor 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 Cursor
The gateway covers every client the same way. The rest depends on what Cursor 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 Cursor. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Cursor
Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.
User attribution
Cursor
Every Cursor hook event carries the user's email.
Budgets
Cursor
Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
Device agent and MDM
Cursor
The device agent installs the marketplace and plugins and reapplies them every minute.
- Cursor Cloud agents need a checked-in
.cursor/hooks.json. Session and MCP-specific hooks don't run there. - After a plugin update, members run Developer: Reload Window.
Questions
Frequently asked questions
Can Speakeasy block a Postman call from Cursor?
What do Cursor users do after the Postman plugin changes?
How do Cursor users get Postman?
Are Postman calls from Cursor logged?
Connect more