postman-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTMAN_API_KEY | Yes | Your Postman API key from https://postman.com/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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getAuthenticatedUserA | Gets information about the authenticated user. Use this to get current user context (user.id, username, teamId, roles) for 'my ...' requests. |
| getEnabledToolsA | IMPORTANT: Run this first when a requested tool is unavailable. Returns info about enabled tools in full and minimal sets. |
| createCollectionA | Creates a collection using the Postman Collection v2.1.0 schema format. If workspace is not specified, creates in the oldest personal workspace. |
| getCollectionA | Get information about a collection. Returns lightweight collection map by default. Use model='minimal' for root-level IDs only, or model='full' for complete payload. |
| getCollectionsA | Gets all collections in a workspace. Workspace ID is required - ask user if not provided. |
| putCollectionA | Replaces collection contents using Postman Collection v2.1.0 format. Include ID values or they'll be removed and recreated. Max size 100MB. |
| duplicateCollectionB | Duplicates a collection to another workspace. Returns a task ID - use getDuplicateCollectionTaskStatus to check status. |
| getDuplicateCollectionTaskStatusC | Gets the status of a collection duplication task. |
| createCollectionRequestB | Creates a request in a collection. Recommended to pass 'name' property. See Postman Collection Format docs for full properties. |
| updateCollectionRequestA | Updates a request in a collection (PATCH-like: only updates provided fields). Cannot change folder. Use collection ID (not UID). |
| createCollectionResponseC | Creates a request response in a collection. Recommended to pass 'name' property. See Response entry in Postman Collection Format docs. |
| createEnvironmentB | Creates an environment. Max size 30MB. If workspace not specified, creates in oldest personal workspace. |
| getEnvironmentC | Gets information about an environment. |
| getEnvironmentsB | Gets all environments. Optionally filter by workspace. |
| putEnvironmentA | Replaces all environment contents. Max size 30MB. |
| createMockA | Creates a mock server for a collection. Use collection UID (ownerId-collectionId). Use workspace param to specify target workspace. |
| getMockB | Gets information about a mock server, including associated collection UID and mockUrl. |
| getMocksA | Gets all active mock servers. Always pass workspace or teamId. Prefer workspace when known. Set teamId from GET /me (me.teamId) for team scope. |
| updateMockA | Updates a mock server (name, environment, privacy, default response). |
| publishMockA | Publishes a mock server (sets Access Control to public). |
| createSpecA | Creates an API spec in Postman's Spec Hub. Supports OpenAPI 2.0/3.0/3.1, AsyncAPI 2.0, protobuf 2/3, GraphQL. Max file size 10MB. |
| getSpecC | Gets information about an API specification. |
| getAllSpecsC | Gets all API specifications in a workspace. |
| updateSpecPropertiesB | Updates an API spec's properties (e.g., name). |
| getSpecDefinitionB | Gets the complete contents of an API spec's definition. |
| createSpecFileA | Creates an API spec file. Use '/' in path to create folders. File assigned DEFAULT type. Max size 10MB. |
| getSpecFilesC | Gets all files in an API specification. |
| getSpecFileB | Gets the contents of an API spec's file. |
| updateSpecFileA | Updates an API spec's file. Only pass one property at a time (content, name, or type). Max size 10MB. |
| generateCollectionA | Creates a collection from an API spec. Returns polling link to task status. |
| getSpecCollectionsB | Gets all collections generated from an API spec. |
| generateSpecFromCollectionB | Generates an API spec for a collection. Returns polling link to task status. |
| getGeneratedCollectionSpecsC | Gets the API spec generated for a collection. |
| syncCollectionWithSpecA | Syncs a collection generated from an API spec. Async endpoint returns 202. Only for OpenAPI 2.0/3.0/3.1. |
| syncSpecWithCollectionB | Syncs an API spec linked to a collection. Async endpoint returns 202. Only for OpenAPI 2.0/3.0/3.1. |
| createWorkspaceA | Creates a new workspace. Private/Partner workspaces require Team/Enterprise. Public names must be unique. Pass teamId if Organizations is enabled. |
| getWorkspaceB | Gets information about a workspace (visibility: personal/team/private/public/partner). |
| getWorkspacesA | Gets all accessible workspaces. For 'my ...' requests, call GET /me first and pass createdBy={me.user.id}. Paginated with cursor. |
| updateWorkspaceA | Updates a workspace property (name, visibility, etc.). Some visibility changes not allowed. Public names must be unique. |
| getTaggedEntitiesB | Gets Postman entities by tag. Enterprise only - returns 404 on Free/Basic/Professional plans. |
| runCollectionB | Runs a Postman collection with detailed test results and execution statistics. Supports optional environment for variable substitution. |
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 41 tools
Most tools have distinct purposes, e.g., createCollection vs generateCollection, but some pairs like syncCollectionWithSpec and generateCollection could be confused without careful reading. Overall clear.
All tools use consistent camelCase naming with a clear verb-noun pattern (e.g., createCollection, getEnvironment). No mixing of conventions.
41 tools is on the higher side for an MCP server, but the domain (Postman API) is broad and justifies many operations. However, it slightly exceeds the typical range.
The tool set lacks delete operations for collections, environments, mocks, and specs, creating significant gaps in lifecycle management. Also, collection update is limited to full replacement.