# Run agents with Postman

Postman AI agents on Rush: connect Postman once, then name it on any run. The agent works in its own cloud computer, with a record of every run.

[Connect Postman](https://cloud.getrush.ai/console/settings/?section=connections) in the console under Settings → Connections.

## What an agent can do in Postman

Work with APIs in Postman: manage workspaces, collections, requests and environments, and run collections to test APIs.

## Jobs on Rush that use Postman

- [Did Our Public API Examples Break Overnight? An API Company's Postman Monitor Review](https://getrush.ai/run/review-overnight-api-monitor-failures/postman/)

## How Postman connects

Postman is a remote MCP server, published by Postman, at `https://mcp.postman.com/mcp`. Connecting it signs in through the MCP OAuth flow on Postman's side.

From Postman: [Postman's MCP documentation](https://learning.postman.com/docs/reference/postman-api/postman-mcp-server/postman-mcp-remote-server/) · [source code](https://github.com/postmanlabs/postman-mcp-server).

Connect it once in the console under Settings → Connections, or from your server with `POST /me/connections`. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.

After that, a run that names `postman` in `connections`, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.

```http
POST https://api.phoenix.so/me/connections

{
  "type": "mcp",
  "name": "Postman",
  "url": "https://mcp.postman.com/mcp"
}
```

## Whose Postman account the agent uses

Your Postman connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Postman, and a run started with an API key uses the Postman of the member who created the key.

To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link `POST /o/{org}/agents/{agent}/connections` returns. They sign in to their own Postman, and that agent's runs use their account and nothing else: never yours, never another user's.

## More Developer Tools integrations

- [n8n](https://getrush.ai/integrations/n8n/)
- [GitLab](https://getrush.ai/integrations/gitlab/)
- [Jam](https://getrush.ai/integrations/jam/)

## Frequently asked questions

### How do I connect Postman to Rush?

Open Settings → Connections in the console and connect Postman, or send `POST /me/connections` with `{"type":"mcp","name":"Postman","url":"https://mcp.postman.com/mcp"}` and open the `authorize_url` it returns while signed in to the console. The connection reads `pending` until the sign-in finishes, then `connected`.

### Does every run get my Postman account?

No. A run gets your Postman connection only when it names it in `connections` (`"connections": ["postman"]`), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.

### What can an agent do in Postman?

Work with APIs in Postman: manage workspaces, collections, requests and environments, and run collections to test APIs. 1 published job uses it; this page lists it.

### Can my app's users connect their own Postman?

Yes. Make each user an agent from your template, and they sign in to their own Postman through the link `POST /o/{org}/agents/{agent}/connections` returns. That agent's runs use their account alone.

## Keep reading

- [AI agents for engineering teams: every job and app for them](https://getrush.ai/solutions/engineering/)
- [How connections work: sign in once, then every run that names a connection gets it](https://getrush.ai/docs/concepts/connections/)
- [Start your first run from the developer API quickstart](https://getrush.ai/docs/quickstart/)
- [Pricing: one price per member, hours shared by the team](https://getrush.ai/pricing/)
- [How Rush compares with other cloud agents](https://getrush.ai/compare/)
- [Every app and MCP server Rush connects to](https://getrush.ai/integrations/)
