# How to integrate Postman MCP with OpenCode

```json
{
  "title": "How to integrate Postman MCP with OpenCode",
  "toolkit": "Postman",
  "toolkit_slug": "postman",
  "framework": "OpenCode",
  "framework_slug": "opencode",
  "url": "https://composio.dev/toolkits/postman/framework/opencode",
  "markdown_url": "https://composio.dev/toolkits/postman/framework/opencode.md",
  "updated_at": "2026-03-29T06:46:22.365Z"
}
```

## Introduction

### How to integrate Postman MCP with OpenCode
This guide explains how to connect Postman MCP to OpenCode using Composio Connect, which simplifies OAuth, API changes, and reliability concerns.
There are two ways to set this up:
- Via [Composio Connect MCP](https://dashboard.composio.dev/)
- Via the [Composio CLI](https://dashboard.composio.dev/)

## Also integrate Postman with

- [ChatGPT](https://composio.dev/toolkits/postman/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/postman/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/postman/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/postman/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/postman/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/postman/framework/codex)
- [Cursor](https://composio.dev/toolkits/postman/framework/cursor)
- [VS Code](https://composio.dev/toolkits/postman/framework/vscode)
- [OpenClaw](https://composio.dev/toolkits/postman/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/postman/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/postman/framework/cli)
- [Google ADK](https://composio.dev/toolkits/postman/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/postman/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/postman/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/postman/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/postman/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/postman/framework/crew-ai)

## TL;DR

### Why use Composio?
Composio provides a single MCP server or CLI tool that exposes a set of meta-tools, allowing you to:
- Connect to 1,000+ apps with on-demand tool loading, so you do not fill your LLM context window with unnecessary tool definitions.
- Use programmatic tool calling through a remote Bash tool, letting LLMs write their own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
- Handle large tool responses outside the LLM context to keep conversations lean.

## Connect Postman to OpenCode

### Connect Postman with OpenCode
### Option 1: Using Composio CLI
### 1. Install Composio CLI
Install the Composio CLI, authenticate, and initialize your project:

```bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login
```

## What is the Postman MCP server, and what's possible with it?

The Postman MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Postman account. It provides structured and secure access so your agent can perform Postman operations on your behalf.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `POSTMAN_CREATE_A_COLLECTION` | 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. |
| `POSTMAN_CREATE_A_COLLECTION_COMMENT` | Create a Collection Comment | Tool 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. |
| `POSTMAN_CREATE_A_COLLECTION_FROM_A_SCHEMA` | Create Collection from Schema | Tool 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. |
| `POSTMAN_CREATE_A_FOLDER` | Create a Folder | Tool 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. |
| `POSTMAN_CREATE_A_FOLDER_COMMENT` | Create a Folder Comment | Tool to create a comment on a folder. Use when you need to add a comment to a specific folder in a collection. |
| `POSTMAN_CREATE_A_FORK` | Create a Fork | Tool to create a fork from an existing collection into a workspace. Use when you need to fork a collection to create an independent copy in a specific workspace. |
| `POSTMAN_CREATE_ENVIRONMENT_FORK` | Create Environment Fork | Tool to create a fork from an existing environment into a workspace. Use when you need to fork an environment to a specified workspace. |
| `POSTMAN_CREATE_A_MOCK_SERVER` | Create a Mock Server | Tool 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. |
| `POSTMAN_CREATE_A_MONITOR` | Create a Monitor | Tool 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. |
| `POSTMAN_CREATE_AN_API` | Create an API | Tool to create a new API in Postman. Use when you need to create an API with a name, summary, and description in your Postman workspace. |
| `POSTMAN_CREATE_AN_API` | Create an API | Tool to create a new API in a Postman workspace. Use when you need to create an API with a name and optional summary and description. |
| `POSTMAN_CREATE_AN_ENVIRONMENT` | Create an Environment | Tool to create a new environment in a Postman workspace. Use when you need to create a new environment with variables for different settings (development, production, testing, etc.). Returns the created environment's ID, name, and UID upon successful creation. |
| `POSTMAN_CREATE_A_PULL_REQUEST` | Create a Pull Request | Tool 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. |
| `POSTMAN_CREATE_REQUEST_IN_COLLECTION` | Create Request in Collection | Tool to create a new request in a Postman collection. Use when you need to add a request to an existing collection with specified method, URL, headers, and body. |
| `POSTMAN_CREATE_A_REQUEST_COMMENT` | Create a Request Comment | Tool to create a comment on a request. Use when you need to add a comment to a specific request within a collection or reply to an existing comment thread. |
| `POSTMAN_CREATE_A_RESPONSE` | Create a Response | Tool to create a request response in a Postman collection. Use when you need to add a saved response example to a specific request in a collection. |
| `POSTMAN_CREATE_A_RESPONSE_COMMENT` | Create a Response Comment | Tool to create a comment on a response. Use when you need to add a comment to a specific response within a collection or reply to an existing comment thread. |
| `POSTMAN_CREATE_API_SCHEMA` | Create API Schema | Tool to create a schema for an API in Postman. Use when you need to add a schema definition (such as OpenAPI, GraphQL, or Protocol Buffers) to an existing API. The schema can consist of single or multiple files. Returns the created schema's ID and metadata upon successful creation. |
| `POSTMAN_CREATE_MOCK_SERVER_RESPONSE` | Create Mock Server Response | Tool to create a server response on a Postman mock server. Use when you need to simulate 5xx server-level responses (500, 503, etc.) for testing error conditions. |
| `POSTMAN_CREATE_A_SPEC` | Create a Spec | Tool to create an API specification in Postman's Spec Hub. Use when you need to create single or multi-file specifications in a workspace. Supports various spec types including OpenAPI 3.0, OpenAPI 3.1, and AsyncAPI 2.0. |
| `POSTMAN_CREATE_SPEC_FILE` | Create Spec File | Tool to create a new file in an API specification. Use when you need to add a new file (such as schema definitions, path configurations, or components) to an existing spec. |
| `POSTMAN_CREATE_A_WEBHOOK` | Create a Webhook | Tool to create a webhook that triggers a collection with a custom payload. Use when you need to set up a webhook endpoint that can trigger a Postman collection run. The webhook URL is available in the webhookUrl property of the response. |
| `POSTMAN_CREATE_A_WORKSPACE` | Create a Workspace | Tool to create a new workspace in Postman. Use when you need to create a workspace with a specified name, type (personal, team, private, or public), and optional description. Returns the created workspace's ID, name, and type upon successful creation. |
| `POSTMAN_CREATE_COLLECTION` | Create Collection | Tool to create a new Postman collection with specified name and configuration. Use when you need to create a new collection in Postman workspace. Returns the created collection's ID, name, and UID upon successful creation. |
| `POSTMAN_CREATE_ENVIRONMENT` | Create Environment | Tool to create a new Postman environment with specified name and variables. Use when you need to create a new environment in Postman workspace. Returns the created environment's ID, name, and UID upon successful creation. |
| `POSTMAN_CREATE_MOCK_SERVER` | Create Mock Server | Tool to create a new mock server for a Postman collection. Use when you need to set up a mock server that simulates API responses based on saved examples in a collection. |
| `POSTMAN_CREATE_MONITOR` | Create Monitor | Tool to create a new monitor to run a collection on a schedule. Use when you need to set up automated collection runs at specified intervals using cron expressions. |
| `POSTMAN_CREATE_OR_UPDATE_A_SCHEMA_FILE` | Create or Update a Schema File | Tool to create or update an API schema file in Postman. Use when you need to add a new schema file or modify an existing one within an API schema. Requires API ID, schema ID, file path, and stringified JSON content. |
| `POSTMAN_CREATE_API_VERSION_RELATIONS` | Create API Version Relations | Tool to create new relations for an API version. Use when you need to link collections or mock servers to an API version as contract tests, test suites, documentation, or mocks. |
| `POSTMAN_CREATE_WEBHOOK` | Create Webhook | Tool to create a new webhook for a Postman collection. Use when you need to create a webhook that triggers a collection when called. Returns the created webhook's ID and name upon successful creation. |
| `POSTMAN_DELETE_A_COLLECTION` | Delete a Collection | Tool to permanently delete a collection from Postman. Use when you need to remove a collection that is no longer needed. |
| `POSTMAN_DELETE_A_COLLECTION_S_COMMENT` | Delete a collection's comment | Tool to delete a comment from an API's collection. Use when you need to remove a specific comment from a collection. On success, returns HTTP 204 No Content. |
| `POSTMAN_DELETE_A_FOLDER` | Delete a Folder | Tool to delete a folder in a Postman collection. Use when you need to remove a folder and all its contents from a collection. The folder ID should not contain spaces to avoid 404 errors. |
| `POSTMAN_DELETE_A_FOLDER_S_COMMENT` | Delete a Folder's Comment | Tool to delete a comment from a folder. Use when you need to remove a specific comment from a folder. Returns HTTP 204 No Content on successful deletion. |
| `POSTMAN_DELETE_AN_API` | Delete an API | Tool to delete an API from Postman. Use when you need to permanently remove an API. On success, returns HTTP 204 No Content response. |
| `POSTMAN_DELETE_AN_API_S_COMMENT` | Delete an API's Comment | Tool to delete a comment from an API. Use when you need to remove a comment from a specific API. On success, this returns an HTTP 204 No Content response indicating the comment was successfully deleted. |
| `POSTMAN_DELETE_AN_ENVIRONMENT` | Delete an environment | Tool to delete an environment permanently in Postman. Use when you need to remove an environment that is no longer needed. |
| `POSTMAN_DELETE_A_REQUEST_S_COMMENT` | Delete a Request's Comment | Tool to delete a comment from a request. Use when you need to remove a specific comment from a request. On success, this returns an HTTP 204 No Content response. |
| `POSTMAN_DELETE_A_RESPONSE` | Delete a Response | Tool to delete a response in a Postman collection. Use when you need to remove a saved response from a collection. |
| `POSTMAN_DELETE_A_RESPONSE_S_COMMENT` | Delete a Response's Comment | Tool to delete a comment from a response. Use when you need to remove a specific comment from a collection response. On successful deletion, this returns HTTP 204 No Content. |
| `POSTMAN_DELETE_A_SCHEMA_FILE` | Delete a Schema File | Tool to delete a file in an API schema. Use when you need to remove a specific file from a schema. On success, returns HTTP 204 No Content response. |
| `POSTMAN_DELETE_MOCK_SERVER_RESPONSE` | Delete Mock Server Response | Tool to delete a mock server's server response. Use when you need to remove a specific response from a Postman mock server. |
| `POSTMAN_DELETE_A_SPEC` | Delete a Spec | Tool to delete an API specification from Postman. Use when you need to permanently remove a specification. On success, returns HTTP 204 No Content response. |
| `POSTMAN_DELETE_SPEC_FILE` | Delete Spec File | Tool to delete a file from an API specification. Use when you need to remove a specific file from a multi-file specification. |
| `POSTMAN_DELETE_A_WORKSPACE` | Delete a Workspace | Tool to delete a Postman workspace permanently. Use when you need to remove a workspace and all its contents. Deletion is permanent and cannot be undone. |
| `POSTMAN_DELETE_MONITOR` | Delete Monitor | Tool to delete a monitor by its ID. Use when you need to permanently remove a monitor from Postman. The monitor ID must be provided to identify which monitor to delete. |
| `POSTMAN_DUPLICATE_A_COLLECTION` | Duplicate a Collection | Tool 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. |
| `POSTMAN_FORK_COLLECTION` | Fork Collection | Tool to create a fork of a collection in a specified workspace. Use when you need to fork an existing collection to a workspace. |
| `POSTMAN_GENERATE_COLLECTION_FROM_SPEC` | Generate Collection from Spec | Tool to generate a Postman collection from an OpenAPI 2.0, 3.0, or 3.1 specification. Use when you need to create a collection from an existing API spec. The operation is asynchronous and returns a task ID and polling URL to check the generation status. |
| `POSTMAN_GENERATE_SPEC_FROM_COLLECTION` | Generate Spec from Collection | Tool to generate an API specification from a Postman collection. Use when you need to create an OpenAPI 3.0 specification from an existing collection. The operation is asynchronous and returns a task ID and polling URL to check the generation status. |
| `POSTMAN_GET_BILLING_ACCOUNT_DETAILS` | Get Billing Account Details | Tool to retrieve Postman billing account details for the authenticated team. Use when you need to access account information such as account ID, team ID, account state, billing slots, sales channel, or billing email. |
| `POSTMAN_GET_COLLECTION_COMMENTS` | Get Collection 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. |
| `POSTMAN_GET_COLLECTION_S_FORKS` | Get Collection's Forks | Tool to get all forks of a specific collection. Use when you need to retrieve information about who has forked a collection, including fork IDs, users, and creation dates. |
| `POSTMAN_GET_COLLECTION_PULL_REQUESTS` | Get Collection Pull Requests | Tool to get information about a collection's pull requests including source and destination IDs, status, and URLs. Use when you need to retrieve pull request details for a specific collection. |
| `POSTMAN_GET_COLLECTION_ROLES` | Get Collection Roles | Tool to get information about all roles in a collection. Use when you need to retrieve the IDs of all users, teams, and groups with access to view or edit a collection. |
| `POSTMAN_GET_FOLDER_INFORMATION` | Get Folder Information | Tool to retrieve information about a folder in a Postman collection. Use when you need to fetch details about a specific folder including its name, description, owner, and timestamps. |
| `POSTMAN_GET_FOLDER_COMMENTS` | Get Folder Comments | Tool to retrieve all comments left by users in a folder. Use when you need to fetch all comments associated with a specific folder within a collection. |
| `POSTMAN_GET_ALL_API_RELEASES` | Get All API Releases | Tool to get all releases for a specific API version in Postman. Use when you need to list releases for an API version. Note: This endpoint is deprecated in Postman v10 and higher. |
| `POSTMAN_GET_ALL_APIS` | Get All APIs | Tool to get all APIs accessible to the authenticated user with optional workspace filtering. Use when you need to list or retrieve APIs from Postman. Returns an array of API objects with their IDs, names, summaries, and other metadata. |
| `POSTMAN_GET_ALL_APIS_IN_WORKSPACE` | Get All APIs in Workspace | Tool to get all APIs in a specific Postman workspace. Use when you need to list or retrieve APIs from a workspace. Returns an array of API objects with their details. |
| `POSTMAN_GET_ALL_COLLECTIONS` | Get All Collections | Tool to get all collections accessible to the authenticated user with optional workspace filtering. Use when you need to list or retrieve collections from Postman. Returns an array of collection objects with their IDs, names, and UIDs. |
| `POSTMAN_GET_ALL_COLLECTIONS` | Get All Collections | Tool to get all collections accessible to the authenticated user. Use when you need to retrieve all your collections including subscribed collections. Returns detailed information for each collection including owner, creation/update timestamps, and visibility. |
| `POSTMAN_GET_ALL_ENVIRONMENTS` | Get All Environments | Tool to get all environments accessible to the authenticated user with optional workspace filtering. Use when you need to list or retrieve environments from Postman. Returns an array of environment objects with their IDs, names, and UIDs. |
| `POSTMAN_GET_ALL_FORKED_COLLECTIONS` | Get All Forked Collections | Tool to retrieve all forked collections for the authenticated user. Use when you need to list or access all collections that the user has forked. |
| `POSTMAN_GET_ALL_GROUPS` | Get All Groups | Tool to get all user groups in a Postman team. Use when you need to list all groups and their details including member counts and timestamps. Returns an array of group objects with their IDs, names, team IDs, user counts, and creation/update timestamps. |
| `POSTMAN_GET_ALL_LINKED_RELATIONS` | Get All Linked Relations | Tool to retrieve all linked relations for a specific API version in Postman. Use when you need to discover what collections, documentation, mocks, or monitors are linked to an API version. |
| `POSTMAN_GET_ALL_MOCK_SERVERS` | Get All Mock Servers | Tool to get all active mock servers accessible to the authenticated user. Use when you need to list or retrieve mock servers from Postman. By default, returns only mock servers you created across all workspaces. Can be filtered by workspace ID to get mock servers specific to a workspace. |
| `POSTMAN_GET_ALL_MONITORS` | Get All Monitors | Tool to get all monitors accessible to the authenticated user with optional workspace filtering. Use when you need to list or retrieve monitors from Postman. Returns an array of monitor objects with their IDs, names, and UIDs. |
| `POSTMAN_GET_ALL_WORKSPACE_ROLES` | Get All Workspace Roles | Tool to get information about all roles in a workspace based on the team's plan. Use when you need to retrieve the IDs of all users with different roles (Editor, Admin, Viewer) in a workspace. |
| `POSTMAN_GET_ALL_API_SPECIFICATIONS` | Get All API Specifications | Tool to get all API specifications in a workspace. Use when you need to list or retrieve API specs from a specific Postman workspace. Returns an array of spec objects with their IDs, names, types, and timestamps, along with pagination metadata. |
| `POSTMAN_GET_ALL_TEAM_USERS` | Get All Team Users | Tool to get information about all users on the Postman team. Use when you need to list all team members and their details including roles and join dates. Returns an array of user objects with their IDs, names, usernames, emails, roles, and join timestamps. |
| `POSTMAN_GET_ALL_TEST_RELATIONS` | Get All Test Relations | Tool to retrieve all test relations for a specific API version. Use when you need to get test relations associated with an API version. Note: This endpoint is deprecated in Postman v10 and higher. |
| `POSTMAN_GET_ALL_API_VERSIONS` | Get All API Versions | Tool to get all published versions of a specific API in Postman. Use when you need to list or retrieve version information for an API. Returns an array of version objects with their IDs and names. |
| `POSTMAN_GET_ALL_WORKSPACES` | Get All Workspaces | Tool to get all workspaces accessible to the authenticated user with optional type filtering. Use when you need to list or retrieve workspaces from Postman. Returns an array of workspace objects with their IDs, names, and types. |
| `POSTMAN_GET_MONITOR_INFORMATION` | Get Monitor Information | Tool to retrieve information about a specific monitor in Postman. Use when you need to fetch monitor details including schedule, collection, environment, and run status. |
| `POSTMAN_GET_API_INFORMATION` | Get API Information | Tool to retrieve information about a specific API in Postman. Use when you need to fetch API details including name, description, versions, and schemas. |
| `POSTMAN_GET_API_COMMENTS` | Get API Comments | Tool to retrieve all comments left by users in an API. Use when you need to fetch all comments associated with a specific API. |
| `POSTMAN_GET_API_VERSION` | Get API Version | Tool to get information about a specific API version in Postman. Use when you need to retrieve details about a particular version of an API. Returns version details including ID, name, creation date, and associated schemas. |
| `POSTMAN_GET_AN_ENVIRONMENT` | Get an Environment | Tool to retrieve detailed information about a specific environment in Postman. Use when you need to fetch environment details including name, ID, owner, and all environment variables. |
| `POSTMAN_GET_ENVIRONMENT_FORKS` | Get Environment Forks | Tool to retrieve all forked environments for a specific environment. Use when you need to list all environments that have been forked from a particular environment. |
| `POSTMAN_GET_REQUEST_INFORMATION` | Get Request Information | Tool to retrieve information about a specific request in a Postman collection. Use when you need to fetch details about a request including its method, URL, headers, body, authentication, and associated scripts. |
| `POSTMAN_GET_REQUEST_COMMENTS` | Get Request Comments | Tool to retrieve all comments left by users in a request. Use when you need to fetch all comments associated with a specific request within a collection. |
| `POSTMAN_GET_RESPONSE_INFORMATION` | Get Response Information | Tool to retrieve information about a saved response in a Postman collection. Use when you need to fetch details about a specific response including status, headers, body, and metadata. |
| `POSTMAN_GET_RESPONSE_COMMENTS` | Get Response Comments | Tool to retrieve all comments left by users in a response. Use when you need to fetch all comments associated with a specific response within a collection. |
| `POSTMAN_GET_API_SCHEMA` | Get API Schema | Tool to retrieve information about an API schema from Postman. Use when you need to fetch schema details for a specific API. Optionally specify a version ID to get a schema published in a specific API version. |
| `POSTMAN_GET_API_SPECIFICATION` | Get API Specification | Tool to retrieve information about an API specification in Postman. Use when you need to fetch spec details including name, type, and timestamps. |
| `POSTMAN_GET_SPEC_FILE_CONTENTS` | Get Spec File Contents | Tool to get the contents of an API specification's file. Use when you need to retrieve the actual content and metadata of a specific file within a spec. |
| `POSTMAN_GET_SPEC_DEFINITION` | Get Spec Definition | Tool to get the complete contents of an API specification's definition. Use when you need to retrieve the full OpenAPI/Swagger specification content for a spec. Returns the raw definition content as a string. |
| `POSTMAN_GET_SPECIFICATION_FILES` | Get Specification Files | Tool to retrieve all files in an API specification from Postman. Use when you need to list or view specification files for a specific spec ID. Returns file metadata including IDs, names, paths, types, and timestamps. |
| `POSTMAN_GET_SPEC_S_GENERATED_COLLECTIONS` | Get Spec's Generated Collections | Tool to retrieve all collections generated from an API specification in Postman. Use when you need to fetch collections that have been auto-generated from a spec. Returns metadata and an array of generated collections. |
| `POSTMAN_GET_ASYNC_COLLECTION_UPDATE_STATUS` | Get Async Collection Update Status | Tool to get the status of an asynchronous collection update task. Use when you need to check whether a previously initiated async collection update is still processing, has completed successfully, or has failed. The task ID is obtained from PUT /collections/{collectionId} endpoint when using the Prefer: respond-async header. |
| `POSTMAN_GET_TEAM_USER` | Get Team User | Tool to get information about a user on the Postman team. Use when you need to retrieve details about a specific team member including their ID, name, email, roles, and join date. |
| `POSTMAN_GET_AUTHENTICATED_USER` | Get Authenticated User | Tool to get information about the authenticated user. Use when you need to retrieve details about the current authenticated user, including their user ID, username, and email address. |
| `POSTMAN_GET_WORKSPACE_DETAILS` | Get Workspace Details | Tool to get detailed information about a specific workspace by its ID. Use when you need to retrieve the complete structure of a workspace including all collections, environments, APIs, mocks, and monitors. |
| `POSTMAN_GET_WORKSPACE_ACTIVITY_FEED` | Get Workspace Activity Feed | Tool to get a workspace's activity feed showing who added or removed collections, environments, or elements, and users joining or leaving. Use when you need to track workspace changes and user activity. |
| `POSTMAN_GET_WORKSPACE_ROLES` | Get Workspace Roles | Tool to get the roles of users, user groups, and partners in a workspace. Use when you need to retrieve role assignments and understand who has what level of access to a specific workspace. |
| `POSTMAN_GET_COLLECTION_ACCESS_KEYS` | Get Collection Access Keys | Tool to retrieve all personal and team collection access keys for the authenticated user. Use when you need to list or manage collection access keys. Returns an array of access key objects with their IDs, tokens, status, and associated collection information. |
| `POSTMAN_GET_CONTRACT_TEST_RELATIONS` | Get Contract Test Relations | Tool to retrieve contract test relations for a specific API version. Use when you need to check contract test associations. Note: This endpoint is deprecated and may return limited or no data. |
| `POSTMAN_GET_DOCUMENTATION_RELATIONS` | Get documentation relations | Tool to get documentation relations for a specific API version. This endpoint is deprecated in Postman v10 and higher. |
| `POSTMAN_GET_DUPLICATION_TASK_STATUS` | Get Duplication Task Status | Tool to get the status of a collection duplication task. Use when you need to check whether a previously initiated collection duplication is still processing or has completed. The task ID must first be obtained from the POST /collections/{collectionId}/duplicates endpoint. |
| `POSTMAN_GET_ENVIRONMENT_RELATIONS` | Get Environment Relations | Tool to get environment relations for a specific API version. This endpoint is deprecated in Postman v10 and higher. |
| `POSTMAN_GET_GENERATED_SPECIFICATION` | Get Generated Specification | Tool to retrieve the API specification generated for a Postman collection. Use when you need to fetch OpenAPI/Swagger specs that have been auto-generated from a collection. Returns metadata and an array of generated specifications. |
| `POSTMAN_GET_WORKSPACE_GLOBAL_VARIABLES` | Get Workspace Global Variables | Tool to get a workspace's global variables. Use when you need to retrieve global variables that are available throughout a workspace for access between collections, requests, scripts, and environments. Note that this endpoint only works with personal or team workspaces, not public workspaces. |
| `POSTMAN_GET_INTEGRATION_TEST_RELATIONS` | Get Integration Test Relations | Tool to get integration test relations for a specific API version. This endpoint is deprecated and may not return active data. |
| `POSTMAN_GET_RESOURCE_TYPES` | Get Resource Types | Tool to get all resource types supported by Postman's SCIM API. Use when you need to discover what resource types (e.g., User, Group) are available in the SCIM API and their corresponding endpoints and schemas. |
| `POSTMAN_GET_SCHEMA_FILE_CONTENTS` | Get Schema File Contents | Tool to get the contents of an API schema file at a specified path. Use when you need to retrieve the actual content of a schema file. Optionally specify a version ID to get file contents from a specific API version. |
| `POSTMAN_GET_SCHEMA_FILES` | Get Schema Files | Tool to retrieve files in an API schema from Postman. Use when you need to list or view schema files for a specific API and schema ID. Optionally filter by version ID to get files from a particular API version. |
| `POSTMAN_GET_SERVICE_PROVIDER_CONFIGURATION` | Get Service Provider Configuration | Tool to get Postman's SCIM API service provider configuration information. Use when you need to discover supported SCIM operations, capabilities, and authentication schemes. This endpoint returns configuration details including support for PATCH, bulk operations, filtering, sorting, and ETag handling. |
| `POSTMAN_GET_SOURCE_COLLECTION_STATUS` | Get Source Collection Status | Tool to check whether there is a change between a forked collection and its parent (source) collection. Use when you need to determine if the source collection has updates that are not yet in the forked collection. This endpoint only works with forked collections; attempting to use it with regular collections will result in an error. |
| `POSTMAN_GET_TEST_SUITE_RELATIONS` | Get Test Suite Relations | Tool to get test suite relations for a specific API version. Use when you need to retrieve the test suites associated with an API version. Note: This endpoint is deprecated and only works with legacy v9 APIs. For v10+ APIs, this returns an empty array. |
| `POSTMAN_GET_UNCLASSIFIED_RELATIONS` | Get Unclassified Relations | Tool to get unclassified relations for an API version in Postman. Use when you need to retrieve unclassified relations for a specific API version. This endpoint is for Postman v10 and higher. |
| `POSTMAN_IMPORT_OPENAPI_DEFINITION` | Import OpenAPI Definition | Tool to import an OpenAPI definition into Postman as a new collection. Use when you need to convert an OpenAPI specification into a Postman collection within a specific workspace. |
| `POSTMAN_IMPORT_OPENAPI_SPECIFICATION` | Import OpenAPI Specification | Tool to import an OpenAPI specification into Postman as a new collection. Use when you need to convert an OpenAPI 3.0+ specification into a Postman collection within a specific workspace. The imported specification will be automatically converted to a Postman collection with all endpoints, request parameters, and documentation. |
| `POSTMAN_LIST_ACCOUNT_INVOICES` | List Account Invoices | Tool to get all invoices for a Postman billing account filtered by status. Use when you need to retrieve invoice history for an account. The account ID must first be obtained from the GET /accounts endpoint. |
| `POSTMAN_MERGE_A_FORK` | Merge a Fork | Tool to merge a forked collection back into its parent collection. This endpoint is deprecated. Use when you need to merge changes from a forked collection into the parent collection. |
| `POSTMAN_MERGE_A_FORKED_ENVIRONMENT` | Merge a forked environment | Tool to merge a forked environment back into its parent environment. Use when you need to merge changes from a forked environment into the parent. |
| `POSTMAN_PUBLISH_A_MOCK_SERVER` | Publish a Mock Server | Tool to publish a mock server in Postman. Use when you need to make a mock server publicly accessible. Publishing sets the mock server's Access Control configuration to public. |
| `POSTMAN_PULL_SOURCE_CHANGES_INTO_FORK` | Pull Source Changes into Fork | Tool to pull changes from a parent (source) collection into a forked collection. Use when you need to sync a forked collection with its parent. |
| `POSTMAN_REPLACE_AN_ENVIRONMENT_S_DATA` | Replace an Environment's Data | Tool to completely replace an environment's data with new variables and values. Use when you need to update an entire environment by replacing all its contents. This operation replaces ALL existing variables with the ones provided in the request. |
| `POSTMAN_REPLACE_COLLECTION_DATA_ASYNCHRONOUSLY` | Replace Collection Data Asynchronously | Tool to replace the entire contents of a collection asynchronously. Use when you need to completely replace a collection with new data. IMPORTANT: Include the collection's ID values in item, variable, and other nested objects to preserve them. If you do not include IDs, existing items will be removed and new items will be created. |
| `POSTMAN_RESOLVE_A_COMMENT_THREAD` | Resolve a Comment Thread | Tool to resolve a comment thread and any associated replies. Use when you need to mark a comment thread as resolved. On success, this returns an HTTP 204 No Content response. |
| `POSTMAN_REVIEW_A_PULL_REQUEST` | Review a Pull Request | Tool to update the review status of a pull request by approving, declining, or unapproving it. Use when you need to perform a review action on a Postman pull request. |
| `POSTMAN_RUN_A_MONITOR` | Run a Monitor | Tool to trigger an immediate run of a monitor and retrieve its execution results. Use when you need to manually execute a monitor outside of its scheduled runs. |
| `POSTMAN_SYNC_COLLECTION_WITH_API_SCHEMA` | Sync Collection with API Schema | Tool to sync a collection attached to an API with the API schema. This is an asynchronous endpoint that returns HTTP 202 Accepted. Use when you need to synchronize a collection with changes made to the API schema. The collection must already be attached to the API. Returns a task ID that can be used to check the status of the sync operation. |
| `POSTMAN_SYNC_COLLECTION_WITH_SPECIFICATION` | Sync Collection with Specification | Tool to sync a collection generated from an API specification. This is an asynchronous operation that returns HTTP 202 Accepted. Use when you need to update a collection to match the latest version of its source API specification. The collection must have been generated from a spec. |
| `POSTMAN_SYNC_SPEC_WITH_COLLECTION` | Sync Spec with Collection | Tool to sync an API specification with a linked collection. This is an asynchronous operation that returns HTTP 202 Accepted with task tracking information. Use when you need to synchronize changes from a spec to its generated collection. Prerequisites: the collection must be generated from the spec, and the spec must be single-file. |
| `POSTMAN_TRANSFER_FOLDERS` | Transfer Folders | Tool to copy or move folders into a collection or folder. Use when you need to reorganize collections by transferring folders between collections or into other folders. |
| `POSTMAN_TRANSFORM_COLLECTION_TO_OPENAPI` | Transform Collection to OpenAPI | Tool to transform an existing Postman Collection into a stringified OpenAPI 3.0.3 definition. Use when you need to convert a collection to OpenAPI format for API documentation or interoperability with other tools. |
| `POSTMAN_UPDATE_A_FOLDER` | Update a Folder | Tool to update a folder in a Postman collection. Use when you need to modify the name or description of an existing folder. For complete properties and information, see the Postman Collection Format documentation. |
| `POSTMAN_UPDATE_A_FOLDER_S_COMMENT` | Update a Folder's Comment | Tool to update a comment on a folder. Use when you need to modify the text content of an existing comment on a specific folder in a collection. |
| `POSTMAN_UPDATE_A_MOCK_SERVER` | Update a Mock Server | Tool to update an existing mock server. Use when you need to change a mock server's name, collection, environment, or privacy settings. The collection UID is required for all updates. |
| `POSTMAN_UPDATE_A_MONITOR` | Update a Monitor | Tool to update an existing monitor in Postman. Use when you need to modify monitor properties like name, active status, collection, environment, options, notifications, or distribution settings. |
| `POSTMAN_UPDATE_AN_API` | Update an API | Tool to update an existing API in Postman. Use when you need to modify the name, summary, or description of an API. |
| `POSTMAN_UPDATE_AN_API_S_COMMENT` | Update an API's Comment | Tool to update a comment on an API. Use when you need to modify the text content of an existing comment on a specific API. |
| `POSTMAN_UPDATE_AN_ENVIRONMENT` | Update an Environment | Tool to update specific environment properties using JSON Patch operations (RFC 6902). Use when you need to modify environment name or variables without replacing the entire environment. |
| `POSTMAN_UPDATE_A_PULL_REQUEST` | Update a Pull Request | Tool to update an open pull request in Postman. Use when you need to modify the title, description, source, destination, or reviewers of an existing pull request. All fields must be provided in the request. |
| `POSTMAN_UPDATE_REQUEST_IN_COLLECTION` | Update Request in Collection | Tool to update a request in a Postman collection. Use when you need to modify an existing request's name, method, URL, headers, or body following the Postman Collection Format. |
| `POSTMAN_UPDATE_A_REQUEST_S_COMMENT` | Update a Request's Comment | Tool to update a comment on a request. Use when you need to modify the text content of an existing comment on a specific request within a collection. |
| `POSTMAN_UPDATE_A_RESPONSE` | Update a Response | Tool to update a response in a Postman collection. Use when you need to modify properties of an existing saved response example such as name, status, code, headers, cookies, or body. |
| `POSTMAN_UPDATE_A_RESPONSE_S_COMMENT` | Update a Response's Comment | Tool to update a comment on a response. Use when you need to modify the text content of an existing comment on a specific response within a collection. |
| `POSTMAN_UPDATE_A_SERVER_RESPONSE` | Update a Server Response | Tool to update a mock server's server response. Use when you need to modify properties of an existing server response such as name, status code, language, body, or headers. At least one property must be included in the update request. |
| `POSTMAN_UPDATE_SPEC_FILE` | Update Spec File | Tool to update an API specification file's content. Use when you need to modify the contents of a specific file within a spec. |
| `POSTMAN_UPDATE_SPEC_PROPERTIES` | Update Spec Properties | Tool to update an API specification's properties such as its name. Use when you need to modify metadata of an existing spec. |
| `POSTMAN_UPDATE_A_WORKSPACE` | Update a Workspace | Tool to update an existing workspace in Postman. Use when you need to modify the name, type, or description of a workspace. The 'type' field is required for all updates. |
| `POSTMAN_UPDATE_WORKSPACE_GLOBAL_VARIABLES` | Update Workspace Global Variables | Tool to update and replace a workspace's global variables. Use when you need to set or replace all global variables in a workspace. Note: This endpoint replaces all existing global variables with the provided list. |
| `POSTMAN_UPDATE_COLLECTION_PROPERTIES` | Update Collection Properties | Tool to update specific collection properties like name, description, authentication, variables, or events. Use when you need to partially update a collection without replacing the entire collection structure. Returns the updated collection information after the changes are applied. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

Once connected, OpenCode can access the Postman MCP server via Composio to run the app actions you authorize, directly from your coding workflow.

## Complete Code

None listed.

## Conclusion

### Way Forward
Now that Postman is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.
- Connect Calendar to turn threads into scheduled meetings automatically.
- Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
- Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
- Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.
Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

## How to build Postman MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/postman/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/postman/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/postman/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/postman/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/postman/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/postman/framework/codex)
- [Cursor](https://composio.dev/toolkits/postman/framework/cursor)
- [VS Code](https://composio.dev/toolkits/postman/framework/vscode)
- [OpenClaw](https://composio.dev/toolkits/postman/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/postman/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/postman/framework/cli)
- [Google ADK](https://composio.dev/toolkits/postman/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/postman/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/postman/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/postman/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/postman/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/postman/framework/crew-ai)

## Related Toolkits

- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.
- [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences.
- [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.
- [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure.
- [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure.
- [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.
- [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Postman MCP?

With a standalone Postman MCP server, the agents and LLMs can only access a fixed set of Postman tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Postman and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with OpenCode?

Yes, you can. OpenCode fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Postman tools.

### Can I manage the permissions and scopes for Postman while using Tool Router?

Yes, absolutely. You can configure which Postman scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Postman data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)