Postman’s MCP Server Now Works With Google Antigravity IDE
Note:
The Postman CLI, MCP, and agentic plugins have recently been consolidated into the Postman Plugin.
It has been optimized to work with all modern agentic coding tools.
Please refer to the GitHub repository for install and usage instructions.
We are excited to announce that Postman’s MCP server now integrates natively with Google’s Antigravity IDE. If you are already using Postman to manage your APIs, you can now give Antigravity’s AI agents direct access to your Collections, environments, and test workflows with a few lines of config.
What Is Postman’s MCP Server?
The Postman MCP server uses the Model Context Protocol (MCP) to give AI agents structured, executable access to your APIs. Think of it as a translation layer between your Postman workspace and any MCP-compatible AI tool. You define your APIs once in Postman, and the server handles the rest. Once connected, AI agents can browse your Collections, execute requests, run your test scripts, and reference your environment variables to move between dev, staging, and production. Your Collections stop being documentation. They become something an AI can actually use.Setting Up the Integration
To get started, generate a Postman API key at go.postman.co/settings/me/api-keys.
- Open the MCP store via the “Additional options” or “…”dropdown at the top of the editor’s agent panel.
- Click on “MCP Servers”
- Search “Postman”
- Click “Install”
- Enter your Postman API Key
How It Works Under the Hood
When the Postman MCP server starts up, it reads your connected Postman workspace and exposes your Collections as tools the AI agent can invoke directly. Each request in a Collection becomes a callable action. Your environments become switchable contexts. Your test scripts become validation steps the agent can run and report on. Antigravity maintains this context persistently across sessions. The agent doesn’t start from scratch each time you open a new task. It already knows your API surface, and it can draw on that knowledge throughout a full feature build without you having to re-explain anything.What You Can Do With It
Rather than share a long feature list, here are a few real usage scenarios. “My team needs to validate API changes before merging” This is one of the most common pain points for API teams. A backend change ships, something breaks downstream, and no one finds out until the PR is already merged. With the integration active, you can ask Antigravity’s agent to run your Postman test suite against staging before any pull request is opened. It executes the Collection, parses the results, surfaces failures inline, and flags which requests broke. Regressions get caught before they reach code review. “I’m writing code that calls an internal API and I don’t want to guess at the contract” This happens constantly. A developer writes an integration against a service they don’t own, and they’re either digging through static docs or copying examples from memory. With Postman’s MCP server connected, Antigravity’s agent pulls the actual request definition from your Collection. The correct method, headers, auth scheme, and expected response shape are all there. No hallucinated endpoints. No made-up field names. The agent is working from what the API actually does. “We onboarded a new engineer and they need to understand our API surface” Point them to Antigravity and have them ask the agent to walk through your APIs. The agent can execute live requests against a sandbox environment and show real responses in context. It is a faster, more concrete introduction than handing someone a static doc and hoping they read it.
“I have an OpenAPI spec and I need a Postman Collection”
Drop the spec into Antigravity and ask the agent to scaffold a Collection from it. It uses Postman’s MCP tools to generate requests, test assertions, and example responses, then publishes the Collection directly to your workspace. Your team can pick it up immediately.

What do you think about this topic? Tell us in a comment below.