postman-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTMAN_API_KEY | Yes | Postman API Key used to authenticate with the Postman API. Can be generated at https://go.postman.co/settings/me/api-keys |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspacesC | List all workspaces |
| get_workspaceB | Get details of a specific workspace |
| list_environmentsB | List all environments in a workspace. If workspace not specified, lists environments in "My Workspace". |
| get_environmentB | Get details of a specific environment |
| create_environmentB | Create a new environment in a workspace. Creates in "My Workspace" if workspace not specified. |
| update_environmentA | Update an existing environment. Only include variables that need to be modified. |
| delete_environmentB | Delete an environment |
| fork_environmentB | Create a fork of an environment in a workspace |
| get_environment_forksB | Get a list of environment forks |
| merge_environment_forkB | Merge a forked environment back into its parent |
| pull_environmentB | Pull changes from parent environment into forked environment |
| list_collectionsA | List all collections in a workspace. Supports filtering and pagination. |
| get_collectionC | Get details of a specific collection |
| create_collectionB | Create a new collection in a workspace. Supports Postman Collection v2.1.0 format. |
| update_collectionA | Update an existing collection. Full collection replacement with maximum size of 20 MB. |
| patch_collectionA | Partially update a collection. Only updates provided fields. |
| create_collection_folderB | Create a new folder in a collection |
| get_collection_folderC | Get details of a specific folder in a collection |
| update_collection_folderA | Update a folder in a collection. Acts like PATCH, only updates provided values. |
| create_collection_requestB | Create a new request in a collection |
| get_collection_requestB | Get details of a specific request in a collection |
| update_collection_requestA | Update a request in a collection. Cannot change request folder. |
| create_collection_responseC | Create a new response in a collection |
| get_collection_responseB | Get details of a specific response in a collection |
| update_collection_responseA | Update a response in a collection. Acts like PATCH, only updates provided values. |
| fork_collectionB | Fork a collection to a workspace |
| get_collection_forksB | Get a list of collection forks |
| merge_collection_forkB | Merge a forked collection back into its parent |
| pull_collection_changesB | Pull changes from parent collection into forked collection |
| transfer_collection_itemsC | Transfer items between collections |
| get_user_infoB | Get information about the authenticated user |
| list_apisC | List all APIs in a workspace |
| get_apiC | Get details of a specific API |
| create_apiC | Create a new API |
| update_apiC | Update an existing API |
| delete_apiB | Delete an API |
| add_api_collectionC | Add a collection to an API |
| get_api_collectionC | Get a specific collection from an API |
| create_api_schemaC | Create a schema for an API |
| get_api_schemaC | Get a specific schema from an API |
| create_api_versionB | Create a new version of an API |
| get_api_versionsC | Get all versions of an API |
| get_api_versionB | Get a specific version of an API |
| update_api_versionC | Update an API version |
| delete_api_versionC | Delete an API version |
| get_api_commentsB | Get comments for an API |
| create_api_commentB | Create a new comment on an API (max 10,000 characters) |
| update_api_commentB | Update an existing API comment (max 10,000 characters) |
| delete_api_commentC | Delete an API comment |
| get_api_tagsB | Get tags for an API |
| update_api_tagsB | Update tags for an API |
| get_api_schema_filesC | Get files in an API schema |
| get_schema_file_contentsC | Get contents of a schema file |
| create_update_schema_fileC | Create or update a schema file |
| delete_schema_fileB | Delete a schema file |
| sync_collection_with_schemaC | Sync a collection with its schema |
| get_task_statusC | Get status of an asynchronous task |
| list_collection_access_keysB | List collection access keys with optional filtering by collection ID |
| delete_collection_access_keyD | Delete a collection access key |
| list_workspace_rolesA | Get all available workspace roles based on team's plan |
| get_workspace_rolesC | Get roles for a specific workspace |
| update_workspace_rolesB | Update workspace roles for users and groups (limited to 50 operations per call) |
| get_collection_rolesC | Get roles for a collection |
| update_collection_rolesB | Update collection roles (requires EDITOR role) |
| get_authenticated_userB | Get authenticated user information |
| get_accountsB | Gets Postman billing account details for the given team |
| list_account_invoicesB | Gets all invoices for a Postman billing account filtered by status |
| resolve_comment_threadB | Resolves a comment and any associated replies |
| list_pan_elementsC | Get all elements and folders in Private API Network |
| add_pan_elementB | Add element or folder to Private API Network |
| update_pan_elementC | Update element or folder in Private API Network |
| remove_pan_elementB | Remove element or folder from Private API Network |
| create_webhookB | Creates webhook that triggers collection with custom payload |
| get_tagged_elementsC | Get elements by tag |
| get_workspace_tagsC | Get workspace tags |
| update_workspace_tagsD | Update workspace tags |
| health_checkA | Perform a local system health check to verify Postman MCP server configuration and connectivity. Returns system information and configuration status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| list_workspaces | Show all available workspaces and their details |
| list_collections | Show all collections across workspaces |
| list_environments | Show all environments and their variables |
| analyze_collection | Analyze a Postman collection for potential improvements and best practices |
| document_api | Generate documentation for an API based on its collection and schema |
| suggest_tests | Suggest test cases for API endpoints in a collection |
| review_environment | Review environment variables for security and completeness |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Postman Workspaces | List of all available Postman workspaces |
| Current User | Information about the currently authenticated user |
| Postman APIs | List of all available API definitions |
| Postman Collections | List of all available request collections |
| Postman Environments | List of all available environments |
| Collection Roles | List of roles and permissions for collections |
| Workspace Roles | List of roles and permissions for workspaces |
| Collection Access Keys | List of access keys for collections |
| Private API Network Elements | List of elements in the Private API Network |
| Webhooks | List of configured webhooks |
| Tagged Elements | List of elements with specific tags |
| Workspace Tags | List of tags used in workspaces |
| API Tags | List of tags used in APIs |
TDQS
Scored across 77 tools
Most tools have distinct purposes targeting specific resources and actions, such as create_api vs. update_api or get_collection vs. list_collections. However, some overlap exists, like get_authenticated_user and get_user_info, which could cause confusion despite slight differences in scope. Overall, the toolset is well-organized with clear boundaries for the majority of operations.
Tool names follow a highly consistent verb_noun pattern throughout, such as create_api, get_api, update_api, and delete_api. This consistency extends across all resources like collections, environments, and workspaces, making the toolset predictable and easy to navigate. Minor deviations like health_check or get_tagged_elements still adhere to the overall naming convention.
With 77 tools, the count is excessive for typical MCP server purposes, making it overwhelming and difficult for agents to manage efficiently. While Postman's API is feature-rich, this many tools suggests poor scoping or unnecessary granularity, such as separate tools for every minor operation like get_collection_folder and get_collection_request. A more consolidated approach would improve usability.
The toolset provides comprehensive CRUD and lifecycle coverage for Postman's domain, including APIs, collections, environments, workspaces, and related features like comments, forks, and webhooks. It supports all essential operations from creation to deletion, with no apparent gaps that would hinder agent workflows. The inclusion of niche tools like sync_collection_with_schema and health_check further enhances completeness.