Integration · Automate and collaborate

Postman and Meteor AI agents

Connect Postman to a Met: read your API's collections, environments and mock servers and answer the developers integrating it on WhatsApp.

Book a demo See every integration

How does Postman connect to Meteor?

With the Postman ready connector, your Met uses Postman's official MCP server, in its Minimal configuration, with the account the admin authorizes. It gets a workspace, a collection, an environment or a mock server by its identifier, so it answers whoever integrates your API with what your team documented in Postman, not from memory, and shares the mock URL so they can test without touching production. If the admin leaves writing on, it also creates collections, environments, mock servers and workspaces, and changes a mock or a workspace. Usage runs on your Postman plan; Meteor does not resell the service.

What it automates

What a Meteor Met does with Postman

Answer whoever integrates your API

When a client's developer asks on WhatsApp what an endpoint is called, the Met opens the collection your team keeps in Postman and replies with the method, the path and the description documented there.

Share the mock so they can test

The Met gets the collection's mock server and shares its URL with the developer, so they can test their calls against example responses before touching your real API.

Explain the test environment

The Met gets the test environment and explains to the developer which variables your API expects, such as the base URL, without sharing secret values if your team says so in the skill.

Set up a new client's workspace

If the admin leaves writing on, the Met creates a workspace, a collection and an environment for a new agency client, and gets a mock server ready.

10 tools

Everything your Met can ask Postman for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`getworkspace`	Gets a workspace's details, including its visibility: personal, team, private, public or partner.
`createworkspace`	Creates a new workspace. Private and partner workspaces are on Postman's Team and Enterprise plans.
`updateworkspace`	Changes a workspace property, such as its name or its visibility.
`getcollection`	Gets a collection: by default, its lightweight map with metadata and items; on request, the full collection.
`createcollection`	Creates a collection in the Postman Collection v2.1.0 format. Without a workspace, it lands in the account's oldest personal internal workspace.
`getenvironment`	Gets the details of a Postman environment.
`createenvironment`	Creates an environment, with a body of up to 30 MB. Without a workspace, it lands in the account's oldest personal internal workspace.
`getmock`	Gets a mock server's details, with the UID of the collection it comes from and its URL (mockUrl).
`createmock`	Creates a mock server in a collection, from that collection's UID.
`updatemock`	Updates a mock server: its name, its environment, its privacy or the response it returns by default.

The limits

What the Postman integration does NOT do

We would rather say it here than have you find out during rollout.

It does not read Postman monitors or APIs, and it does not delete anything: the Minimal configuration Met uses does not include those tools.
It does not list your collections or environments with the tools on this page: the listing tools do not have the same name in the directory and in the official code, and this page leaves them out. The Met works with the workspace, collection, environment and mock identifiers your team gives it in the skill.
It does not decide by itself which variables are secret. If an environment stores keys or tokens, tell it in the skill not to share values, or use an environment without secrets.
It does not ask you for confirmation in the chat before writing. The admin decides in Connections which actions stay on.
It does not use the EU region server. Met connects through OAuth to the global server, and Postman states its EU server only accepts an API key.

Before you start

What you need to connect Postman

1

A Postman account with access to your collections

Your team's Postman account, with access to the workspace that holds your API's collection, environment and mock. The Met works with that account's permissions.
2

Connect it in Met

In Met, open Connections → Postman → Connect. A Postman window opens so you sign in and authorize Met. Then you choose which actions stay on.

Frequently asked questions

Questions about Postman and Meteor

Not to ask questions. They talk to the Met on WhatsApp, and the Met reads Postman with the account your team connected. Opening the workspace themselves does depend on its visibility.

Because the server's Minimal configuration does not include them, and because this page only lists the tools whose name matches in the connector directory and in the official code.

It can change a mock's privacy or a workspace's visibility if the admin leaves those actions on. If you do not want that, turn them off in Connections.

You do, with your Postman account and plan. Meteor does not resell Postman or charge for the actions your Met takes there.

Step by step