What your AI apps can do with Postman
- Manage collections and environments
- Inspect APIs and specifications
Postman MCP tools
38 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.
| Tool | What it does |
|---|---|
getAuthenticatedUser | Show the signed-in Postman user |
getWorkspaces | List workspaces or read one |
getWorkspace | List workspaces or read one |
searchPostmanElements | Search Postman for collections, requests and other elements |
getCollections | List collections or read one |
getCollection | List collections or read one |
getCollectionRequest | Read a request or saved response |
getCollectionResponse | Read a request or saved response |
getEnvironments | List environments or read one |
getEnvironment | List environments or read one |
getAllSpecs | List or read API specifications |
getSpec | List or read API specifications |
getMocks | List mock servers and monitors |
getMonitors | List mock servers and monitors |
createCollection | Create a collection |
createCollectionRequest | Add or change a request in a collection |
updateCollectionRequest | Add or change a request in a collection |
putCollection | Replace a collection's contents |
generateCollection | Generate a collection from a spec, or a spec from a collection |
generateSpecFromCollection | Generate a collection from a spec, or a spec from a collection |
syncCollectionWithSpec | Sync a collection and its spec in either direction |
syncSpecWithCollection | Sync a collection and its spec in either direction |
createEnvironment | Create or replace an environment |
putEnvironment | Create or replace an environment |
createMock | Create a mock server or make it public |
publishMock | Create a mock server or make it public |
runCollection | Run a collection's requests |
runMonitor | Trigger a monitor run |
createWorkspace | Create or change a workspace |
updateWorkspace | Create or change a workspace |
deleteCollection | Delete a collection, environment or workspace |
deleteEnvironment | Delete a collection, environment or workspace |
deleteWorkspace | Delete a collection, environment or workspace |
updateCollectionRoles | Change who can access a collection or workspace |
updateWorkspaceRoles | Change who can access a collection or workspace |
removeTeamMembers | Remove team members or change their roles |
manageTeamMemberRoles | Remove team members or change their roles |
getAuditLogs | Read team audit logs |
Suggested access for each AI app
The documentation this list comes from doesn't mark Postman's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.
Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.
Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.
Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.
Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Postman connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.
How it works with Toolstile
- Connect once. Add Postman to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
- Choose access per app. Give Claude Code every Postman tool, give Cursor only the read tools, or keep Postman away from an app entirely.
- Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
- Review activity. See which app called which tool and when, so you can tighten access with evidence.
Add the Postman MCP server to an AI app
Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:
claude mcp add --transport http toolstile 'https://toolstile.com/mcp'Then connect Postman in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.
To connect directly instead, add the Postman endpoint to each app separately. In Claude Code:
claude mcp add --transport http postman 'https://mcp.postman.com/mcp'In Cursor's mcp.json:
{
"mcpServers": {
"postman": {
"url": "https://mcp.postman.com/mcp"
}
}
}Some servers accept only clients they have approved, or need a token header. Check the Postman MCP documentation for what your client needs.
Before you connect
A Postman account. Sign-in uses your Postman permissions.
Server details
| Detail | Value |
|---|---|
| Publisher | Postman |
| Endpoint | https://mcp.postman.com/mcp |
| Authentication | Browser sign-in |
| Categories | Development |
| Tool list | 38 tools, observed 29 October 2026 (docs) |