Postman MCP server for your AI

Fork a collection, patch its requests, spin up a mock server, run a monitor and read the results — all from the chat window, against the workspaces your API key can already see.

PopMCPPostman

Which monitors failed on their last run in the Payments workspace?

Contact support Connect

Supported Postman tools

The full set of calls and triggers on this connection — workspaces, collections, environments, mocks, monitors, specs, tags, analytics and search.

postman_create_collection

Creates a collection using the Postman Collection v2.1.0 schema format.

postman_create_collection_comment

Creates a comment on a collection.

postman_create_collection_folder

Creates a folder in a collection.

postman_create_collection_fork

Creates a fork from an existing collection into a workspace.

postman_create_collection_request

Creates a request in a collection.

postman_delete_collection

Deletes a collection.

postman_get_collection

Get information about a collection.

postman_get_collection_comments

Gets all comments left by users in a collection.

postman_get_collection_forks

Gets a collection's forked collections.

postman_get_collections

The workspace ID query is required for this endpoint.

postman_merge_collection_fork

This endpoint is deprecated.

postman_patch_collection

Updates specific collection information, such as its name, events, or its variables.

postman_put_collection

Replaces the contents of a collection using the Postman Collection v2.1.0 schema format.

postman_update_collection_request

Updates a request in a collection.

postman_create_spec

Creates an API specification in Postman's Spec Hub.

postman_get_all_specs

Gets all API specifications in a workspace.

postman_get_spec

Gets information about an API specification.

postman_create_mock

Creates a mock server in a collection.

postman_delete_mock

Deletes a mock server.

postman_get_mock

Gets information about a mock server.

postman_get_mocks

Gets all active mock servers.

postman_update_mock

Updates a mock server.

postman_create_monitor

Creates a monitor.

postman_create_workspace

Creates a new workspace.

postman_delete_monitor

Deletes a monitor.

postman_delete_workspace

Deletes an existing workspace.

postman_get_monitor

Gets information about a monitor.

postman_get_monitors

Gets all monitors.

postman_get_workspace

Gets information about a workspace.

postman_get_workspaces

Gets all workspaces you have access to.

postman_run_monitor

Runs a monitor and returns its run results.

postman_update_workspace

Updates a workspace's property, such as its name or visibility.

postman_create_environment

Creates an environment.

postman_delete_environment

Deletes an environment.

postman_get_environment

Gets information about an environment.

postman_get_environments

Gets information about all of your environments.

postman_patch_environment

Updates specific environment properties, such as its name and variables.

postman_put_environment

Replaces all the contents of an environment with the given information.

postman_get_authenticated_user

Gets information about the authenticated user.

postman_search_postman_elements

Search Postman for entities (requests, collections, workspaces, specs, flows, environments, mocks).

postman_create_collection_response

Creates a request response in a collection.

postman_create_folder_comment

Creates a comment on a folder.

postman_create_request_comment

The request ID must contain the team ID as a prefix, in teamId-requestId format.

postman_create_response_comment

Creates a comment on a response.

postman_delete_collection_comment

Deletes a comment from a collection.

postman_delete_collection_folder

Deletes a folder in a collection.

postman_delete_collection_request

Deletes a request in a collection.

postman_delete_collection_response

Deletes a response in a collection.

postman_delete_folder_comment

Deletes a comment from a folder.

postman_delete_request_comment

Deletes a comment from a request.

postman_delete_response_comment

Deletes a comment from a response.

postman_duplicate_collection

Creates a duplicate of the given collection in another workspace.

postman_generate_spec_from_collection

Generates an OpenAPI 2.0, 3.0, or 3.1 specification for the given collection.

postman_get_collection_folder

Gets information about a folder in a collection.

postman_get_collection_request

Gets information about a request in a collection.

postman_get_collection_response

Gets information about a response in a collection.

postman_get_collection_tags

Gets all the tags associated with a collection.

postman_get_collection_updates_tasks

Gets the status of an asynchronous collection update task.

postman_get_collections_forked_by_user

Gets a list of all the authenticated user's forked collections.

postman_get_duplicate_collection_task_status

Gets the status of a collection duplication task.

postman_get_folder_comments

Gets all comments left by users in a folder.

postman_get_generated_collection_specs

Gets the API specification generated for the given collection.

postman_get_request_comments

Gets all comments left by users in a request.

postman_get_response_comments

Gets all comments left by users in a response.

postman_get_source_collection_status

Checks whether there is a change between the forked collection and its parent (source) collection.

postman_publish_documentation

Publishes a collection's documentation.

postman_pull_collection_changes

Pulls the changes from a parent (source) collection into the forked collection.

postman_sync_collection_with_spec

Syncs a collection generated from an API specification.

postman_transfer_collection_folders

Copies or moves folders into a collection or folder.

postman_transfer_collection_requests

Copies or moves requests into a collection or folder.

postman_transfer_collection_responses

Copies or moves responses into a request.

postman_unpublish_documentation

Unpublishes a collection's documentation.

postman_update_collection_comment

Updates a comment on a collection.

postman_update_collection_folder

Updates a folder in a collection.

postman_update_collection_response

Updates a response in a collection.

postman_update_collection_tags

Updates a collection's associated tags.

postman_update_folder_comment

Updates a comment on a folder.

postman_update_request_comment

Updates a comment on a request.

postman_update_response_comment

Updates a comment on a response.

postman_create_spec_file

Creates a file for an OpenAPI or a protobuf 2 or 3 specification.

postman_delete_spec

Deletes an API specification.

postman_delete_spec_file

Deletes a file in an API specification.

postman_generate_collection

Creates a collection from the given API specification.

postman_get_async_spec_task_status

Gets the status of an asynchronous API specification creation task.

postman_get_spec_collections

Gets all of an API specification's generated collections.

postman_get_spec_definition

Gets the complete contents of an OpenAPI or AsyncAPI specification's definition.

postman_get_spec_file

Gets the contents of an API specification's file.

postman_get_spec_files

Gets all the files in an API specification.

postman_sync_spec_with_collection

Syncs an API specification linked to a collection.

postman_update_spec_file

Updates a file for an OpenAPI or protobuf 2 or 3 specification.

postman_update_spec_properties

Updates an API specification's properties, such as its name.

postman_create_mock_server_response

Creates a server response on a mock server.

postman_delete_mock_server_response

Deletes a server response from a mock server.

postman_get_mock_server_response

Gets the full details of a specific server response, including its body, headers, and language.

postman_get_mock_server_responses

Gets all server responses configured for a mock server.

postman_publish_mock

Publishes a mock server.

postman_unpublish_mock

Unpublishes a mock server.

postman_update_mock_server_response

Updates a server response's name, statusCode, body, headers, or language.

postman_get_monitor_run_results

Gets results for a monitor run, including trimmed execution logs (beforeItem and assertion events only) and result counts.

postman_get_workspace_global_variables

Gets a workspace's global variables.

postman_get_workspace_tags

Gets all the tags associated with a workspace.

postman_list_monitor_executions

Lists executions for a monitor.

postman_list_runs_for_execution

Lists runs for a monitor execution.

postman_update_monitor

Updates a monitor's configurations.

postman_update_workspace_global_variables

Updates and replaces a workspace's global variables.

postman_update_workspace_tags

Updates a workspace's associated tags.

postman_add_workspace_to_private_network

Publishes a workspace to your team's Private API Network.

postman_list_private_network_add_requests

Gets all requests to add workspaces to your team's Private API Network.

postman_list_private_network_workspaces

Gets information about workspaces added to your team's Private API Network.

postman_remove_workspace_from_private_network

Removes a workspace from your team's Private API Network.

postman_respond_private_network_add_request

Responds to an user's request to add a workspace to your team's Private API Network.

postman_delete_api_collection_comment

Deletes a comment from an API's collection.

postman_get_status_of_an_async_api_task

Gets the status of an asynchronous task.

postman_update_api_collection_comment

Updates a comment on an API's collection.

postman_get_analytics_data

Gets analytics data based on the specified resource, metrics, and given filters for team, internal, and public workspaces, as well as Partner Workspaces.

postman_get_analytics_metadata

Returns a catalog of analytics resources and their corresponding metrics for use with the GET /analytics endpoint.

postman_get_tagged_entities

Requires an Enterprise plan.

postman_resolve_comment_thread

Resolves a comment and any associated replies.

Connect Postman to your AI

Credentials off one Postman screen, then an endpoint your client signs into. Nothing to deploy, and nothing to install.

Paste your key into the API key field on the connect form — no OAuth popup, no token refresh. The key is scoped to one Postman account, so the connection is locked to that account and the workspaces it can see.

API key••••••••••••3f7a

ConnectionVerified

Drop the PopMCP URL into Claude, ChatGPT, Codex or any other supported client. It signs in through PopMCP with OAuth, so your Postman credential never leaves the server.

app.popmcp.com/mcp/…

Claude wants to connectApprove

Ask for something harmless before you turn writes on. Once it comes back clean, widen the tool set or switch the connection to full access.

Which monitors failed on their last run in the Payments workspace?

postman_get_workspacesok

Then just ask for the work

“Which monitors failed on their last run in the Payments workspace?”
- get_workspaces
- get_monitors
- get_monitor
“Rename every mock server in the Staging workspace to start with stg-”
- get_mocks
- get_mock
- update_mock
“Fork the Billing API collection into my sandbox workspace and add a smoke-test folder”
- get_collections
- create_collection_fork
- create_collection_folder
“Which API specs in our Platform workspace have no monitor watching them?”
- get_workspaces
- get_all_specs
- get_monitors

Contact support View docs

Use Postman from the assistant you already open

One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.

Claude DesktopCustom connector

Add the PopMCP URL under Settings → Connectors and the tools appear in every chat.

Claude WebCustom connector

The same endpoint, registered in the browser. Nothing to install on the machine you are working from.

ChatGPTCustom connector

CodexDesktop & CLI

Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.

OpenCodeCoding agent

ZCodeDesktop app

Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.

Contact support View docs

FAQ

Postman MCP server questions

What teams ask before putting Postman behind an AI client.

What does my Postman API key give the agent access to?

The key is scoped to one Postman account, and the connection is locked to that account — the agent reaches exactly the workspaces, collections, environments and monitors that key already has rights to. There is no OAuth popup and nothing to re-authorize later, because there is no token to refresh. You paste the key once on the connect form and the MCP server is ready.

Can it edit collections, or only read them?

It edits. Collections is by far the biggest module on this connection: create, fork, add folders and requests, update a request, leave and read comments, and delete. Watch the difference between patch_collection, which updates named parts like the collection's name, events or variables, and put_collection, which replaces the whole collection body against the Postman Collection v2.1.0 schema. One caveat worth knowing: merge_collection_fork is deprecated on Postman's side.

How many tools load into my AI client by default?

40 of the 118 operations load up front, which keeps the tool list in your client short enough to stay useful. The other 78 stay searchable and get pulled in when a request actually needs them, or you can switch on the full catalog and have everything present from the start. Across the whole set it works out to 46 reads and 72 writes, spread over 13 API modules.

Can the agent run a monitor and act on what it finds?

Yes. run_monitor executes a monitor and returns its run results, so the agent can trigger a check and read the failing tests in the same turn, rather than firing and forgetting. create_monitor, get_monitors, get_monitor and delete_monitor cover the rest of the lifecycle. PopMCP can also watch for a monitor run finishing or a monitor run failing, so a broken nightly check starts the conversation instead of waiting for someone to ask.

Does this cover Spec Hub and the Private API Network?

Both. create_spec, get_all_specs and get_spec work against API specifications in Postman's Spec Hub, including their spec files. The Private API Network has its own operations, and two of the watchable events live there: someone raising a request to add an element to the team's network, and a workspace or element being published to it. Both of those are polled rather than pushed.

Why does listing collections need a workspace first?

Postman's API requires a workspace ID on the get_collections endpoint — there is no listing call that returns every collection at once. In practice the agent runs get_workspaces, picks the right workspace, then lists inside it, which is why a vague request sometimes takes an extra hop. When you do not know where something lives, search_postman_elements looks across requests, collections, workspaces, specs, flows, environments and mocks in one pass.

Do I have to run or host the Postman MCP server myself?

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Which AI clients can use this MCP server?

Any client that supports a remote Streamable HTTP MCP server — Claude Desktop, Claude Web, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

Why do only 40 of the 118 tools load by default?

Loading 118 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 40-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. You can switch a connection to the full catalog at any time.

What is the difference between a tool and a trigger?

A tool is something your AI calls — there are 118 here. A trigger is something PopMCP watches for you: 14 Postman events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Postman.

Connect Postman to your AI in minutes

Launch a hosted MCP endpoint for Postman, keep tool access under control, and start testing real workflow prompts right away.

Connect your first MCP