Postman MCP integration for AI agents.
Connect AI agents to Postman through 135 structured actions, including get a collections comments, create a collection, delete a collection, and duplicate a…
- ACTION CONTRACTS
- 135
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Postman integration exposes
The Postman Agent App exposes 135 provider-backed actions for developer tools work. Its current contract lets an authorized agent tool to retrieve all comments left by users in an api's collection. use when you need to fetch all comments associated with a specific collection within an api, tool to create a new postman collection in a specific workspace or the default workspace. use when you need to create a collection with workspace specification. for complete collection format details, refer to the postman collection format documentation, and tool to permanently delete a collection from postman. use when you need to remove a collection that is no longer needed. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Postman account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Postman capabilities.
Showing 12 of 135 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_a_collections_commentsREADTool to retrieve all comments left by users in an API's collection. Use when you need to fetch all comments associated with a specific collection within an API.
INPUTS: api_id / collection_id
create_a_collectionWRITETool to create a new Postman collection in a specific workspace or the default workspace. Use when you need to create a collection with workspace specification. For complete collection format details, refer to the Postman Collection Format documentation.
INPUTS: workspace / collection
delete_a_collectionHIGH IMPACTTool to permanently delete a collection from Postman. Use when you need to remove a collection that is no longer needed.
INPUTS: collection_id
duplicate_a_collectionREVIEWTool to create a duplicate of a collection in another workspace. Use when you need to copy an existing collection to a different workspace. Returns an asynchronous task that can be tracked using the duplication task status endpoint.
INPUTS: workspace / collection_id
create_a_collection_commentWRITETool to create a comment on an API's collection. Use when you need to add a comment to a specific collection within an API. To create a reply on an existing comment, include the thread_id in the request.
INPUTS: body / api_id / thread_id / collection_id
create_a_collection_from_a_schemaWRITETool to create a collection from a schema and link it to an API with specified relations. Note: This endpoint is deprecated in Postman v10 and higher. Use when you need to generate a collection from an API schema and establish relations like contract tests or documentation.
INPUTS: name / api_id / relations / schema_id / workspace
create_a_folderWRITETool to create a folder in a Postman collection. Use when you need to organize requests by creating a new folder within a collection. For complete details, see the Postman Collection Format documentation.
INPUTS: name / description / collection_id
create_a_folder_commentWRITETool to create a comment on a folder. Use when you need to add a comment to a specific folder in a collection.
INPUTS: body / folder_uid / collection_uid
create_a_fork2WRITETool to create a fork from an existing environment into a workspace. Use when you need to fork an environment to a specified workspace.
INPUTS: fork_name / workspace / environment_uid
create_a_mock_serverWRITETool to create a new mock server in a Postman collection. Use when you need to create a mock server to simulate API endpoints for testing or development. Returns the created mock server's details including the mockUrl which can be used to make requests.
INPUTS: mock / workspace
create_a_monitorWRITETool to create a new monitor in a specific workspace to run a collection on a schedule. Use when you need to set up automated collection runs at specified intervals using cron expressions within a workspace.
INPUTS: monitor / workspace
create_a_pull_requestWRITETool to create a pull request for a forked collection into its parent collection. Use when you need to propose changes from a forked collection to be merged into the parent collection. The forked collection must exist before creating a pull request.
INPUTS: title / reviewers / description / collection_uid / destination_id
INPUT CONTRACTS
Know what the action needs before it runs.
get_a_collections_comments
api_idREQUIRED- The API's unique identifier (UUID). This identifies the API containing the collection.
collection_idREQUIRED- The collection's unique identifier (UUID). This identifies the specific collection to retrieve comments from.
create_a_collection
workspaceOPTIONAL- Optional workspace ID where the collection will be created. If not specified, the collection is created in the user's default workspace
collectionREQUIRED- Collection object containing info (name, description, schema) and item array (requests/folders)
delete_a_collection
collection_idREQUIRED- The unique identifier (UID) or ID of the collection to delete.
duplicate_a_collection
workspaceREQUIRED- The ID of the workspace where the duplicated collection will be created
collection_idREQUIRED- The unique identifier (UUID) of the collection to duplicate
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get A Collections Comments
Tool to retrieve all comments left by users in an API's collection. Use when you need to fetch all comments associated with a specific collection within an API. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_a_collections_commentsControl Create A Collection
Tool to create a new Postman collection in a specific workspace or the default workspace. Use when you need to create a collection with workspace specification. For complete collection format details, refer to the Postman Collection Format documentation. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_a_collectionVerify with Create A Collection
Tool to create a new Postman collection in a specific workspace or the default workspace. Use when you need to create a collection with workspace specification. For complete collection format details, refer to the Postman Collection Format documentation. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_a_collectionSAFETY BOUNDARY
Operate Postman with explicit limits
- Authorize Postman with API key and grant only the provider access required by the selected actions.
- 63 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_a_collection`, `delete_a_collections_comment`, and `delete_a_folder` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Postman rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Postman task completed successfully.
CONNECTION MODEL
API key
Postman API key used with the X-API-Key header. Generate it from Postman account settings under API keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 59
- WRITE SIGNALS
- 45
- HIGH IMPACT
- 18
- REVIEW SIGNALS
- 13
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Postman.