Skip to content

Application Development

Postman MCP connector

The Postman connector lets Claude, ChatGPT, Cursor and other AI clients read and update your Postman APIs, collections, schemas and comments, with every call made as the signed-in person and recorded in an audit log.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Postman to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Postman once

  1. Open Connections, choose Add connection, and pick Postman.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Postman API key. One person generates a token in Postman and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

postman
Postman
Apache Airflow
Boomi
Browserbase
Caspio
Cloudflare
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Postman to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Postman to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Postman to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Postman to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Postman through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Engineering

    Find the API before the meeting

    Ask for an API by name and get its description, collections and attached schemas without opening Postman and clicking through workspaces.

  • Platform

    Register a new API with its schema

    Describe the service in plain language and have the API created in Postman with its schema file attached, ready for the team to build on.

  • QA

    Leave review notes on a collection

    After a test run, add comments to the collection or the API that explain what failed and what needs a second look, so the owner sees it in Postman.

  • API governance

    Tidy tags and descriptions in bulk

    Pull the list of APIs, spot the ones missing an owner tag or a description, and update them together instead of one at a time.

  • Developer relations

    Summarize what changed across APIs

    Ask which APIs and collections were updated this week and turn the answer into a changelog draft for partners and external developers.

  • Product

    Read usage analytics without a dashboard

    Ask which Postman APIs are getting the most attention according to analytics, and get a plain answer you can paste into a roadmap update.

Try asking

  • “Which Postman collections changed this week, and who edited them”
  • “List unresolved comments on our public Postman APIs”
  • “Show Postman API collections tagged for the payments release”

See all 244 Postman tools below

AI tools

Postman tools for your AI agents

244 tools are ready to call through Elaichi's MCP endpoint the moment you connect Postman, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Postman gets you

6 screens from the product, each doing one job for your Postman account.

The agent

Ask about Postman APIs in plain language.

Questions about collections, APIs and comments answered from live Postman records.

  • apis
  • collections
  • comments
  • tags

Ask Elaichi to work across your apps.

Which Postman collections changed this week, and who edited them

List unresolved comments on our public Postman APIs

Show Postman API collections tagged for the payments release

Also runs in Claude, ChatGPT or Cursor

MCP clients

One Postman endpoint for every MCP client.

Claude, ChatGPT and Cursor connect over OAuth, no SDK, no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

244 Postman tools, no custom code.

APIs, collections, comments, tags and analytics, each with resources and methods listed.

  • List all Postman analytics
  • List all Postman analytics metadatas
  • List all Postman apis
  • Create a Postman API
ElaichiTools
Tool Action Description
List all Postman analytics List Get Postman analytics data for a given resource and metric, with optional filters for workspace type, duration, period, user type, and entity type. Returns metric-specific analytics data whose shape varies by the resource:metric combination. Required: resource, metrics.
List all Postman analytics metadatas List List Postman analytics metadata — a catalog of analytics resources and their corresponding metrics for use with the GET /analytics endpoint. Returns the analytics metadata catalog with available resources, metrics, and optionally detailed parameter and response schema information. Filter by resources (user, workspace, team, ai) or specific metric values.
List all Postman apis List List all APIs in a Postman workspace, optionally filtered by creator or description text. Returns each API's id, name, summary, and description. Required: workspace_id.
Create a Postman API Create Create an API in a Postman workspace. Returns the created API object including its id, name, summary, and description. Required: workspace_id, name.
Get single Postman API by ID Get Get a single Postman API by id. Returns: id, description, schemas. Required: id.

Toolboxes

Every team gets its own Postman toolbox.

Curate one toolbox per team and scope it to that team only.

  • Platform engineering
  • QA
  • Developer experience
  • API governance
ElaichiToolboxes
Name Source template Tools Created

Platform engineering toolbox

Postman · APIs and versions

Postman starter 18 Mar 4, 2026

QA toolbox

Postman · collections and test runs

9 Mar 2, 2026

Developer experience toolbox

Postman · documentation and comments

24 Feb 27, 2026

API governance toolbox

Postman · tags and bulk updates

Postman starter 6 Feb 19, 2026

Partner integrations toolbox

Postman · shared collections

31 Jan 30, 2026

Analytics toolbox

Postman · usage metrics and reports

12 Jan 22, 2026

Shared connections

Teammates use Postman without seeing credentials.

Each connection shows who connected it and which teams and members share it.

  • Platform team
  • QA EMEA
  • Developer experience
  • Partner APIs
ElaichiConnections
Connection Scope Status Access
PO

Postman (Platform team)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
PO

Postman (QA EMEA)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
PO

Postman (Developer experience)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
PO

Postman (Partner APIs)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
PO

Postman (Internal tooling)

Connected by Clara Nowak

Personal • Active Not shared
PO

Postman (API governance)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Answer who changed which Postman collection.

Append-only log of when, who, what happened, type and resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Postman Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Postman Apis Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Postman Apis List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, Postman work gets done.

Fetch APIs, group them, draft a digest, approve it, post a comment back.

Postman digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch apis

    Postman

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Postman

    Queued

Collections and dashboards

Postman health in numbers, refreshed on schedule.

Four metrics, 14 days of collections created, and a breakdown by team.

Postman health

Refreshed 4 minutes ago · every 15 minutes · from the apis collection

Live

Apis

1,284 ↓ 12%

Collections

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Apis created

Last 14 days

By team

Share of activity

Platform team 34%

QA EMEA 27%

Developer experience 21%

Partner APIs 18%

FAQ

Frequently asked questions

How do I connect Postman to Claude?

First connect Postman in Elaichi by pasting a Postman API key, which you copy from your Postman account settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs in to Elaichi as you and Postman is ready to use.

Does Postman work with ChatGPT and Cursor as well as Claude?

Yes. Once Postman is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, the Elaichi Agent and any other MCP client. You connect Postman once and every client you use picks it up.

What can an AI agent actually do with my Postman data?

An agent connected to Postman can look up your APIs and collections, create new ones, update their details, attach schemas and schema files, add or edit comments, manage tags and read analytics. It can also update several APIs at once when you need to clean things up. Because Postman offers a lot of actions, short concrete asks such as "add a comment to the Payments collection" work better than long paragraphs.

Does connecting Postman give the AI access to every workspace?

No. The agent works with exactly what the Postman API key can see, so it never reaches a workspace, API or collection that the person who connected Postman could not open themselves. Elaichi can narrow that access further, for example to read-only, but it can never widen it.

Can my team share one Postman connection?

Yes. One person connects Postman in Elaichi and shares the connection with a team, and nobody else ever handles the Postman API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every change to an API, collection or comment.

Can I stop an agent from deleting or changing things in Postman?

Yes. In Elaichi you can block individual actions on the Postman connector, such as deleting an API or removing a comment, while leaving reading and creating available. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can trigger it.

What happens to a Postman connection when someone leaves?

When you offboard a person in Elaichi, their access to Postman through every AI client ends at once. A Postman connection they shared with a team keeps working for everyone else on it. If you want Postman gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

Put Postman in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.