Postman MCP server

Read from the package source without running it. The installed server may list more.

• add_relations_to_api_version

  Link existing Postman entities (collections, environments, mocks, monitors) to an API version as relations. Specify which entity types to associate by providing their corresponding UIDs or IDs in the request body.

• create_apiwrite action

  Creates a new API with a default API Version. The request must include an `api` object with at least a `name` property, and returns the created API with full details including id, name, summary, and description.

• create_api_versionwrite action

  Creates a new API version within the specified API. Optionally copies schema and related resources (mocks, monitors, documentation, tests, etc.) from an existing API version.

• create_collectionwrite action

  Create a new Postman collection in Postman Collection v2 format. Returns the created collection's name, ID, and UID. Optionally specify a workspace via query parameter to create the collection in a specific workspace.

• create_collection_from_schemawrite action

  Create a new collection linked to an API schema with one or more relation types (contract test, integration test, test suite, or documentation). The collection serves as an organizational container for API-related artifacts.

• create_environmentwrite action

  Create a new environment with configuration variables. Optionally specify a workspace context via query parameter. Returns the created environment's name and unique identifier.

• create_fork_of_collectionwrite action

  Create a fork of an existing collection. The response includes the forked collection's name, ID, UID, and fork metadata. You can optionally specify a target workspace for the fork. Note: The fork is created with a default label 'Forked Collection' (Postman v10 API requires 'label', and the schema-declared 'name' field is rejected).

• create_mockwrite action

  Create a mock server for a collection, optionally resolving environment variables. You can specify a workspace context via query parameter to determine where the mock is created.

• create_monitorwrite action

  Create a new monitor that runs API tests on a specified schedule. The monitor will execute a Postman collection in a given environment at intervals defined by a cron expression and timezone.

• create_schemawrite action

  Creates a new schema for an API version. The schema can be defined in OpenAPI (v1, v2, v3), RAML, or GraphQL format with corresponding language specification.

• create_webhookwrite action

  Create a webhook that automatically triggers a specified collection when the webhook URL is called. The webhook URL is returned in the response for use in external systems.

• create_workspacewrite action

  Create a new workspace and optionally populate it with collections, environments, mocks, and monitors by their unique identifiers. Returns the created workspace name and ID.

• delete_apiwrite action

  Permanently deletes an API by its ID. Returns the deleted API object with its ID for confirmation.

• delete_api_versionwrite action

  Permanently deletes a specific API version. Returns the id of the deleted API version.

• delete_collectionwrite action

  Permanently delete a collection by its unique identifier. Returns the deleted collection's id and uid upon successful deletion.

• delete_environmentwrite action

  Permanently delete a single environment by its unique identifier. This action cannot be undone.

• delete_mockwrite action

  Permanently delete an existing mock by its unique identifier. This operation removes the mock and all associated data.

• delete_mock_publicationwrite action

  Unpublish a mock by its unique identifier. This removes the mock from published state, making it unavailable for use.

• delete_monitorwrite action

  Permanently delete an existing monitor by its unique identifier. This operation removes the monitor and all associated data.

• delete_workspacewrite action

  Permanently delete an existing workspace by its ID. Returns the ID of the deleted workspace upon successful completion.

• get_api

  Retrieve detailed information about a specific API by its ID, including metadata such as name, summary, and description.

• get_api_version

  Retrieve detailed information about a specific API version, including its configuration and metadata.

• get_authenticated_user

  Retrieve detailed information about the authenticated user, including username, full name, email address, and other profile data. Requires API Key authentication via X-Api-Key header or apikey query parameter.

• get_collection

  Retrieve the full contents of a specific collection by its unique identifier. You must have access permissions to the collection to retrieve it.

• get_documentation_relations

  Retrieves all documentation relations linked to a specific API version, organized by relation type with complete details for each relation.

• get_environment

  Retrieve the full contents of a specific environment by its unique identifier. This operation requires authentication via API Key.

• get_environment_relations_for_api_version

  Retrieves all environment relations linked to a specific API version, organized by relation type with complete details for each relation.

• get_mock

  Retrieve detailed information about a specific mock by its unique identifier. Requires API Key authentication via X-Api-Key header or apikey query parameter.

• get_monitor

  Retrieve detailed information about a specific monitor using its unique identifier. This operation requires authentication via API key.

• get_schema

  Retrieves a single schema by its ID. Returns a schema object containing metadata including id, language, type, and schema definition.

• get_workspace

  Retrieve a workspace by its ID, including all associated collections, environments, mocks, and monitors that you have access to.

• list_api_versions

  Retrieve all versions of a specified API, including detailed metadata for each version.

• list_apis

  Retrieve all APIs in a workspace with optional filtering by metadata, timestamps, privacy state, and text search. Results can be sorted by any response field in ascending or descending order.

• list_collections

  Retrieve all collections accessible to you, including your own collections and those you have subscribed to. Each collection includes its name, ID, owner, and UID.

• list_contract_test_relations

  Retrieves all contract test relations linked to a specific API version, organized by relation type with complete details for each relation.

• list_environments

  Retrieve a list of all environments you own, including their names, IDs, owners, and UIDs. Requires API Key authentication.

• list_integration_test_relations

  Retrieves all integration test relations linked to a specific API version, organized by relation type with complete details for each relation.

• list_linked_relations

  Retrieve all relations linked to a specific API version, including detailed information about each relation type and its associated relations.

• list_mocks

  Retrieve all mocks you have created. Returns a complete list of your mock configurations for managing and testing API responses.

• list_monitor_relations

  Retrieves all monitor relations linked to a specific API version, organized by relation type with complete details for each relation.

• list_monitors

  Retrieve a list of all monitors accessible to you, including their name, ID, owner, and unique identifier. Requires API Key authentication.

• list_test_suite_relations

  Retrieves all test suite relations linked to a specific API version, organized by relation type with complete details for each relation.

• list_workspaces

  Retrieve a list of all workspaces accessible to you, including your own workspaces and those shared with you. Each workspace entry includes its name, ID, and type.

• merge_fork_to_collection

  Merge a forked collection back into its destination collection. Optionally specify a merge strategy to control whether the source fork is deleted or updated with destination changes after the merge.

• publish_mockwrite action

  Publishes a mock that you have created, making it available for use. Requires the mock's unique identifier (uid) and API key authentication.

• run_monitorwrite action

  Executes a monitor immediately and waits for completion, returning the run results. This is a synchronous operation that blocks until the monitor finishes executing.

• sync_relation_with_schema

  Synchronize a relation (such as documentation, contract test, or monitor) with the current API schema to ensure consistency and alignment with schema changes.

• update_apiwrite action

  Update an existing API by modifying its name, summary, or description. Returns the complete updated API object with all current details.

• update_api_versionwrite action

  Update the name of an existing API version. Provide the API ID and version ID, along with the new name in the request body.

• update_collectionwrite action

  Replace an existing collection with updated content in Postman Collection v2 format. Returns the updated collection's name, id, and uid. Requires API Key authentication.

• update_environmentwrite action

  Replace an existing environment with updated configuration. Specify the environment to modify by its unique identifier and provide the new environment name and variable values.

• update_mockwrite action

  Update an existing mock server by its unique identifier. Modify properties such as name, description, environment, privacy settings, and version tag.

• update_monitorwrite action

  Update an existing monitor's name and execution schedule. Modify the monitor identified by its unique identifier to change its display name and/or cron-based execution frequency and timezone.

• update_schemawrite action

  Update an existing API schema by replacing its content and metadata. Supports OpenAPI (v1, v2, v3), RAML, and GraphQL schema types in their respective formats.

• update_workspacewrite action

  Update a workspace's properties and manage its associations with collections, environments, mocks, and monitors. The endpoint replaces all associated entities with those specified in the request, so omitted entities will be removed from the workspace.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 60% of 48,255 servers

Tools

55

the typical server has 7

Tools that change things

53%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

31

more than 92% of 28,688 servers

Downloads a week

153

more than 71% of 12,191 servers with a package

Postman: common questions

Is Postman MCP server safe?

Mostly: it is graded B (80/100). Read the Postman safety report

How do I install Postman?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Postman need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Postman maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.2.

How does Postman compare with other MCP servers?

safety score 80/100 (higher than 60% of 48,255 servers); tools 55 (the typical server has 7); tools that change things 53% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.