developer-toolsapi_key

Postman

Postman is an API platform for building, testing, and managing APIs with powerful collaboration features.

Verdict

The Postman MCP turns your team's API workspace into a conversational interface. @mention it to create collections, spin up mock servers, schedule monitors, or fork existing work — all without leaving chat. Developers get instant scaffolding for new endpoints; QA can automate smoke tests on a cron; product managers can comment on collections to flag breaking changes. You'll need a Postman API key with workspace write access. The MCP can't run requests or inspect responses directly — it manages workspace artifacts, not live traffic.

Common use cases

Scaffold new API collections from chat
Schedule monitors for nightly regression runs
Fork production collections into staging workspace
Add review comments to shared endpoints
Spin up mock servers for frontend dev

Integration

Vendor: Postman
Category: developer-tools
Auth: API_KEY
Tools: 50
Composio slug: postman

Tools

Create a Collection
Tool to create a new Postman collection in a specific workspace or the default workspace. Use when you need to create a collection with workspace specification. For complete collection format details, refer to the Postman Collection Format
Create a Collection Comment
Tool to create a comment on an API's collection. Use when you need to add a comment to a specific collection within an API. To create a reply on an existing comment, include the thread_id in the request.
Create a Folder
Tool to create a folder in a Postman collection. Use when you need to organize requests by creating a new folder within a collection. For complete details, see the Postman Collection Format documentation.
Create a Folder Comment
Tool to create a comment on a folder. Use when you need to add a comment to a specific folder in a collection.
Create a Fork
Tool to create a fork from an existing collection into a workspace. Use when you need to fork a collection to create an independent copy in a specific workspace.
Create a Mock Server
Tool to create a new mock server in a Postman collection. Use when you need to create a mock server to simulate API endpoints for testing or development. Returns the created mock server's details including the mockUrl which can be used to m
Create a Monitor
Tool to create a new monitor in a specific workspace to run a collection on a schedule. Use when you need to set up automated collection runs at specified intervals using cron expressions within a workspace.
Create an API
Tool to create a new API in a Postman workspace. Use when you need to create an API with a name and optional summary and description.
Create an API
Tool to create a new API in Postman. Use when you need to create an API with a name, summary, and description in your Postman workspace.
Create an Environment
Tool to create a new environment in a Postman workspace. Use when you need to create a new environment with variables for different settings (development, production, testing, etc.). Returns the created environment's ID, name, and UID upon
Create API Schema
Tool to create a schema for an API in Postman. Use when you need to add a schema definition (such as OpenAPI, GraphQL, or Protocol Buffers) to an existing API. The schema can consist of single or multiple files. Returns the created schema's
Create API Version Relations
Tool to create new relations for an API version. Use when you need to link collections or mock servers to an API version as contract tests, test suites, documentation, or mocks.
Create a Pull Request
Tool to create a pull request for a forked collection into its parent collection. Use when you need to propose changes from a forked collection to be merged into the parent collection. The forked collection must exist before creating a pull
Create a Request Comment
Tool to create a comment on a request. Use when you need to add a comment to a specific request within a collection or reply to an existing comment thread.
Create a Response
Tool to create a request response in a Postman collection. Use when you need to add a saved response example to a specific request in a collection.
Create a Response Comment
Tool to create a comment on a response. Use when you need to add a comment to a specific response within a collection or reply to an existing comment thread.
Create a Spec
Tool to create an API specification in Postman's Spec Hub. Use when you need to create single or multi-file specifications in a workspace. Supports various spec types including OpenAPI 3.0, OpenAPI 3.1, and AsyncAPI 2.0.
Create a Webhook
Tool to create a webhook that triggers a collection with a custom payload. Use when you need to set up a webhook endpoint that can trigger a Postman collection run. The webhook URL is available in the webhookUrl property of the response.
Create a Workspace
Tool to create a new workspace in Postman. Use when you need to create a workspace with a specified name, type (personal, team, private, or public), and optional description. Returns the created workspace's ID, name, and type upon successfu
Create Collection
Tool to create a new Postman collection with specified name and configuration. Use when you need to create a new collection in Postman workspace. Returns the created collection's ID, name, and UID upon successful creation.
Create Collection from Schema
Tool to create a collection from a schema and link it to an API with specified relations. Note: This endpoint is deprecated in Postman v10 and higher. Use when you need to generate a collection from an API schema and establish relations lik
Create Environment
Tool to create a new Postman environment with specified name and variables. Use when you need to create a new environment in Postman workspace. Returns the created environment's ID, name, and UID upon successful creation.
Create Environment Fork
Tool to create a fork from an existing environment into a workspace. Use when you need to fork an environment to a specified workspace.
Create Mock Server
Tool to create a new mock server for a Postman collection. Use when you need to set up a mock server that simulates API responses based on saved examples in a collection.
Create Mock Server Response
Tool to create a server response on a Postman mock server. Use when you need to simulate 5xx server-level responses (500, 503, etc.) for testing error conditions.
Create Monitor
Tool to create a new monitor to run a collection on a schedule. Use when you need to set up automated collection runs at specified intervals using cron expressions.
Create or Update a Schema File
Tool to create or update an API schema file in Postman. Use when you need to add a new schema file or modify an existing one within an API schema. Requires API ID, schema ID, file path, and stringified JSON content.
Create Request in Collection
Tool to create a new request in a Postman collection. Use when you need to add a request to an existing collection with specified method, URL, headers, and body.
Create Spec File
Tool to create a new file in an API specification. Use when you need to add a new file (such as schema definitions, path configurations, or components) to an existing spec.
Create Webhook
Tool to create a new webhook for a Postman collection. Use when you need to create a webhook that triggers a collection when called. Returns the created webhook's ID and name upon successful creation.
Delete a Collection
destructive
Tool to permanently delete a collection from Postman. Use when you need to remove a collection that is no longer needed.
Delete a collection's comment
destructive
Tool to delete a comment from an API's collection. Use when you need to remove a specific comment from a collection. On success, returns HTTP 204 No Content.
Delete a Folder
destructive
Tool to delete a folder in a Postman collection. Use when you need to remove a folder and all its contents from a collection. The folder ID should not contain spaces to avoid 404 errors.
Delete a Folder's Comment
destructive
Tool to delete a comment from a folder. Use when you need to remove a specific comment from a folder. Returns HTTP 204 No Content on successful deletion.
Delete an API
destructive
Tool to delete an API from Postman. Use when you need to permanently remove an API. On success, returns HTTP 204 No Content response.
Delete an API's Comment
destructive
Tool to delete a comment from an API. Use when you need to remove a comment from a specific API. On success, this returns an HTTP 204 No Content response indicating the comment was successfully deleted.
Delete an environment
destructive
Tool to delete an environment permanently in Postman. Use when you need to remove an environment that is no longer needed.
Delete a Request's Comment
destructive
Tool to delete a comment from a request. Use when you need to remove a specific comment from a request. On success, this returns an HTTP 204 No Content response.
Delete a Response
destructive
Tool to delete a response in a Postman collection. Use when you need to remove a saved response from a collection.
Delete a Response's Comment
destructive
Tool to delete a comment from a response. Use when you need to remove a specific comment from a collection response. On successful deletion, this returns HTTP 204 No Content.
Delete a Schema File
destructive
Tool to delete a file in an API schema. Use when you need to remove a specific file from a schema. On success, returns HTTP 204 No Content response.
Delete a Spec
destructive
Tool to delete an API specification from Postman. Use when you need to permanently remove a specification. On success, returns HTTP 204 No Content response.
Delete a Workspace
destructive
Tool to delete a Postman workspace permanently. Use when you need to remove a workspace and all its contents. Deletion is permanent and cannot be undone.
Delete Mock Server Response
destructive
Tool to delete a mock server's server response. Use when you need to remove a specific response from a Postman mock server.
Delete Monitor
destructive
Tool to delete a monitor by its ID. Use when you need to permanently remove a monitor from Postman. The monitor ID must be provided to identify which monitor to delete.
Delete Spec File
destructive
Tool to delete a file from an API specification. Use when you need to remove a specific file from a multi-file specification.
Duplicate a Collection
Tool to create a duplicate of a collection in another workspace. Use when you need to copy an existing collection to a different workspace. Returns an asynchronous task that can be tracked using the duplication task status endpoint.
Fork Collection
Tool to create a fork of a collection in a specified workspace. Use when you need to fork an existing collection to a workspace.
Generate Collection from Spec
Tool to generate a Postman collection from an OpenAPI 2.0, 3.0, or 3.1 specification. Use when you need to create a collection from an existing API spec. The operation is asynchronous and returns a task ID and polling URL to check the gener
Generate Spec from Collection
Tool to generate an API specification from a Postman collection. Use when you need to create an OpenAPI 3.0 specification from an existing collection. The operation is asynchronous and returns a task ID and polling URL to check the generati

Setup

Setup guide

11. In Switchy, open your Space settings and click 'Add Integration'. 2. Search for Postman and select it from the developer tools category. 3. Generate an API key in your Postman account under Settings → API Keys; grant it workspace and collection write scopes. 4. Paste the key into Switchy's auth field and click Connect. 5. Return to your Space and type '@Postman list my workspaces' to confirm the connection works. 6. To invoke a tool, @mention Postman in any message and describe what you need — for example, '@Postman create a collection called User Auth Endpoints in the QA workspace'. The MCP will execute the action and reply with confirmation or error details. If you manage multiple workspaces, specify the workspace name in your prompt to avoid ambiguity.

What teammates see: by default, memories from Postman are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

Create Test Collection

@Postman create a collection called 'Payment Gateway Tests' with a description 'End-to-end tests for Stripe integration'. Put it in the QA workspace.

Open in a Space →

Set Up Mock Server

@Postman create a mock server for the 'User Auth Endpoints' collection. Name it 'Auth Mock' and make it private.

Open in a Space →

Schedule Nightly Monitor

@Postman create a monitor in the Production workspace that runs the 'Smoke Tests' collection daily at 2 AM UTC. Name it 'Nightly Smoke Check'.

Open in a Space →

Fork for Experimentation

@Postman fork the 'Payments API' collection from Production into the Sandbox workspace. Label the fork 'Payments v2 Experiment'.

Open in a Space →

Comment on Endpoint

@Postman add a comment to the 'Legacy Auth' folder in the 'User Auth Endpoints' collection: 'This route is deprecated as of Q2. Migrate to /v2/auth by June 1.'

Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@postman list all collections in my default workspace and show me which ones have active monitors running

Output

Based on your Postman workspace, you have 7 collections. Three have active monitors: 'Payment API v2' runs every 6 hours checking endpoint health, 'User Service Integration' runs daily at 3am UTC, and 'Third-party Webhooks' runs every 15 minutes. The remaining collections ('Legacy Auth Flow', 'Internal Tools', 'Staging Environment Tests', 'Mobile App Endpoints') have no monitors configured. Would you like me to set up monitoring for any of these?

Notes

This read-heavy example demonstrates the MCP's ability to query workspace state and correlate collections with their monitoring configuration. Requires API key with read access to workspaces and monitors. Response accuracy depends on current workspace state—collections and monitor schedules will vary by account.

Prompt

@postman create a new collection called 'Customer Onboarding API' with folders for registration, verification, and profile setup, then add a mock server for local development

Output

Created collection 'Customer Onboarding API' in your default workspace with three folders: 'Registration Endpoints', 'Email Verification', and 'Profile Setup'. Added mock server at https://a3f8d2c1-mock.pstmn.io that will respond to requests matching your collection structure. The mock server is now active and will return example responses based on saved examples in each request. You can start making calls to the mock URL immediately for frontend development.

Notes

This write example chains multiple Postman operations—collection creation, folder organization, and mock server provisioning. Requires API key with write permissions. Mock server URLs are randomly generated and persist until explicitly deleted. Be aware that mock servers count against your workspace's mock server limit (varies by Postman plan tier).

Prompt

@postman review all failed monitor runs from the past week and create a summary comment on the affected collections explaining common failure patterns

Output

Analyzed 23 monitor runs across 4 collections in the past 7 days. Found 8 failures, primarily in 'Payment API v2' (5 failures) and 'Third-party Webhooks' (3 failures). Common patterns: timeout errors on POST /payments/process (4 occurrences, avg response time 31s vs 5s threshold), and 401 authentication failures on webhook endpoints (3 occurrences, likely expired tokens). Added summary comments to both collections detailing failure timestamps, affected endpoints, and recommended fixes: increase timeout threshold for payment processing, implement token refresh logic for webhook authentication.

Notes

This synthesis example combines the MCP's monitoring data retrieval with AI reasoning to identify patterns and automatically document findings. Demonstrates how Switchy can turn raw API monitoring data into actionable team communication. Requires read access to monitors and write access to create comments. Monitor history retention depends on your Postman plan—free plans retain 7 days, paid plans retain more.

Use-case deep-dives

API contract review in distributed teams

When Postman MCP speeds up async API design feedback

A 6-person backend team spread across three time zones needs to review and comment on API contracts before implementation. The Postman MCP lets Switchy agents create collections, add folder-level comments, and fork experimental versions without anyone opening the Postman web UI. This works when your team already uses Postman as the source of truth for API specs—Switchy becomes the comment layer that runs in Slack or your chat tool. The threshold: if your team doesn't already have Postman collections for every service, you're adding overhead instead of removing it. Best fit for teams that treat collections like living docs and need faster feedback loops on endpoint changes. If you're doing this more than twice a week, the MCP pays off in saved context-switching.

Mock server spin-up for frontend prototyping

When this MCP wins for rapid frontend iteration

A 3-person product team building a new dashboard needs mock API endpoints so the designer can prototype interactions before backend work starts. The Postman MCP's mock server tool lets a Switchy agent create and configure mocks from a collection in under a minute—no manual Postman setup, no waiting for backend availability. This is the right call when you're prototyping user flows that depend on realistic API responses and your team already has Postman collections defining those endpoints. If you're starting from scratch with no existing collections, you'll spend more time defining the collection structure than you save. Ideal for teams running week-long design sprints where frontend and backend work in parallel. The mock server tool is the standout here—most other Postman automation focuses on testing, not prototyping.

Scheduled API health monitoring setup

When monitor creation belongs in your chat workflow

A 2-person SaaS ops team needs to add uptime monitors for three new API endpoints after each deploy. The Postman MCP's monitor tool lets them configure cron-based collection runs from Switchy without leaving their incident channel. This works when you already have collections that double as health checks and you're adding monitors frequently enough that the Postman UI becomes a bottleneck. The trade-off: if you're setting up monitors once a quarter, the MCP is overkill—just use Postman directly. Best for teams shipping new endpoints weekly and treating monitors as part of the deploy checklist, not a separate ops task. The 50-tool count suggests broad Postman coverage, but monitor creation is the specific win for ops-heavy workflows.

Frequently asked

What does the Postman MCP let me do in Switchy?

It lets your AI agents create and manage Postman collections, folders, mock servers, and monitors directly from chat. Agents can fork collections, add comments, set up scheduled runs, and organize API requests without you switching to the Postman UI. Useful when you're prototyping APIs or coordinating test coverage across the team.

Do I need a paid Postman plan to use this MCP?

You need a Postman API key, which requires at least a free Postman account. Some tools — like creating monitors or mock servers — may hit workspace or usage limits on Postman's free tier. Check your Postman plan's quotas before connecting. The MCP itself doesn't charge extra; it just calls Postman's API on your behalf.

Can the Postman MCP send actual HTTP requests or run collections?

No. It creates and configures collections, folders, monitors, and mocks, but it doesn't execute requests or return API responses. To run a collection, you still use Postman's UI, CLI, or a monitor you've set up via the MCP. Think of this as the scaffolding layer, not the execution layer.

Why use this instead of just opening Postman?

You save context-switching when an AI agent can scaffold a collection structure, add comments, or fork a baseline while you're already in a Switchy conversation. It's faster for repetitive setup tasks — like creating a dozen folders or scheduling monitors — than clicking through Postman's UI manually.

Who on the team should connect the Postman MCP?

Whoever owns your team's Postman workspace and has an API key with write permissions. That's usually a backend lead or QA engineer. Once connected in Switchy, any teammate in the workspace can ask agents to create collections or monitors, but the actions run under the connected account's permissions.