mcp/postman

Postman的MCP服务器用于将AI代理、助手及聊天机器人直接连接至Postman上的API。

4 次收藏下载次数: 0状态：社区镜像维护者：mcp（Model Context Protocol）仓库类型：镜像最近更新：26 天前

Postman 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?

MCP Info

Attribute	Details
Docker Image	https://hub.docker.com/repository/docker/mcp/postman
Author	https://github.com/postmanlabs
Repository	https://github.com/postmanlabs/postman-mcp-server

Image Building Info

Attribute	Details
Dockerfile	https://github.com/postmanlabs/postman-mcp-server/blob/61b7f9eae66f75f0b3cba5774426adc7b4b425af/Dockerfile
Commit	`61b7f9eae66f75f0b3cba5774426adc7b4b425af`
Docker Image built by	Docker Inc.
Docker Scout Health Score	!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 (41)

Tools provided by this Server	Short Description
`createCollection`	Creates a collection using the Postman Collection v2.1.0 schema format.
`createCollectionRequest`	Creates a request in a collection. For a complete list of properties, refer to the Request entry in the Postman Collection Format documentation.
`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.
`createEnvironment`	Creates an environment.
`createMock`	Creates a mock server in a collection.
`createSpec`	Creates an API specification in Postman's Spec Hub. Specifications can be single or multi-file.
`createSpecFile`	Creates an API specification file.
`createWorkspace`	Creates a new workspace.
`duplicateCollection`	Creates a duplicate of the given collection in another workspace.
`generateCollection`	Creates a collection from the given API specification.
`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.
`getCollection`	Get Collection (map by default)
`getCollections`	The workspace ID query is required for this endpoint. If not provided, the LLM should ask the user to provide it.
`getDuplicateCollectionTaskStatus`	Gets the status of a collection duplication task.
`getEnabledTools`	Get Enabled Tools
`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.
`getMocks`	Gets all active mock servers. By default, returns only mock servers you created across all workspaces.
`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.
`getTaggedEntities`	Requires an Enterprise plan. Tagging is only available on Postman Enterprise plans. This tool returns a 404 error on Free, Basic, and Professional accounts.
`getWorkspace`	Gets information about a workspace.
`getWorkspaces`	Gets all workspaces you have access to.
`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.
`putEnvironment`	Replaces all the contents of an environment with the given information.
`runCollection`	Run Postman Collection
`syncCollectionWithSpec`	Syncs a collection generated from an API specification. This is an asynchronous endpoint that returns an HTTP `202 Accepted` response.
`syncSpecWithCollection`	Syncs an API specification linked to a collection. This is an asynchronous endpoint that returns an HTTP `202 Accepted` response.
`updateCollectionRequest`	Updates a request in a collection. For a complete list of properties, refer to the Request entry in the Postman Collection Format documentation.
`updateMock`	Updates a mock server.
`updateSpecFile`	Updates an API specification's file.
`updateSpecProperties`	Updates an API specification's properties, such as its name.
`updateWorkspace`	Updates a workspace.

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.

Parameters	Type	Description
`workspace`	`string`	The workspace's ID.
`collection`	`object` optional

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.

Parameters	Type	Description
`collectionId`	`string`	The collection's ID.
`auth`	`string` optional	The request's authentication information.
`data`	`string` optional	The request body's form data.
`dataMode`	`string` optional	The request body's data mode.
`dataOptions`	`string` optional	Additional configurations and options set for the request body's various data modes.
`description`	`string` optional	The request's description.
`events`	`string` optional	A list of scripts configured to run when specific events occur.
`folderId`	`string` optional	The folder ID in which to create the request. By default, the system will create the request at the collection level.
`graphqlModeData`	`string` optional	The request body's GraphQL mode data.
`headerData`	`array` optional	The request's headers.
`method`	`string` optional	The request's HTTP method.
`name`	`string` optional	The request's name. 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.
`queryParams`	`array` optional	The request's query parameters.
`rawModeData`	`string` optional	The request body's raw mode data.
`url`	`string` optional	The request's URL.

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.

Parameters	Type	Description
`collectionId`	`string`	The collection's ID.
`request`	`string`	The parent request's ID.
`cookies`	`string` optional	The response's cookie data.
`dataMode`	`string` optional	The associated request body's data mode.
`dataOptions`	`string` optional	Additional configurations and options set for the request body's various data modes.
`description`	`string` optional	The response's description.
`headers`	`array` optional	A list of headers.
`language`	`string` optional	The response body's language type.
`method`	`string` optional	The request's HTTP method.
`mime`	`string` optional	The response's MIME type.
`name`	`string` optional	The response's name. 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.
`rawDataType`	`string` optional	The response's raw data type.
`rawModeData`	`string` optional	The associated request body's raw mode data.
`requestObject`	`string` optional	A JSON-stringified representation of the associated request.
`responseCode`	`object` optional	The response's HTTP response code information.
`status`	`string` optional	The response's HTTP status text.
`text`	`string` optional	The raw text of the response body.
`time`	`string` optional	The time taken by the request to complete, in milliseconds.
`url`	`string` optional	The associated request's URL.

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|object optional|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|object optional|

Tool: createSpec

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

Note:

Postman supports OpenAPI 2.0, OpenAPI 3.0, OpenAPI 3.1, AsyncAPI 2.0, protobuf 2 and 3, and GraphQL 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.
Private and Partner Workspaces are available on Postman Team and Enterprise plans.
There are rate limits when publishing public workspaces.
Public team workspace names must be unique.
The `teamId` property must be passed in the request body if Postman Organizations is enabled. Parameters|Type|Description -|-|- workspace|object optional|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.

Parameters	Type	Description
`collectionId`	`string`	The collection's unique ID.
`workspace`	`string`	The workspace ID in which to duplicate the collection.
`suffix`	`string` optional	An optional suffix to append to the duplicated collection's name.

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.

Parameters	Type	Description
`elementType`	`string`	The `collection` element type.
`name`	`string`	The generated collection's name.
`options`	`object`	The advanced creation options and their values. For more details, see Postman's https://github.com/postmanlabs/openapi-to-postman/blob/develop/OPTIONS.md. These properties are case-sensitive.
`specId`	`string`	The spec's ID.

Tool: generateSpecFromCollection

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

Parameters	Type	Description
`collectionUid`	`string`	The collection's unique ID.
`elementType`	`string`	The `spec` value.
`format`	`string`	The format of the API specification.
`name`	`string`	The API specification's name.
`type`	`string`	The specification's type.

Tool: getAllSpecs

Gets all API specifications in a workspace.

Parameters	Type	Description
`workspaceId`	`string`	The workspace's ID.
`cursor`	`string` optional	The pointer to the first record of the set of paginated results. To view the next response, use the `nextCursor` value for this parameter.
`limit`	`integer` optional	The maximum number of rows to return in the response.

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

Get information about a collection. By default this tool returns the lightweight collection map (metadata + recursive itemRefs). Use the model parameter to opt in to Postman's full API responses:

model=minimal — root-level folder/request IDs only
model=full — full Postman collection payload. Parameters|Type|Description -|-|- collectionId|string|The collection ID must be in the form <OWNER_ID>- (e.g. ***-33823532ab9e41c9b6fd12d0fd459b8b). access_key|string optional|A collection's read-only access key. Using this query parameter does not require an API key to call the endpoint. model|string optional|Optional response shape override. Omit to receive the lightweight collection map. Set to minimal for the Postman minimal model or full for the complete collection payload.

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.

Parameters	Type	Description
`workspace`	`string`	The workspace's ID.
`limit`	`integer` optional	The maximum number of rows to return in the response.
`name`	`string` optional	Filter results by collections that match the given name.
`offset`	`integer` optional	The zero-based offset of the first item to return.

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

Tool: getDuplicateCollectionTaskStatus

Gets the status of a collection duplication task.

Parameters	Type	Description
`taskId`	`string`	The task's unique ID.

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

Tool: getEnabledTools

IMPORTANT: Run this tool first when a requested tool is unavailable. Returns information about which tools are enabled in the full and minimal tool sets, helping you identify available alternatives.

Tool: getEnvironment

Gets information about an environment.

Parameters	Type	Description
`environmentId`	`string`	The environment's ID.

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

Tool: getEnvironments

Gets information about all of your environments.

Parameters	Type	Description
`workspace`	`string` optional	The workspace's ID.

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

Tool: getGeneratedCollectionSpecs

Gets the API specification generated for the given collection.

Parameters	Type	Description
`collectionUid`	`string`	The collection's unique ID.
`elementType`	`string`	The `spec` value.

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|string optional|Return only results that belong to the given team ID.
For team-scoped requests, set this from GET /me (me.teamId).

workspace|string optional|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.

Parameters	Type	Description
`specId`	`string`	The spec's ID.

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

Tool: getSpecCollections

Gets all of an API specification's generated collections.

Parameters	Type	Description
`elementType`	`string`	The `collection` element type.
`specId`	`string`	The spec's ID.
`cursor`	`string` optional	The pointer to the first record of the set of paginated results. To view the next response, use the `nextCursor` value for this parameter.
`limit`	`integer` optional	The maximum number of rows to return in the response.

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

Tool: getSpecDefinition

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

Parameters	Type	Description
`specId`	`string`	The spec's ID.

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

Tool: getSpecFile

Gets the contents of an API specification's file.

Parameters	Type	Description
`filePath`	`string`	The path to the file.
`specId`	`string`	The spec's ID.

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

Tool: getSpecFiles

Gets all the files in an API specification.

Parameters	Type	Description
`specId`	`string`	The spec's ID.

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

Tool: getTaggedEntities

Requires an Enterprise plan. Tagging is only available on Postman Enterprise plans. This tool returns a 404 error on Free, Basic, and Professional accounts.

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

Parameters	Type	Description
`slug`	`string`	The tag's ID within a team or individual (non-team) user scope.
`cursor`	`string` optional	The cursor to get the next set of results in the paginated response. If you pass an invalid value, the API only returns the first set of results.
`direction`	`string` optional	The ascending (`asc`) or descending (`desc`) order to sort the results by, based on the time of the entity's tagging.
`entityType`	`string` optional	Filter results for the given entity type.
`limit`	`integer` optional	The maximum number of tagged elements to return in a single call.

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 (Team and Enterprise plans only).
`public` — Everyone can access the workspace.
`partner` — Only invited team members and partners can access the workspace (Team and Enterprise plans only). Parameters|Type|Description -|-|- workspaceId|string|The workspace's ID. include|string optional|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&cre

[...]

查看更多 postman 相关镜像 →

轩辕镜像配置手册

探索更多轩辕镜像的使用方法，找到最适合您系统的配置方式

Docker 配置

登录仓库拉取

通过 Docker 登录认证访问私有仓库

专属域名拉取

无需登录使用专属域名

K8s Containerd

Kubernetes 集群配置 Containerd

K3s

K3s 轻量级 Kubernetes 镜像加速

Dev Containers

VS Code Dev Containers 配置

Podman

Podman 容器引擎配置

Singularity/Apptainer

HPC 科学计算容器配置

其他仓库配置

ghcr、Quay、nvcr 等镜像仓库

Harbor 镜像源配置

Harbor Proxy Repository 对接专属域名

Portainer 镜像源配置

Portainer Registries 加速拉取

Nexus 镜像源配置

Nexus3 Docker Proxy 内网缓存

系统配置

Linux

在 Linux 系统配置镜像服务

Windows/Mac

在 Docker Desktop 配置镜像

MacOS OrbStack

MacOS OrbStack 容器配置

Docker Compose

Docker Compose 项目配置

NAS 设备

群晖

Synology 群晖 NAS 配置

飞牛

飞牛 fnOS 系统配置镜像

绿联

绿联 NAS 系统配置镜像

威联通

QNAP 威联通 NAS 配置

极空间

极空间 NAS 系统配置服务

网络设备

爱快路由

爱快 iKuai 路由系统配置

宝塔面板

在宝塔面板一键配置镜像

需要其他帮助？请查看我们的常见问题Docker 镜像访问常见问题解答或提交工单

镜像拉取常见问题

使用与功能问题

配置了专属域名后，docker search 为什么会报错？

docker search 限制

Docker Hub 上有的镜像，为什么在轩辕镜像网站搜不到？

站内搜不到镜像

机器不能直连外网时，怎么用 docker save / load 迁镜像？

离线 save/load

docker pull 拉插件报错（plugin v1+json）怎么办？

插件要用 plugin install

WSL 里 Docker 拉镜像特别慢，怎么排查和优化？

WSL 拉取慢

轩辕镜像安全吗？如何用 digest 校验镜像没被篡改？

安全与 digest

第一次用轩辕镜像拉 Docker 镜像，要怎么登录和配置？

新手拉取配置

错误码与失败问题

docker pull 提示 manifest unknown 怎么办？

manifest unknown

docker pull 提示 no matching manifest 怎么办？

no matching manifest（架构）

镜像已拉取完成，却提示 invalid tar header 或 failed to register layer 怎么办？

invalid tar header（解压）

Docker pull 时 HTTPS / TLS 证书验证失败怎么办？

TLS 证书失败

Docker pull 时 DNS 解析超时或连不上仓库怎么办？

DNS 超时

Docker 拉取出现 410 Gone 怎么办？

410 Gone 排查

出现 402 或「流量用尽」提示怎么办？

402 与流量用尽

Docker 拉取提示 UNAUTHORIZED（401）怎么办？

401 认证失败

遇到 429 Too Many Requests（请求太频繁）怎么办？

429 限流

docker login 提示 Cannot autolaunch D-Bus，还算登录成功吗？

D-Bus 凭证提示

为什么会出现「单层超过 20GB」或 413，无法加速拉取？

413 与超大单层

账号 / 计费 / 权限

轩辕镜像免费版和专业版有什么区别？

免费版与专业版区别

轩辕镜像支持哪些 Docker 镜像仓库？

支持的镜像仓库

镜像拉取失败还会不会扣流量？

失败是否计费

麒麟 V10 / 统信 UOS 提示 KYSEC 权限不够怎么办？

KYSEC 拦截脚本

如何在轩辕镜像申请开具发票？

申请开票

怎么修改轩辕镜像的网站登录和仓库登录密码？

修改登录密码

如何注销轩辕镜像账户？要注意什么？

注销账户

配置与原理类

写了 registry-mirrors，为什么还是走官方或仍然报错？

mirrors 不生效

怎么用 docker tag 去掉镜像名里的轩辕域名前缀？

去掉域名前缀

如何拉取指定 CPU 架构的镜像（如 ARM64、AMD64）？

指定架构拉取

用轩辕镜像拉镜像时快时慢，常见原因有哪些？

拉取速度原因

查看全部问题→

用户好评

来自真实用户的反馈，见证轩辕镜像的优质服务

oldzhang

运维工程师

Linux服务器

"Docker访问体验非常流畅，大镜像也能快速完成下载。"

mcp/postman

mcp（Model Context Protocol）

Postman的MCP服务器用于将AI代理、助手及聊天机器人直接连接至Postman上的API。

4 次收藏下载次数: 0状态：社区镜像维护者：mcp（Model Context Protocol）仓库类型：镜像最近更新：26 天前

轩辕镜像，不浪费每一次拉取。点击查看

版本下载

轩辕镜像，不浪费每一次拉取。点击查看

Postman MCP Server

What is an MCP Server?

MCP Info

Attribute	Details
Docker Image	https://hub.docker.com/repository/docker/mcp/postman
Author	https://github.com/postmanlabs
Repository	https://github.com/postmanlabs/postman-mcp-server

Image Building Info

Attribute	Details
Dockerfile	https://github.com/postmanlabs/postman-mcp-server/blob/61b7f9eae66f75f0b3cba5774426adc7b4b425af/Dockerfile
Commit	`61b7f9eae66f75f0b3cba5774426adc7b4b425af`
Docker Image built by	Docker Inc.
Docker Scout Health Score	!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 (41)

Tools provided by this Server	Short Description
`createCollection`	Creates a collection using the Postman Collection v2.1.0 schema format.
`createCollectionRequest`	Creates a request in a collection. For a complete list of properties, refer to the Request entry in the Postman Collection Format documentation.
`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.
`createEnvironment`	Creates an environment.
`createMock`	Creates a mock server in a collection.
`createSpec`	Creates an API specification in Postman's Spec Hub. Specifications can be single or multi-file.
`createSpecFile`	Creates an API specification file.
`createWorkspace`	Creates a new workspace.
`duplicateCollection`	Creates a duplicate of the given collection in another workspace.
`generateCollection`	Creates a collection from the given API specification.
`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.
`getCollection`	Get Collection (map by default)
`getCollections`	The workspace ID query is required for this endpoint. If not provided, the LLM should ask the user to provide it.
`getDuplicateCollectionTaskStatus`	Gets the status of a collection duplication task.
`getEnabledTools`	Get Enabled Tools
`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.
`getMocks`	Gets all active mock servers. By default, returns only mock servers you created across all workspaces.
`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.
`getTaggedEntities`	Requires an Enterprise plan. Tagging is only available on Postman Enterprise plans. This tool returns a 404 error on Free, Basic, and Professional accounts.
`getWorkspace`	Gets information about a workspace.
`getWorkspaces`	Gets all workspaces you have access to.
`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.
`putEnvironment`	Replaces all the contents of an environment with the given information.
`runCollection`	Run Postman Collection
`syncCollectionWithSpec`	Syncs a collection generated from an API specification. This is an asynchronous endpoint that returns an HTTP `202 Accepted` response.
`syncSpecWithCollection`	Syncs an API specification linked to a collection. This is an asynchronous endpoint that returns an HTTP `202 Accepted` response.
`updateCollectionRequest`	Updates a request in a collection. For a complete list of properties, refer to the Request entry in the Postman Collection Format documentation.
`updateMock`	Updates a mock server.
`updateSpecFile`	Updates an API specification's file.
`updateSpecProperties`	Updates an API specification's properties, such as its name.
`updateWorkspace`	Updates a workspace.

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.

Parameters	Type	Description
`workspace`	`string`	The workspace's ID.
`collection`	`object` optional

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.

Parameters	Type	Description
`collectionId`	`string`	The collection's ID.
`auth`	`string` optional	The request's authentication information.
`data`	`string` optional	The request body's form data.
`dataMode`	`string` optional	The request body's data mode.
`dataOptions`	`string` optional	Additional configurations and options set for the request body's various data modes.
`description`	`string` optional	The request's description.
`events`	`string` optional	A list of scripts configured to run when specific events occur.
`folderId`	`string` optional	The folder ID in which to create the request. By default, the system will create the request at the collection level.
`graphqlModeData`	`string` optional	The request body's GraphQL mode data.
`headerData`	`array` optional	The request's headers.
`method`	`string` optional	The request's HTTP method.
`name`	`string` optional	The request's name. 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.
`queryParams`	`array` optional	The request's query parameters.
`rawModeData`	`string` optional	The request body's raw mode data.
`url`	`string` optional	The request's URL.

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.

Parameters	Type	Description
`collectionId`	`string`	The collection's ID.
`request`	`string`	The parent request's ID.
`cookies`	`string` optional	The response's cookie data.
`dataMode`	`string` optional	The associated request body's data mode.
`dataOptions`	`string` optional	Additional configurations and options set for the request body's various data modes.
`description`	`string` optional	The response's description.
`headers`	`array` optional	A list of headers.
`language`	`string` optional	The response body's language type.
`method`	`string` optional	The request's HTTP method.
`mime`	`string` optional	The response's MIME type.
`name`	`string` optional	The response's name. 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.
`rawDataType`	`string` optional	The response's raw data type.
`rawModeData`	`string` optional	The associated request body's raw mode data.
`requestObject`	`string` optional	A JSON-stringified representation of the associated request.
`responseCode`	`object` optional	The response's HTTP response code information.
`status`	`string` optional	The response's HTTP status text.
`text`	`string` optional	The raw text of the response body.
`time`	`string` optional	The time taken by the request to complete, in milliseconds.
`url`	`string` optional	The associated request's URL.

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|object optional|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|object optional|

Tool: createSpec

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

Note:

Postman supports OpenAPI 2.0, OpenAPI 3.0, OpenAPI 3.1, AsyncAPI 2.0, protobuf 2 and 3, and GraphQL 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.
Private and Partner Workspaces are available on Postman Team and Enterprise plans.
There are rate limits when publishing public workspaces.
Public team workspace names must be unique.
The `teamId` property must be passed in the request body if Postman Organizations is enabled. Parameters|Type|Description -|-|- workspace|object optional|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.

Parameters	Type	Description
`collectionId`	`string`	The collection's unique ID.
`workspace`	`string`	The workspace ID in which to duplicate the collection.
`suffix`	`string` optional	An optional suffix to append to the duplicated collection's name.

Tool: generateCollection

Parameters	Type	Description
`elementType`	`string`	The `collection` element type.
`name`	`string`	The generated collection's name.
`options`	`object`	The advanced creation options and their values. For more details, see Postman's https://github.com/postmanlabs/openapi-to-postman/blob/develop/OPTIONS.md. These properties are case-sensitive.
`specId`	`string`	The spec's ID.

Tool: generateSpecFromCollection

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

Parameters	Type	Description
`collectionUid`	`string`	The collection's unique ID.
`elementType`	`string`	The `spec` value.
`format`	`string`	The format of the API specification.
`name`	`string`	The API specification's name.
`type`	`string`	The specification's type.

Tool: getAllSpecs

Gets all API specifications in a workspace.

Parameters	Type	Description
`workspaceId`	`string`	The workspace's ID.
`cursor`	`string` optional	The pointer to the first record of the set of paginated results. To view the next response, use the `nextCursor` value for this parameter.
`limit`	`integer` optional	The maximum number of rows to return in the response.

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

Get information about a collection. By default this tool returns the lightweight collection map (metadata + recursive itemRefs). Use the model parameter to opt in to Postman's full API responses:

model=minimal — root-level folder/request IDs only
model=full — full Postman collection payload. Parameters|Type|Description -|-|- collectionId|string|The collection ID must be in the form <OWNER_ID>- (e.g. ***-33823532ab9e41c9b6fd12d0fd459b8b). access_key|string optional|A collection's read-only access key. Using this query parameter does not require an API key to call the endpoint. model|string optional|Optional response shape override. Omit to receive the lightweight collection map. Set to minimal for the Postman minimal model or full for the complete collection payload.

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.

Parameters	Type	Description
`workspace`	`string`	The workspace's ID.
`limit`	`integer` optional	The maximum number of rows to return in the response.
`name`	`string` optional	Filter results by collections that match the given name.
`offset`	`integer` optional	The zero-based offset of the first item to return.

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

Tool: getDuplicateCollectionTaskStatus

Gets the status of a collection duplication task.

Parameters	Type	Description
`taskId`	`string`	The task's unique ID.

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

Tool: getEnabledTools

IMPORTANT: Run this tool first when a requested tool is unavailable. Returns information about which tools are enabled in the full and minimal tool sets, helping you identify available alternatives.

Tool: getEnvironment

Gets information about an environment.

Parameters	Type	Description
`environmentId`	`string`	The environment's ID.

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

Tool: getEnvironments

Gets information about all of your environments.

Parameters	Type	Description
`workspace`	`string` optional	The workspace's ID.

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

Tool: getGeneratedCollectionSpecs

Gets the API specification generated for the given collection.

Parameters	Type	Description
`collectionUid`	`string`	The collection's unique ID.
`elementType`	`string`	The `spec` value.

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|string optional|Return only results that belong to the given team ID.
For team-scoped requests, set this from GET /me (me.teamId).

workspace|string optional|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.

Parameters	Type	Description
`specId`	`string`	The spec's ID.

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

Tool: getSpecCollections

Gets all of an API specification's generated collections.

Parameters	Type	Description
`elementType`	`string`	The `collection` element type.
`specId`	`string`	The spec's ID.
`cursor`	`string` optional	The pointer to the first record of the set of paginated results. To view the next response, use the `nextCursor` value for this parameter.
`limit`	`integer` optional	The maximum number of rows to return in the response.

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

Tool: getSpecDefinition

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

Parameters	Type	Description
`specId`	`string`	The spec's ID.

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

Tool: getSpecFile

Gets the contents of an API specification's file.

Parameters	Type	Description
`filePath`	`string`	The path to the file.
`specId`	`string`	The spec's ID.

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

Tool: getSpecFiles

Gets all the files in an API specification.

Parameters	Type	Description
`specId`	`string`	The spec's ID.

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

Tool: getTaggedEntities

Requires an Enterprise plan. Tagging is only available on Postman Enterprise plans. This tool returns a 404 error on Free, Basic, and Professional accounts.

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

Parameters	Type	Description
`slug`	`string`	The tag's ID within a team or individual (non-team) user scope.
`cursor`	`string` optional	The cursor to get the next set of results in the paginated response. If you pass an invalid value, the API only returns the first set of results.
`direction`	`string` optional	The ascending (`asc`) or descending (`desc`) order to sort the results by, based on the time of the entity's tagging.
`entityType`	`string` optional	Filter results for the given entity type.
`limit`	`integer` optional	The maximum number of tagged elements to return in a single call.

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 (Team and Enterprise plans only).
`public` — Everyone can access the workspace.
`partner` — Only invited team members and partners can access the workspace (Team and Enterprise plans only). Parameters|Type|Description -|-|- workspaceId|string|The workspace's ID. include|string optional|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&cre