Postman

Postman MCP Connector for Claude

A+

Bring your Postman API lifecycle to your AI — orchestrate collections, environments, API mocks, and check workspace health seamlessly.

6 tools Official Updated Jun 28, 2026 Official Vinkius Partner

Connect your Postman developer keys to any AI agent and bring the power of collaborative API design, testing, and monitoring into a pure LLM conversational context.

What you can do

  • Collections & Endpoints — Extract complete internal JSON schemas of your Postman Collections to teach your AI exactly how internal APIs work
  • Workspaces & Environments — Map development environments (Staging/Prod) and expose scoped variables autonomously
  • Mock Servers — List active API endpoints serving simulated JSON responses, crucial for checking decoupled front-ends
  • Health Monitors — Retrieve scheduled cron checks tracking test success and failure histories out-of-the-box

How it works

  1. Subscribe to this server
  2. Enter your Postman Developer API Key
  3. Start mapping REST definitions natively in Claude, Cursor, or any MCP client

No exporting JSONs or jumping back and forth to read raw cURL formats. Ask the AI how to hit an endpoint, and it reads your collection.

Who is this for?

  • Backend Engineers — quickly check if staging environment URLs differ from production without navigating the Postman app
  • Frontend Devs — ask the AI to retrieve exact HTTP payloads and Mock server URLs when building your UI bindings
  • QA Testers — monitor failing API scenarios actively reporting through Postman Scheduled Monitors
api-testingapi-documentationmock-serversrest-apicollection-managementendpoint-testing

6 tools expose this connector's capabilities to your AI agent.

list_collections

List all available API Collections on the connected Postman account

list_workspaces

List all available engineering team workspaces in Postman

list_environments

List development environments (Staging, Prod) and their variables configured in Postman

list_mocks

List configured Mock Servers on Postman to simulate API responses and test Front-Ends

list_monitors

List API health monitors, showing their schedules and last run status (Success/Failure)

get_collection

Download the complete internal schema of a Postman Collection. Exposes all API Endpoints, HTTP Methods, Headers, and Request Bodies for AI learning

See how to talk to your AI agent using Postman.

Are there any Mock servers currently simulating our Auth API?

I checked your Postman configurations and found 1 active mock server tied to 'User Onboarding Flows'. It exposes exactly 4 static JSON responses for `/login` and `/token` and operates at URL `https://c123.mock.pstmn.io`. Shall I pull its schema details?

Download our core API Collection. Tell me exactly what parameters I need to submit to the Create User endpoint.

I extracted Collection `col-x71...`, the 'Create User' endpoint (POST `/api/v2/users`) expects a JSON body containing `email` (string, required), `role` (string, defaults to 'viewer'), and `department_id` (number, required). Would you like me to write a Javascript snippet invoking it?

Did any of our scheduled Postman monitors fail over the weekend?

Looking at the `list_monitors` data, your 'Checkout Flow Monitor' failed consecutively on Saturday morning. The internal log indicates an assertion error mapping a `502 Bad Gateway` status on step 3 (`POST /cart`). All other monitors are currently healthy and passing.

Absolutely. If you use `get_collection` the AI unpacks the entire Postman hierarchy. Combine this by asking the AI to 'write a Python script to hit my Users Endpoint' and it will natively respect your headers, payload requirements, and auth settings without any context copy-pasting.

Related Connectors