TestingOps.ai

MCP tools for agents · MCP tool for agents

Postman and TestingOps: your API collections as a tool for test agents

Connect Postman's MCP server and TestingOps agents can look up the collections, requests and environments in your Postman workspaces while they design and check API tests.

  • MCP tool for agents
  • Available
Request a demo Postman MCP server
Connection
MCP tool for agents
Writes back
Only after a person approves
Last checked
7 Nov 2026

In short

Postman and TestingOps in short

The Postman connection is an MCP tool: after you paste a Postman API key under Integrations → API & MCP, TestingOps agents can call Postman's hosted MCP server while they work.

Agents can then read the workspaces, collections and environments that key can see, for example to base API test steps on the requests your team already maintains, within the tools Postman's server offers.

Nothing is imported by itself, tools that change your workspace ask for approval first, and the key carries all of its user's permissions, so use an account that sees only the workspaces agents need.

What it does

What it does for your testing

  1. 1

    Requests your team already maintains

    Input
    Collections and their requests in your Postman workspaces
    TestingOps
    Agents can look up a collection's requests, headers and example bodies while writing API test steps
    Output
    API steps that can follow the requests your API team uses
  2. 2

    The right environment values

    Input
    Postman environments and their variables
    TestingOps
    Agents can check which base address and variables an environment defines
    Output
    API steps aimed at the environment the case is meant for
  3. 3

    Workspace changes only with approval

    Input
    A Postman tool that creates or updates something
    TestingOps
    TestingOps pauses the call and asks for approval on the agent's task
    Output
    No collection or environment change through such a tool without an approved request

Step by step

How it works

  1. Create a Postman API keyIn Postman, generate an API key under Settings → Account settings → API keys. It is shown once and carries every permission of its user.
  2. Connect it in TestingOpsUnder Integrations → API & MCP, pick Postman in Extra tools your agents may use, paste the key into Postman API key and select Connect.
  3. Tools are listed and sortedTestingOps lists the tools Postman's server offers. Tools that Postman marks as read-only, or whose names say they read (get, list, search and similar), are open to agents; every other tool asks first.
  4. Agents call Postman during a taskWhen a task needs it, an agent calls a Postman tool through TestingOps. The key stays on the TestingOps server; the agent's run gets a one-hour token that can only list and call tools.

Importing a Postman collection file as API test cases is a separate feature on the test cases page (Postman collection). This MCP tool reads your Postman workspaces live and imports nothing.

Connect

Setup

  1. In Postman, open Settings → Account settings → API keys, select Generate API Key, name the key and generate it; copy the key (PMAK-…), which is shown once.
  2. In TestingOps, as customer admin, open Integrations → API & MCP and pick Postman under Extra tools your agents may use (outgoing, over MCP).
  3. Paste the key into Postman API key and select Connect. The message shows how many tools are ready for your agents.
  4. Use Refresh catalog on the connection row later to pick up new Postman tools. New or changed tools wait under Review tools on the same row; only the ones you tick open to agents.

Documentation: Postman MCP server

Where you connect it in TestingOps: Integrations → API & MCP → Extra tools your agents may use → Postman

Use cases

Use cases

Write API cases from an existing collection

Trigger
A story changes an endpoint that already has requests in a Postman collection
Uses
The collection's requests and the environment's variables
Agent activity
Can look up the request, its parameters and example responses, then write API steps that follow it
Result
API cases that start from the request your team maintains
Condition
The key's user must see that workspace

Check which environment a failing request used

Trigger
An API case fails on staging but passes elsewhere
Uses
The Postman environments for each stage
Agent activity
Can compare the base address and variables between the environments
Result
A configuration difference to confirm before a defect is filed

Find requests no case covers yet

Trigger
A test lead plans the API regression set
Uses
The collections of a workspace
Agent activity
Can list a collection's requests and compare them with the project's API cases
Result
A list of requests that may need cases
Condition
The comparison goes by request names and paths; review the list

Capabilities

Capabilities and limits

What is read

What Postman's MCP server offers to the key: workspaces, collections and their requests, environments and their variables

What is produced

Context for agents' API test design and failure analysis; the tool stores nothing in TestingOps by itself

Where it can write

  • Collections, environments or workspaces in Postman, only through tools Postman offers and the key allows
  • Every tool that is not marked read-only or named for reading asks first, including tools named run…

How it connects

Postman's hosted MCP server (https://mcp.postman.com/mcp) with your Postman API key in the Authorization header

Account and permissions

  • A Postman API key (PMAK-…) of an account that sees only the workspaces agents need
  • Customer admin (or Manage integrations) rights in TestingOps; the connection is visible only to agents working on your organisation's projects

Limits

  • Postman keys expire after the inactivity period set in Postman's API key settings
  • Write approvals are answered on the request by people in your organisation with Manage integrations rights, or by the TestingOps team; tools that delete also need the TestingOps team's formal approval
  • Tools added or changed later wait in quarantine after Refresh catalog until someone in your organisation with Manage integrations rights reviews them on the connection's row (the TestingOps team can too)
  • Agents running on Grok receive no MCP tools

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team keeps its payment API in a Postman workspace, with one environment per stage. After connecting Postman with the API key of a service account that sees only that workspace, the team asks an agent to write cases for a new refund endpoint.

The agent can look up the refund request in the collection and the staging environment's base address, and writes API steps that follow the team's own request. The cases go to review like any others.

Frequently asked questions

Is this the same as importing a Postman collection?

No. The Postman collection button on the test cases page turns a collection file into API test cases. This MCP tool lets agents read your Postman workspaces live during a task and stores nothing by itself.

Can agents run a collection?

Only if Postman's MCP server offers such a tool to your key. A tool named run… counts as a write, so each call waits for approval on the agent's task; an approved collection run can call your APIs, so choose the key's user accordingly.

Which workspaces can agents see?

Everything the key's user can see. Postman keys carry all of their user's permissions, so create the key for an account that sees only the workspaces agents need.

Who approves a write?

When an agent calls a Postman tool that is not marked read-only or named for reading, the call waits on the request as an Approve tool action card. People in your organisation with Manage integrations rights approve or reject it (the TestingOps team can too); the request expires after an hour, and an approved call runs once with the reviewed arguments.

Does the Postman key leave TestingOps?

Only towards Postman's MCP server. It is kept on the TestingOps server, and an agent's run gets a one-hour TestingOps token that can list and call tools, not the key itself.

Next step

Request a demo with a Postman workspace of your own to see what agents can look up in it.

Request a demoMore mcp tools integrations