Postman MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTMAN_API_KEY | Yes | Postman API Key (format: PMAK-xxxxx-xxxxx). Get from Postman Account Settings. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_collectionsB | List all Postman collections |
| get_collectionC | Get details of a specific Postman collection by ID |
| create_requestB | Create a new API request in a Postman collection |
| update_requestC | Update an existing API request in a Postman collection |
| delete_requestC | Delete an API request from a Postman collection |
| create_collectionC | Create a new Postman collection |
| create_folderC | Create a new folder in a Postman collection |
| sync_from_controllerB | Auto-migrate API endpoint from .NET controller code to Postman |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose targeting specific Postman entities (collections, folders, requests) with unambiguous actions. There is no overlap between tools like create_collection, create_folder, and create_request, which operate on different resources.
All tools follow a consistent verb_noun pattern using snake_case (e.g., create_collection, list_collections, update_request). The naming is predictable and uniform across all eight tools, making them easy to identify and use.
With 8 tools, the server is well-scoped for managing Postman collections and requests. Each tool serves a clear purpose in the domain, covering essential operations without being overly sparse or bloated, which is appropriate for this functionality.
The tool set provides strong CRUD coverage for collections and requests, including create, get, list, update, and delete operations. However, there are minor gaps such as missing update/delete for collections and folders, and the sync_from_controller tool stands out as a specialized feature not fully integrated into the core workflow.