Postman MCP connector for Manus

Turn an API spec into a ready Postman collection, mock and monitor

Connect Postman and hand Manus an OpenAPI file. It builds the collection with a folder for each feature, sets up environments and monitors, and gives the frontend a Postman mock server while the backend is still being built. For changes to a shared workspace, ask it to list them first and confirm before it goes ahead.

First, connect Postman in Manus
Payments team workspaceIllustration
Payments API4 requests
Charges
POSTCreate charge
GETGet charge
Refunds
POSTRefund a charge
Payouts
GETList payouts
EnvironmentStaging
GET{{baseUrl}}/v1/payoutsSend
Response200 OK142 ms386 B
{  "data": [    {      "id": "po_1042",      "amount": 125000,      "currency": "usd",      "status": "paid",      "arrival_date": "2026-10-20"    }  ],  "has_more": false}
  • Status code is 200Passed
  • Response time is under 500 msPassed

Create a Postman collection from OpenAPI

Hand Manus an OpenAPI file. It adds the spec to Postman, generates a collection with a folder for each tag and keeps the two in sync when the spec changes.

openapi.yamlIllustration
openapi: 3.1.0info:  title: Payments API  version: 1.4.0paths:  /v1/charges:    post:      tags: [Charges]      summary: Create charge  /v1/charges/{id}:    get:      tags: [Charges]      summary: Get charge  /v1/charges/{id}/refunds:    post:      tags: [Refunds]      summary: Refund a charge  /v1/payouts:    get:      tags: [Payouts]      summary: List payouts
Payments API4 requests
Charges
POSTCreate charge
GETGet charge
Refunds
POSTRefund a charge
Payouts
GETList payouts
  • 3 folders by tag
  • 4 example responses

Turn an OpenAPI file into a Postman collection

Attach the spec. Manus adds it to your Postman workspace, then generates a collection with a folder for each tag and example responses from the spec.

Sync the Postman collection when the spec changes

Hand over the new version. Manus lists the endpoints that were added, changed or removed, then updates the spec and syncs the collection generated from it.

Set up a Postman mock server before the backend is ready

The frontend gets a URL that answers with your saved examples, and each stage gets its own environment, so the same requests work against the mock, staging or production.

Payments API mockIllustration
Mock server URL
https://mock.example.com
GET/v1/payouts200 OK
{  "data": [    {      "id": "po_1042",      "amount": 125000,      "currency": "usd",      "status": "paid",      "arrival_date": "2026-10-20"    }  ],  "has_more": false}

Returns the saved example for each request

EnvironmentsbaseUrl·apiKey
  • Mockhttps://mock.example.com••••••secret
  • Developmenthttp://localhost:4000••••••secret
  • Staginghttps://staging.example.com••••••secret
  • Productionhttps://api.example.com••••••secret

Give the frontend a mock server to call

Manus creates a mock server from your collection’s saved examples and gives you the URL, so the frontend can start before the backend is done.

Set up Postman environment variables for dev, staging and production

Each environment gets its own base URL. Keys stay as placeholder values marked secret, and you fill in the real ones in Postman.

Schedule a Postman API monitor and see what failed

Postman runs the collection from its cloud on a schedule. Manus sets up the monitor and reads the results, so you hear which request broke and when.

Payments API monitorEvery hour · Staging
Illustration
22/24runs passed in the last 24 hours
00:0006:0012:0018:0023:00
PassedFailed
  • 02:00POSTRefund a chargeExpected 201, got 504
  • 03:00POSTRefund a chargeExpected 201, got 504

Add an hourly monitor and get a short failure report

Postman runs the monitor on the schedule you pick. Manus reads the run results and tells you which request failed, when, and with what status.

Run a monitor now and see which check failed

Before a release, run the monitor on demand. Manus shows the failed checks and whether the test or the API looks wrong.

Generate API client code from your Postman collection

Manus reads the requests and example responses, then writes client code in TypeScript, Python or the language your project uses.

payouts.tsIllustration
1// Generated from Postman: Payments API › Payouts › List payouts2export interface Payout {3  id: string4  amount: number5  currency: string6  status: 'pending' | 'paid' | 'failed'7  arrival_date: string8}910const baseUrl = process.env.PAYMENTS_API_URL11const apiKey = process.env.PAYMENTS_API_KEY1213export async function listPayouts(limit = 10): Promise<Payout[]> {14  const res = await fetch(`${baseUrl}/v1/payouts?limit=${limit}`, {15    headers: { Authorization: `Bearer ${apiKey}` },16  })17  if (!res.ok) throw new Error(`List payouts failed: ${res.status}`)18  const body: { data: Payout[] } = await res.json()19  return body.data20}

Write a client function from a saved request

Manus reads the request, its parameters and its example responses, then writes a typed function in the language your project uses.

Find the right request and write the code to call it

Not sure which collection has it? Manus searches your team’s Postman workspaces first, then writes the call in Python or another language.

Clean up your Postman workspace

Find duplicate and forgotten collections, fill in missing docs and decide what to keep. Ask for a list first, and confirm before anything is deleted, moved or published.

Payments team workspaceIllustration
  • Payments APIUpdated 2 days ago
    Keep
  • Payments API copyDuplicate of Payments API, updated 8 months ago
    Delete
  • Payments API v1 (old)Not updated in 11 months
    Move to Archive
  • Checkout sandboxUpdated last week
    Keep
2 changes waiting for your OKConfirm changes

Find duplicate and outdated collections

To clean up Postman workspace clutter, Manus compares names, requests and last-updated dates, then suggests what to keep, delete or move. Ask for the list first, and confirm before anything is deleted or moved.

Fill in missing descriptions, then publish the docs

Manus lists requests with no description and drafts them for you to check. After you approve, it saves them and publishes the docs, which anyone with the link can see.

Postman MCP server setup in Manus

There’s nothing to install. Postman is already in Manus Connectors: connect your account once, and any task can use it as a Postman AI integration alongside your other connectors.

  1. Open Connectors

    In Manus, open Connectors, choose Postman, select Connect and connect your Postman account.

  2. Access follows your Postman account

    Manus sees and changes only the workspaces and elements your Postman role allows.

  3. Ask in any task

    Describe the API work in your own words. For changes to a shared workspace, ask it to list them first.

PostmanIllustration

Use Postman to create, update, and organize workspaces, collections, environments, API specs, mock servers, and monitors. Search, generate, sync, and publish your API resources directly from a conversation.

Connect
Access follows your Postman account
What it works with
  • Workspaces
  • Collections
  • Environments
  • API specs
  • Mock servers
  • Monitors

Questions about the Postman MCP connector

How do I connect Postman to Manus?

Open Connectors in Manus, choose Postman, select Connect and connect your Postman account. After that, any task can use it. There’s no server address or config file to set up.

Will Manus mess up my team’s Postman workspace?

Manus works with the same access as your Postman account, so it can only create, edit or delete what your Postman role allows. For anything that changes a shared workspace, ask it to list the changes first, and say OK before it makes them.

Which Postman workspaces can Manus see?

Only the workspaces, collections and other elements your own Postman account can access. It can also search public APIs on the Postman API Network when you ask it to.

Are my API keys and Postman environment variables safe?

Keep real keys out of the chat. Ask Manus to create environments with placeholder values and mark keys as secret so they’re masked, then fill in the real values in Postman yourself. Values set through the Postman API are shared values, which sync to the Postman cloud and are visible to everyone in that workspace.

Do I need to write code to use it?

No. Describe what you want in plain words, like “build a collection from this OpenAPI file” or “which monitors failed last night”. Manus picks the Postman tools and does the steps. Developers save the time spent adding requests, folders and examples by hand.

What Postman AI features does the Manus connector cover?

Its Postman AI capabilities cover workspaces, collections, environments, API specs, mock servers and monitors. Manus can search, create, update and organize them, generate collections from specs, keep specs and collections in sync, and publish documentation or mock servers.

Is this the same as Postman Agent Mode?

No. Agent Mode is Postman’s own AI assistant, used inside Postman to send requests, fix errors, update tests and build Flows. Manus is a separate AI agent that works with your Postman workspace through the connector and links that work to your other tools, such as building a collection from a requirements doc or adding API changes to a team weekly report.

Is Manus a Postman AI agent?

Not in the sense of Postman’s AI Agent Builder, which is for building and testing your own AI agents, models and MCP servers in Postman. Manus is an AI agent that does the Postman work for you, such as building collections, setting up mocks and checking monitors.

Can I use it with internal APIs?

Yes for building collections, specs, environments and mock servers, because those live in your Postman workspace. Whether requests can reach an internal API depends on your network and permissions. Postman monitors run from the Postman cloud by default; for APIs on a private network, Postman offers Private API Monitoring and static IPs, which you set up in Postman.

I use the Postman Claude connector. Can I use Postman in Manus too?

Yes. The Postman Claude integration runs on the Postman MCP server, which works with MCP-compatible AI tools. In Manus, Postman is already in Connectors: connect your account once, and any task can use it.

Can Manus publish Postman documentation or a mock server?

Yes, when you ask. Publishing documentation makes it public to anyone with the link, and publishing a mock server sets its access to public, so ask for it only when you’re ready to share. On some Enterprise teams, only certain roles can publish documentation.

Does it count toward my Postman plan?

Yes. Postman counts MCP tool calls toward your plan’s monthly limit for Postman API calls. Check your Postman plan for the current limits.

Can Manus check my Postman monitors every morning?

Yes. Create a scheduled task, for example every weekday at 9 AM, and Manus checks the monitor runs from the night before and sends you a short list of the requests that failed.

Use Manus as your Postman API AI agent

Connect Postman in Manus