Postman

Agents can work with your Postman workspaces, collections, and environments — reading API definitions, and on the fuller capability groups generating code and making changes.

Two decisions come before credentials, and getting either wrong means starting over.

Decide region and capability group first

Region determines both the endpoint and how you authenticate:

Capability group determines how many tools the connection exposes:

Warning: Minimal is a smaller catalog, not a read-only one. Postman's own documentation describes it that way, and its published minimal list includes createCollection, createWorkspace, putCollection, updateWorkspace, publishMock, duplicateCollection and runCollection. Choosing Minimal does not stop an agent creating, changing, publishing or running things. If you want a read-only posture, that comes from Paperclip's action settings, not from the group.

Start with Minimal anyway — a smaller catalog is easier for both you and the agent to reason about — but set the write actions it does contain to Ask first or Off when you finish setup.

The region and group are fixed on the connection. To change either, make a new connection.

Before you connect

• A Postman account with access to the workspaces you want agents to use.
• For the EU region, a Postman API key.

Connect Postman

1. Open Connectors and select Postman.
2. Read the access line above the main button. It says who the connection signs in as and which agents can use it. To pick a different identity, narrow the agents, or use another sign-in method, select Change.
3. Check that the selected option matches your region and capability group. To pick another, select Change.
4. For US, complete Postman's browser sign-in. For EU, paste your Postman API key.

Choose access

Workspace, collection, and environment reach comes from Postman: the connection sees what the authenticating account or key can see. Paperclip has no workspace picker, so narrow access by authenticating with an account that has access to fewer workspaces.

Warning: Postman environments commonly hold API keys, tokens, and passwords as variables. An agent that can read an environment can read those values. The controls that actually help here are authenticating with a limited account and keeping secrets out of shared Postman environments — alongside the discovered tool list and Paperclip's action permissions.

Toolsets differ by purpose; do not assume they form progressively broader permission tiers. Inspect the discovered actions for your selected endpoint. Review generated code before using it, and set permissions for each available action separately.

One tool deserves separate attention: runCollection is present in the Minimal list, and running a collection means issuing its requests against whatever the collection targets. Decide explicitly whether an agent should be able to do that, and set it to Off if not.

Set write and destructive actions to Ask first or Off on the Permissions tab. On this connector that is the read-only control. See Set action permissions.

Try it

List the Postman collections you can see and tell me how many requests are in the first one. Do not change anything.

Compare the collection list against what you see in Postman. This confirms the credential, the region endpoint, and the agent's permission at once.

Note: Illustrative task, not a recorded test result.

Troubleshooting and limitations

Limitations: one region and one capability group per connection. No workspace selection in Paperclip. Do not infer read-only access from a capability group's name. Postman's own plan limits apply.

Related guides

• Connector overview

• How connector access works

• Set action permissions

• Verify a connector and fix a broken one

• Postman MCP server documentation