Postman MCP server

Postman MCP server MCP Server

Postman's MCP server connects AI agents, assistants, and chatbots directly to your APIs on Postman. Use natural language to prompt AI to automate work across your Postman collections, environments, workspaces, and more.

What is an MCP Server?⁠

Characteristics

Attribute	Details
Docker Image	mcp/postman⁠
Author	postmanlabs⁠
Repository	https://github.com/postmanlabs/postman-mcp-server⁠
Dockerfile	https://github.com/postmanlabs/postman-mcp-server/blob/main/Dockerfile⁠
Docker Image built by	Docker Inc.
Docker Scout Health Score
Verify Signature	COSIGN_REPOSITORY=mcp/signatures cosign verify mcp/postman --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub
Licence	Apache License 2.0

Available Tools (38)

Note:

If you do not include the `workspace` query parameter, the system creates the collection in the oldest personal Internal workspace you own. | createCollectionRequest|Creates a request in a collection. For a complete list of properties, refer to the Request entry in the Postman Collection Format documentation⁠.

Note:

It is recommended that you pass the `name` property in the request body. If you do not, the system uses a null value. As a result, this creates a request with a blank name. | createCollectionResponse|Creates a request response in a collection. For a complete list of request body properties, refer to the Response entry in the Postman Collection Format documentation⁠.

Note:

It is recommended that you pass the `name` property in the request body. If you do not, the system uses a null value. As a result, this creates a response with a blank name. | createEnvironment|Creates an environment.

Note:

• The request body size cannot exceed the maximum allowed size of 30MB.

• If you receive an HTTP `411 Length Required` error response, manually pass the `Content-Length` header and its value in the request header.

• If you do not include the `workspace` query parameter, the system creates the environment in the oldest personal Internal workspace you own. | createMock|Creates a mock server in a collection.

• Pass the collection UID (ownerId-collectionId), not the bare collection ID.

• If you only have a `collectionId`, resolve the UID first:

  1. Prefer GET `/collections/{collectionId}` and read `uid`, or
  2. Construct `{ownerId}-{collectionId}` using ownerId from GET `/me`:
  • For team-owned collections: `ownerId = me.teamId`
  • For personal collections: `ownerId = me.user.id`

• Use the `workspace` query to place the mock in a specific workspace. Prefer explicit workspace scoping. | createSpec|Creates an API specification in Postman's Spec Hub⁠. Specifications can be single or multi-file.

Note:

• Postman supports OpenAPI 3.0 and AsyncAPI 2.0 specifications.
• If the file path contains a `/` (forward slash) character, then a folder is created. For example, if the path is the `components/schemas.json` value, then a `components` folder is created with the `schemas.json` file inside.
• Multi-file specifications can only have one root file.
• Files cannot exceed a maximum of 10 MB in size. | createSpecFile|Creates an API specification file.

Note:

• If the file path contains a `/` (forward slash) character, then a folder is created. For example, if the path is the `components/schemas.json` value, then a `components` folder is created with the `schemas.json` file inside.
• Creating a spec file assigns it the `DEFAULT` file type.
• Multi-file specifications can only have one root file.
• Files cannot exceed a maximum of 10 MB in size. | createWorkspace|Creates a new workspace⁠.

Note:

• This endpoint returns a 403 `Forbidden` response if the user does not have permission to create workspaces. Admins and Super Admins⁠ can configure workspace permissions to restrict users and/or user groups from creating workspaces or require approvals for the creation of team workspaces.
• There are rate limits when publishing public workspaces.
• Public team workspace names must be unique.

Important

We deprecated linking collections or environments between workspaces. We do not recommend that you do this.

If you have a linked collection or environment, note the following:

• The endpoint does not create a clone of a collection or environment.
• Any changes you make to a linked collection or environment changes them in all workspaces.
• If you delete a collection or environment linked between workspaces, the system deletes it in all the workspaces. | duplicateCollection|Creates a duplicate of the given collection in another workspace.

Use the GET `/collection-duplicate-tasks/{taskId}` endpoint to get the duplication task's current status. | generateCollection|Creates a collection from the given API specification. The specification must already exist or be created before it can be used to generate a collection. The response contains a polling link to the task status. | generateSpecFromCollection|Generates an API specification for the given collection. The response contains a polling link to the task status.| getAllSpecs|Gets all API specifications in a workspace.| getAuthenticatedUser|Gets information about the authenticated user.

• This endpoint provides “current user” context (`user.id`, `username`, `teamId`, roles).

• When a user asks for “my …” (e.g., “my workspaces, my information, etc.”), call this first to resolve the user ID. | getCollection|Gets information about a collection. For a complete list of this endpoint's possible values, refer to the Postman Collection Format documentation⁠.| getCollections|The workspace ID query is required for this endpoint. If not provided, the LLM should ask the user to provide it.| getEnvironment|Gets information about an environment.| getEnvironments|Gets information about all of your environments⁠.| getGeneratedCollectionSpecs|Gets the API specification generated for the given collection.| getMock|Gets information about a mock server.

• Resource: Mock server entity. Response includes the associated `collection` UID and `mockUrl`.

• Use the `collection` UID to navigate back to the source collection. | getMocks|Gets all active mock servers. By default, returns only mock servers you created across all workspaces.

• Always pass either the `workspace` or `teamId` query to scope results. Prefer `workspace` when known.

• If you need team-scoped results, set `teamId` from the current user: call GET `/me` and use `me.teamId`.

• If both `teamId` and `workspace` are passed, only `workspace` is used. | getSpec|Gets information about an API specification.| getSpecCollections|Gets all of an API specification's generated collections.| getSpecDefinition|Gets the complete contents of an API specification's definition.| getSpecFile|Gets the contents of an API specification's file.| getSpecFiles|Gets all the files in an API specification.| getStatusOfAnAsyncApiTask|Gets the status of an asynchronous task.| getTaggedEntities|Gets Postman elements (entities) by a given tag. Tags enable you to organize and search workspaces⁠, APIs⁠, and collections⁠ that contain shared tags.

Note:

Tagging is available on Postman Enterprise plans⁠. | getWorkspace|Gets information about a workspace.

Note:

This endpoint's response contains the `visibility` field. Visibility⁠ determines who can access the workspace:

• `personal` — Only you can access the workspace.
• `team` — All team members can access the workspace.
• `private` — Only invited team members can access the workspace (Professional and Enterprise plans only⁠).
• `public` — Everyone can access the workspace.
• `partner` — Only invited team members and partners⁠ can access the workspace (Professional and Enterprise plans only⁠).

Important

We have deprecated the `name` and `uid` responses in the following array of objects:

• `collections`
• `environments`
• `mocks`
• `monitors`
• `apis` | getWorkspaces|Gets all workspaces you have access to.
• For “my …” requests, first call GET `/me` and pass `createdBy={me.user.id}`.
• This endpoint's response contains the visibility field. Visibility determines who can access the workspace:
  • `personal` — Only you can access the workspace.
  • `team` — All team members can access the workspace.
  • `private` — Only invited team members can access the workspace (Professional and Enterprise).
  • `public` — Everyone can access the workspace.
  • `partner` — Invited team members and partners (Professional and Enterprise).
• For tools that require the workspace ID, and no workspace ID is provided, ask the user to provide the workspace ID. If the user does not provide the workspace ID, call this first with the createdBy parameter to use the first workspace.
• Examples:
  • “List my workspaces” → GET `/me`, then GET `/workspaces?createdBy={me.user.id}`
  • “List my personal workspaces” → GET `/me`, then GET `/workspaces?type=personal&createdBy={me.user.id}`
  • “List all public workspaces” → GET `/workspaces?type=public` | publishMock|Publishes a mock server. Publishing a mock server sets its Access Control configuration setting to public.| putCollection|Replaces the contents of a collection using the Postman Collection v2.1.0 schema format⁠. Include the collection's ID values in the request body. If you do not, the endpoint removes the existing items and creates new items.

To perform an update asynchronously, use the `Prefer` header with the `respond-async` value. When performing an async update, this endpoint returns a HTTP `202 Accepted` response.

Note:

• The maximum collection size this endpoint accepts cannot exceed 100 MB.
• If you don't include the collection items' ID values from the request body, the endpoint removes the existing items and recreates the items with new ID values.
• To copy another collection's contents to the given collection, remove all ID values before you pass it in this endpoint. If you do not, this endpoint returns an error. These values include the `id`, `uid`, and `postman_id` values.
• For protocol profile behavior, refer to Postman's Protocol Profile Behavior documentation⁠. | putEnvironment|Replaces all the contents of an environment with the given information.

Note:

• The request body size cannot exceed the maximum allowed size of 30MB.
• If you receive an HTTP `411 Length Required` error response, manually pass the `Content-Length` header and its value in the request header. | syncCollectionWithSpec|Syncs a collection generated from an API specification. This is an asynchronous endpoint that returns an HTTP `202 Accepted` response.

Note:

• This endpoint only supports the OpenAPI 3.0 specification type.
• You can only sync collections generated from the given spec ID. | syncSpecWithCollection|Syncs an API specification linked to a collection. This is an asynchronous endpoint that returns an HTTP `202 Accepted` response.

Note:

• This endpoint only supports the OpenAPI 3.0 specification type.
• You can only sync specs generated from the given collection ID. | updateMock|Updates a mock server.
• Resource: Mock server entity associated with a collection UID.
• Use this to change name, environment, privacy, or default server response. | updateSpecFile|Updates an API specification's file.

Note:

• This endpoint does not accept an empty request body. You must pass one of the accepted values.
• This endpoint does not accept multiple request body properties in a single call. For example, you cannot pass both the `content` and `type` property at the same time.
• Multi-file specifications can only have one root file.
• When updating a file type to `ROOT`, the previous root file is updated to the `DEFAULT` file type.
• Files cannot exceed a maximum of 10 MB in size. | updateSpecProperties|Updates an API specification's properties, such as its name.| updateWorkspace|Updates a workspace.

Note:

• There are rate limits when publishing public workspaces.
• Public team workspace names must be unique.

Important

We deprecated linking collections or environments between workspaces. We do not recommend that you do this.

If you have a linked collection or environment, note the following:

• The endpoint does not create a clone of a collection or environment.
• Any changes you make to a linked collection or environment changes them in all workspaces.
• If you delete a collection or environment linked between workspaces, the system deletes it in all the workspaces. |

Tools Details

Tool: createCollection

Creates a collection using the Postman Collection v2.1.0 schema format⁠.

Note:

If you do not include the `workspace` query parameter, the system creates the collection in the oldest personal Internal workspace you own.

Tool: createCollectionRequest

Creates a request in a collection. For a complete list of properties, refer to the Request entry in the Postman Collection Format documentation⁠.

Note:

It is recommended that you pass the `name` property in the request body. If you do not, the system uses a null value. As a result, this creates a request with a blank name.

Tool: createCollectionResponse

Creates a request response in a collection. For a complete list of request body properties, refer to the Response entry in the Postman Collection Format documentation⁠.

Note:

It is recommended that you pass the `name` property in the request body. If you do not, the system uses a null value. As a result, this creates a response with a blank name.

Tool: createEnvironment

Creates an environment.

Note:

• The request body size cannot exceed the maximum allowed size of 30MB.
• If you receive an HTTP `411 Length Required` error response, manually pass the `Content-Length` header and its value in the request header.
• If you do not include the `workspace` query parameter, the system creates the environment in the oldest personal Internal workspace you own. Parameters|Type|Description -|-|- workspace|string|The workspace's ID. environment|objectoptional|Information about the environment.

Tool: createMock

Creates a mock server in a collection.

• Pass the collection UID (ownerId-collectionId), not the bare collection ID.
• If you only have a `collectionId`, resolve the UID first:
  1. Prefer GET `/collections/{collectionId}` and read `uid`, or
  2. Construct `{ownerId}-{collectionId}` using ownerId from GET `/me`:
  • For team-owned collections: `ownerId = me.teamId`
  • For personal collections: `ownerId = me.user.id`
• Use the `workspace` query to place the mock in a specific workspace. Prefer explicit workspace scoping. Parameters|Type|Description -|-|- workspace|string|The workspace's ID. mock|objectoptional|

Tool: createSpec

Creates an API specification in Postman's Spec Hub⁠. Specifications can be single or multi-file.

Note:

• Postman supports OpenAPI 3.0 and AsyncAPI 2.0 specifications.
• If the file path contains a `/` (forward slash) character, then a folder is created. For example, if the path is the `components/schemas.json` value, then a `components` folder is created with the `schemas.json` file inside.
• Multi-file specifications can only have one root file.
• Files cannot exceed a maximum of 10 MB in size. Parameters|Type|Description -|-|- files|array|A list of the specification's files and their contents. name|string|The specification's name. type|string|The specification's type. workspaceId|string|The workspace's ID.

Tool: createSpecFile

Creates an API specification file.

Note:

• If the file path contains a `/` (forward slash) character, then a folder is created. For example, if the path is the `components/schemas.json` value, then a `components` folder is created with the `schemas.json` file inside.
• Creating a spec file assigns it the `DEFAULT` file type.
• Multi-file specifications can only have one root file.
• Files cannot exceed a maximum of 10 MB in size. Parameters|Type|Description -|-|- content|string|The file's stringified contents. path|string|The file's path. Accepts JSON or YAML files. specId|string|The spec's ID.

Tool: createWorkspace

Creates a new workspace⁠.

Note:

• This endpoint returns a 403 `Forbidden` response if the user does not have permission to create workspaces. Admins and Super Admins⁠ can configure workspace permissions to restrict users and/or user groups from creating workspaces or require approvals for the creation of team workspaces.
• There are rate limits when publishing public workspaces.
• Public team workspace names must be unique.

Important

We deprecated linking collections or environments between workspaces. We do not recommend that you do this.

If you have a linked collection or environment, note the following:

• The endpoint does not create a clone of a collection or environment.
• Any changes you make to a linked collection or environment changes them in all workspaces.
• If you delete a collection or environment linked between workspaces, the system deletes it in all the workspaces. Parameters|Type|Description -|-|- workspace|objectoptional|Information about the workspace.

Tool: duplicateCollection

Creates a duplicate of the given collection in another workspace.

Use the GET `/collection-duplicate-tasks/{taskId}` endpoint to get the duplication task's current status.

Tool: generateCollection

Creates a collection from the given API specification. The specification must already exist or be created before it can be used to generate a collection. The response contains a polling link to the task status.

Tool: generateSpecFromCollection

Generates an API specification for the given collection. The response contains a polling link to the task status.

Tool: getAllSpecs

Gets all API specifications in a workspace.

This tool is read-only. It does not modify its environment.

Tool: getAuthenticatedUser

Gets information about the authenticated user.

• This endpoint provides “current user” context (`user.id`, `username`, `teamId`, roles).
• When a user asks for “my …” (e.g., “my workspaces, my information, etc.”), call this first to resolve the user ID.

Tool: getCollection

Gets information about a collection. For a complete list of this endpoint's possible values, refer to the Postman Collection Format documentation⁠.

This tool is read-only. It does not modify its environment.

Tool: getCollections

The workspace ID query is required for this endpoint. If not provided, the LLM should ask the user to provide it.

This tool is read-only. It does not modify its environment.

Tool: getEnvironment

Gets information about an environment.

This tool is read-only. It does not modify its environment.

Tool: getEnvironments

Gets information about all of your environments⁠.

This tool is read-only. It does not modify its environment.

Tool: getGeneratedCollectionSpecs

Gets the API specification generated for the given collection.

This tool is read-only. It does not modify its environment.

Tool: getMock

Gets information about a mock server.

• Resource: Mock server entity. Response includes the associated `collection` UID and `mockUrl`.
• Use the `collection` UID to navigate back to the source collection. Parameters|Type|Description -|-|- mockId|string|The mock's ID.

This tool is read-only. It does not modify its environment.

Tool: getMocks

Gets all active mock servers. By default, returns only mock servers you created across all workspaces.

• Always pass either the `workspace` or `teamId` query to scope results. Prefer `workspace` when known.
• If you need team-scoped results, set `teamId` from the current user: call GET `/me` and use `me.teamId`.
• If both `teamId` and `workspace` are passed, only `workspace` is used. Parameters|Type|Description -|-|- teamId|stringoptional|Return only results that belong to the given team ID.
• For team-scoped requests, set this from GET /me (me.teamId).

workspace|stringoptional|Return only results found in the given workspace ID.

• Prefer this parameter when the user mentions a specific workspace.

This tool is read-only. It does not modify its environment.

Tool: getSpec

Gets information about an API specification.

This tool is read-only. It does not modify its environment.

Tool: getSpecCollections

Gets all of an API specification's generated collections.

This tool is read-only. It does not modify its environment.

Tool: getSpecDefinition

Gets the complete contents of an API specification's definition.

This tool is read-only. It does not modify its environment.

Tool: getSpecFile

Gets the contents of an API specification's file.

This tool is read-only. It does not modify its environment.

Tool: getSpecFiles

Gets all the files in an API specification.

This tool is read-only. It does not modify its environment.

Tool: getStatusOfAnAsyncApiTask

Gets the status of an asynchronous task.

This tool is read-only. It does not modify its environment.

Tool: getTaggedEntities

Gets Postman elements (entities) by a given tag. Tags enable you to organize and search workspaces⁠, APIs⁠, and collections⁠ that contain shared tags.

Note:

Tagging is available on Postman Enterprise plans⁠.

This tool is read-only. It does not modify its environment.

Tool: getWorkspace

Gets information about a workspace.

Note:

This endpoint's response contains the `visibility` field. Visibility⁠ determines who can access the workspace:

• `personal` — Only you can access the workspace.
• `team` — All team members can access the workspace.
• `private` — Only invited team members can access the workspace (Professional and Enterprise plans only⁠).
• `public` — Everyone can access the workspace.
• `partner` — Only invited team members and partners⁠ can access the workspace (Professional and Enterprise plans only⁠).

Important

We have deprecated the `name` and `uid` responses in the following array of objects:

• `collections`
• `environments`
• `mocks`
• `monitors`
• `apis` Parameters|Type|Description -|-|- workspaceId|string|The workspace's ID. include|stringoptional|Include the following information in the endpoint's response:
• mocks:deactivated — Include all deactivated mock servers in the response.
• scim — Return the SCIM user IDs of the workspace creator and who last modified it.

This tool is read-only. It does not modify its environment.

Tool: getWorkspaces

Gets all workspaces you have access to.

• For “my …” requests, first call GET `/me` and pass `createdBy={me.user.id}`.
• This endpoint's response contains the visibility field. Visibility determines who can access the workspace:
  • `personal` — Only you can access the workspace.
  • `team` — All team members can access the workspace.
  • `private` — Only invited team members can access the workspace (Professional and Enterprise).
  • `public` — Everyone can access the workspace.
  • `partner` — Invited team members and partners (Professional and Enterprise).
• For tools that require the workspace ID, and no workspace ID is provided, ask the user to provide the workspace ID. If the user does not provide the workspace ID, call this first with the createdBy parameter to use the first workspace.
• Examples:
  • “List my workspaces” → GET `/me`, then GET `/workspaces?createdBy={me.user.id}`
  • “List my personal workspaces” → GET `/me`, then GET `/workspaces?type=personal&createdBy={me.user.id}`
  • “List all public workspaces” → GET `/workspaces?type=public` Parameters|Type|Description -|-|- createdBy|integeroptional|Return only workspaces created by the specified Postman user ID.
• For “my …” requests, set createdBy to the current user’s ID from GET /me (me.user.id).
• If the user's ID is not known, first call GET /me, then retry with createdBy.

include|stringoptional|Include the following information in the endpoint's response:

• mocks:deactivated — Include all deactivated mock servers in the response.
• scim — Return the SCIM user IDs of the workspace creator and who last modified it.

type|stringoptional|The type of workspace to filter the response by. One of: personal, team, private, public, partner.

• For “my …” requests, this can be combined with createdBy. If type is not specified, it will search across all types for that user.

This tool is read-only. It does not modify its environment.

Tool: publishMock

Publishes a mock server. Publishing a mock server sets its Access Control configuration setting to public.

Tool: putCollection

Replaces the contents of a collection using the Postman Collection v2.1.0 schema format⁠. Include the collection's ID values in the request body. If you do not, the endpoint removes the existing items and creates new items.

To perform an update asynchronously, use the `Prefer` header with the `respond-async` value. When performing an async update, this endpoint returns a HTTP `202 Accepted` response.

Note:

• The maximum collection size this endpoint accepts cannot exceed 100 MB.
• If you don't include the collection items' ID values from the request body, the endpoint removes the existing items and recreates the items with new ID values.
• To copy another collection's contents to the given collection, remove all ID values before you pass it in this endpoint. If you do not, this endpoint returns an error. These values include the `id`, `uid`, and `postman_id` values.
• For protocol profile behavior, refer to Postman's Protocol Profile Behavior documentation⁠. Parameters|Type|Description -|-|- collectionId|string|The collection ID must be in the form <OWNER_ID>- (e.g. 12345-33823532ab9e41c9b6fd12d0fd459b8b). Prefer|stringoptional|The respond-async header to perform the update asynchronously. collection|objectoptional|

Tool: putEnvironment

Replaces all the contents of an environment with the given information.

Note:

• The request body size cannot exceed the maximum allowed size of 30MB.
• If you receive an HTTP `411 Length Required` error response, manually pass the `Content-Length` header and its value in the request header. Parameters|Type|Description -|-|- environmentId|string|The environment's ID. environment|objectoptional|Information about the environment.

Tool: syncCollectionWithSpec

Syncs a collection generated from an API specification. This is an asynchronous endpoint that returns an HTTP `202 Accepted` response.

Note:

• This endpoint only supports the OpenAPI 3.0 specification type.
• You can only sync collections generated from the given spec ID. Parameters|Type|Description -|-|- collectionUid|string|The collection's unique ID. specId|string|The spec's ID.

Tool: syncSpecWithCollection

Syncs an API specification linked to a collection. This is an asynchronous endpoint that returns an HTTP `202 Accepted` response.

Note:

• This endpoint only supports the OpenAPI 3.0 specification type.
• You can only sync specs generated from the given collection ID. Parameters|Type|Description -|-|- collectionUid|string|The collection's unique ID. specId|string|The spec's ID.

Tool: updateMock

Updates a mock server.

• Resource: Mock server entity associated with a collection UID.
• Use this to change name, environment, privacy, or default server response. Parameters|Type|Description -|-|- mockId|string|The mock's ID. mock|objectoptional|

Tool: updateSpecFile

Updates an API specification's file.

Note:

• This endpoint does not accept an empty request body. You must pass one of the accepted values.
• This endpoint does not accept multiple request body properties in a single call. For example, you cannot pass both the `content` and `type` property at the same time.
• Multi-file specifications can only have one root file.
• When updating a file type to `ROOT`, the previous root file is updated to the `DEFAULT` file type.
• Files cannot exceed a maximum of 10 MB in size. Parameters|Type|Description -|-|- filePath|string|The path to the file. specId|string|The spec's ID. content|stringoptional|The specification's stringified contents. name|stringoptional|The file's name. type|stringoptional|The type of file:
• ROOT — The file containing the full OpenAPI structure. This serves as the entry point for the API spec and references other (DEFAULT) spec files. Multi-file specs can only have one root file.
• DEFAULT — A file referenced by the ROOT file.

Tool: updateSpecProperties

Updates an API specification's properties, such as its name.

Tool: updateWorkspace

Updates a workspace.

Note:

• There are rate limits when publishing public workspaces.
• Public team workspace names must be unique.

Important

We deprecated linking collections or environments between workspaces. We do not recommend that you do this.

If you have a linked collection or environment, note the following:

• The endpoint does not create a clone of a collection or environment.
• Any changes you make to a linked collection or environment changes them in all workspaces.
• If you delete a collection or environment linked between workspaces, the system deletes it in all the workspaces. Parameters|Type|Description -|-|- workspaceId|string|The workspace's ID. workspace|objectoptional|

Use this MCP Server

{
  "mcpServers": {
    "postman": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "POSTMAN_API_KEY",
        "mcp/postman"
      ],
      "env": {
        "POSTMAN_API_KEY": "<POSTMAN_API_KEY>"
      }
    }
  }
}

Why is it safer to run MCP Servers with Docker?⁠