Skip to main content

Postman

Create Postman collections, environments, and mocks for the APIs you're building.

Tools

41 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

41 tools found.

  • Create collection

    Tool name: createCollection

    Creates a collection using the [Postman Collection v2.1.0 schema format](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html).

  • Create collection request

    Tool name: createCollectionRequest

    Creates a request in a collection.

  • Create collection response

    Tool name: createCollectionResponse

    Creates a request response in a collection.

  • Create environment

    Tool name: createEnvironment

    Creates an environment.

  • Create mock

    Tool name: createMock

    Creates a mock server in a collection.

  • Create spec

    Tool name: createSpec

    Creates an API specification in Postman's [Spec Hub](https://learning.postman.com/docs/design-apis/specifications/overview/).

  • Create spec file

    Tool name: createSpecFile

    Creates a file for an OpenAPI or a protobuf 2 or 3 specification.

  • Create workspace

    Tool name: createWorkspace

    Creates a new [workspace](https://learning.postman.com/docs/collaborating-in-postman/using-workspaces/creating-workspaces/).

  • Duplicate collection

    Tool name: duplicateCollection

    Creates a duplicate of the given collection in another workspace.

  • Generate collection

    Tool name: generateCollection

    Creates a collection from the given API specification.

  • Generate spec from collection

    Tool name: generateSpecFromCollection

    Generates an OpenAPI 2.0, 3.0, or 3.1 specification for the given collection.

  • Get all specs

    Tool name: getAllSpecs

    Gets all API specifications in a workspace.

  • Get authenticated user

    Tool name: getAuthenticatedUser

    Gets information about the authenticated user.

  • Get collection

    Tool name: getCollection

    Model=minimal — root-level folder/request IDs only

  • Get collections

    Tool name: getCollections

    The workspace ID query is required for this endpoint.

  • Get duplicate collection task status

    Tool name: getDuplicateCollectionTaskStatus

    Gets the status of a collection duplication task.

  • Get enabled tools

    Tool name: getEnabledTools

    Returns information about which tools are enabled in the full and minimal tool sets, helping you identify available alternatives.

  • Get environment

    Tool name: getEnvironment

    Gets information about an environment.

  • Get environments

    Tool name: getEnvironments

    Gets information about all of your [environments](https://learning.postman.com/docs/sending-requests/managing-environments/).

  • Get generated collection specs

    Tool name: getGeneratedCollectionSpecs

    Gets the API specification generated for the given collection.

  • Get mock

    Tool name: getMock

    Gets information about a mock server.

  • Get mocks

    Tool name: getMocks

    Gets all active mock servers.

  • Get spec

    Tool name: getSpec

    Gets information about an API specification.

  • Get spec collections

    Tool name: getSpecCollections

    Gets all of an API specification's generated collections.

  • Get spec definition

    Tool name: getSpecDefinition

    Gets the complete contents of an OpenAPI or AsyncAPI specification's definition.

  • Get spec file

    Tool name: getSpecFile

    Gets the contents of an API specification's file.

  • Get spec files

    Tool name: getSpecFiles

    Gets all the files in an API specification.

  • Get tagged entities

    Tool name: getTaggedEntities

    Tagging is only available on Postman Enterprise plans.

  • Get workspace

    Tool name: getWorkspace

    Gets information about a workspace.

  • Get workspaces

    Tool name: getWorkspaces

    Gets all workspaces you have access to.

  • Publish mock

    Tool name: publishMock

    Publishes a mock server.

  • Put collection

    Tool name: putCollection

    Replaces the contents of a collection using the [Postman Collection v2.1.0 schema format](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html).

  • Put environment

    Tool name: putEnvironment

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

  • Search Postman elements

    Tool name: searchPostmanElements

    Search for Postman entities (requests, collections, workspaces, specs, flows, environments, mocks, and documents).

  • Sync collection with spec

    Tool name: syncCollectionWithSpec

    Syncs a collection generated from an API specification.

  • Sync spec with collection

    Tool name: syncSpecWithCollection

    Syncs an API specification linked to a collection.

  • Update collection request

    Tool name: updateCollectionRequest

    Updates a request in a collection.

  • Update mock

    Tool name: updateMock

    Updates a mock server.

  • Update spec file

    Tool name: updateSpecFile

    Updates a file for an OpenAPI or protobuf 2 or 3 specification.

  • Update spec properties

    Tool name: updateSpecProperties

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

  • Update workspace

    Tool name: updateWorkspace

    Updates a workspace's property, such as its name or visibility.

Compatibility

Connect Postman to the clients your teams already use

27 AI clients can connect to Postman through Runlayer. Pick one for its setup steps and controls.

Why Runlayer

Why connect Postman through Runlayer?

One approved path

Approve Postman once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.

Frequently asked questions