Postman MCP. Manage every API resource via conversation.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Postman MCP Server connects your AI agent directly to your API development environment. It exposes Postman's entire resource graph—workspaces, collections, environments, and monitors—as actionable tools.
You can list APIs, pull variable values, or check service status by simply asking your AI client, eliminating the need to click through dozens of complex UI tabs.
What your AI agents can do
Get collection details
Retrieves the detailed requests and metadata for a specific API collection ID.
Get environment details
Fetches all variables, their current values, and configuration details for a selected environment.
Get workspace details
Retrieves the complete list of items and metadata belonging to a specific workspace.
Retrieves a list of every accessible workspace in your Postman organization.
Lists all high-level APIs, including versions and schemas, that exist within the account.
Gets detailed information and requests for a specific API collection.
Shows all available variable sets, allowing you to scope data for development or production stages.
Lists and verifies the current operational state of scheduled API monitors.
Retrieves a list of configured mock servers, useful for testing before implementation.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Postman MCP Server: 9 Tools for API Management
Use these nine tools to programmatically list and retrieve every resource in your Postman organization—from environments to live monitor statuses.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Postman on Vinkius019dd13fget collection details
Retrieves the detailed requests and metadata for a specific API collection ID.
019dd13fget environment details
Fetches all variables, their current values, and configuration details for a selected environment.
019dd13fget workspace details
Retrieves the complete list of items and metadata belonging to a specific workspace.
019dd13flist apis
Lists all API definitions, providing high-level schemas and versions available in your account.
019dd13flist collections
Retrieves a list of every stored API collection by name or ID.
019dd13flist environments
Lists all available environment variable sets, like 'Development' or 'Production'.
019dd13flist mocks
Shows a list of configured mock servers, useful for simulating responses before the backend is ready.
019dd13flist monitors
Retrieves the status and schedule details for all set API performance monitors.
019dd13flist workspaces
Lists every accessible workspace, which is Postman's primary organizational container.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Postman, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Postman. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 9 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Finding documentation data shouldn't take 8 clicks across three different tabs.
Today, finding basic API context is a nightmare. You open Postman, then you have to navigate to Workspaces; then you find the Collection ID; then you switch tabs to check Environment variables for the right scope; and finally, you might need another click just to see the schema definition. It's copy-paste hell.
With this MCP server, your AI client handles all that navigation. You ask it: 'What are the key endpoints in the Core Payments API?' The agent runs `get_collection_details` and returns the full endpoint list, headers, and schemas—all without you ever leaving the chat window.
Postman MCP Server: Get API details right from your IDE.
Previously, checking service status meant opening a dedicated 'Monitoring' tab. If that monitor failed or needed adjustment, you had to leave the main development flow and switch contexts entirely. It broke focus.
Now, just ask: 'What is the current health of our primary API?' The agent runs `list_monitors` and gives you a real-time status report, letting you stay focused on coding while keeping an eye on production readiness.
What you can do with this MCP connector
Postman MCP Server: API Management, Done Right
You'll connect your AI agent straight into your full API development playground. This server exposes every single piece of Postman—your workspaces, collections, environments, and monitors—as tools your agent can run. You don't gotta click through a dozen tabs or mess with complex UIs; you just tell your AI client what you need, and it handles the calls.
What Your Agent Can Do
Your AI agent acts like an API architect sitting right next to you. It gives you direct access to the entire resource graph of your Postman organization. You can list all accessible workspaces using list_workspaces, which shows every container where you keep your team's and personal projects.
For APIs themselves, you can run list_apis to get a full rundown of all high-level API definitions in your account, including their schemas and versions. You also use list_collections to retrieve a list of every stored API collection by name or ID. Once you've got the specific collection ID, running get_collection_details pulls back all the detailed requests and metadata associated with it.
When it comes to variables and settings, your agent uses list_environments to show all available variable sets—think 'Development,' 'Testing,' or 'Production.' If you know the specific environment, get_environment_details fetches every variable, their current values, and the whole configuration breakdown for that set.
To make sure you're always working with fresh data, you can use list_mocks to view all your configured mock servers. This is key for testing responses before the actual backend service is even ready to go live.
Your agent also handles infrastructure status checks. It runs list_monitors to retrieve the operational status and schedule details for every API performance monitor you've set up, while list_environments allows you to scope data by checking which variable sets are available across your whole account. You can pull all the necessary pieces of information—the definitions, the variables, the status checks—without ever leaving your conversation flow.
019dd13f-9b49-7000-9404-eed7b0acead8 
How Postman MCP Works
- 1 Subscribe to the Postman MCP Server and enter your API Key in the Vinkius Marketplace.
- 2 Tell your AI client what resource you need (e.g., 'Show me all staging environments').
- 3 The agent executes the necessary tool (
list_environments) and returns structured data, which it then presents conversationally.
The bottom line is: you talk to your API tools instead of navigating their UIs.
Who Is Postman MCP For?
This server targets the software engineers and QA teams who spend too much time clicking through complex, nested dashboards. If you're tired of manually copying IDs or switching between 15 tabs just to check a variable value, this is for you. It gives your agent immediate access to the core API lifecycle data.
Uses it to instantly pull request headers, inspect environment variables, or retrieve schemas without leaving their IDE.
Checks monitor statuses and verifies collection requests straight from the chat window to confirm service availability before a release.
Automates cross-functional documentation queries, listing workspaces and APIs to map out organizational dependencies quickly.
What Changes When You Connect
- Instant Variable Lookup: Need to know the
user_idfor staging? Useget_environment_details. Your agent pulls the exact value from any environment set—no more clicking through 5 variable tabs. - System Health Check: Instead of checking a dashboard, ask your agent to run
list_monitors. It reports the status (passed/failed) for all scheduled checks immediately. - Clear Inventory Mapping: Want to know what APIs exist? Use
list_apisandlist_collectionstogether. You get an immediate, conversational map of every major resource in your account. - Scope Management: Need to focus on one area? Run
list_workspaces. This tells you exactly which project containers are available, keeping your conversation scoped correctly. - API Documentation Access: Don't hunt for schemas. Use the agent to list APIs and collections (
list_apis,list_collections). It hands you the definitions right in the chat. - Pre-Build Testing: Need a placeholder endpoint? Check
list_mocks. You can confirm mock server existence, letting developers test against fake data before writing any code.
Real-World Use Cases
Validating Staging Readiness
A QA tester needs to verify the 'Staging API' is healthy. Instead of navigating to the Monitoring tab and clicking through filters, they ask their agent: 'Check the status of all monitors.' The tool runs list_monitors and reports if latency warnings exist for the staging environment.
Debugging a Missing Variable
A developer is running code that fails because a required API key isn't found. They tell their agent to run get_environment_details on the 'Production' workspace. The agent pulls all variables and confirms if the specific key exists, solving the bug without leaving the terminal.
Mapping Out Dependencies
A Technical Lead is onboarding a new team member and needs an overview of all services. They ask the agent to run list_workspaces and then loop through list_apis. The agent structures this raw data into a readable, cross-functional service map.
Testing Against Dummy Data
A front-end developer needs to build a UI before the backend team finishes their API. They ask the agent to list available mock servers (list_mocks). The agent confirms the mock endpoint, allowing the dev to proceed with dummy data testing.
The Tradeoffs
Manual ID Hunting
You spend 15 minutes in Postman trying to find the exact Workspace ID or Collection ID because you can't remember it, then copy/paste it into your script.
→
Just tell your agent: 'List all workspaces.' The tool runs list_workspaces and provides the IDs for you. Then, give that ID back to the agent.
Assuming Scope
You assume a certain environment variable set is active when running a test, but the code fails because it's defaulting to 'sandbox' instead of 'development'.
→
Always use list_environments first. This lets you confirm which variables are available and what their current values are before your agent runs any requests.
Ignoring API Definitions
You only test one endpoint, but the requirements change, and you have to manually find the schema for a related resource type.
→
Run list_apis immediately. It provides all available definitions and schemas right away, giving you the full context of what your service can do.
When It Fits, When It Doesn't
Use this server if your core workflow involves querying, inventorying, or checking the operational status of defined API assets (collections, environments, monitors). You need programmatic access to things like variable values and resource lists.
Don't use this if you simply want a visual browsing experience—if you just want to click around in Postman until you find what you need, stick with the native GUI. However, if your workflow is 'I have data; I need to act on it,' then connecting your AI client via these tools is the right path. For deep dependency mapping (e.g., API X depends on Collection Y), this tool provides the raw components (list_apis and get_collection_details), but you'll still need an intermediary script to draw the full graph.
Common Questions About Postman MCP
How do I list all my Postman workspaces using get_workspace_details? +
You first run list_workspaces to see all available containers. Then, if you want details on a specific one, you pass the ID to get_workspace_details. This is how your agent scopes its actions.
Can I use list_environments to check my API keys? +
Yes. The tool runs list_environments and provides a view of all variable sets (like 'Dev' or 'Prod'). You can then ask the agent to run get_environment_details on the specific environment you need.
What is the difference between list_collections and get_collection_details? +
Use list_collections when you just want an inventory of all available API collections. Use get_collection_details when you already know the ID and need to see the specific requests (POST/GET) inside that collection.
Does list_monitors tell me if my service is down? +
It tells you if Postman's monitor is running successfully. It reports the status of scheduled checks, alerting you to potential performance issues or failures in your API endpoints.
When I use get_collection_details, how do I view all headers and body parameters for a request? +
It returns the full payload structure for that endpoint. You'll get access to both HTTP headers and the body content used in that specific request, letting you check exact formats like JSON or form data.
What does list_mocks provide regarding my API's readiness for testing? +
It lists every configured mock server. This confirms that the endpoints are set up to simulate responses, which is useful for development and testing before the actual backend service is finished.
If I need a list of all available top-level API definitions, should I use list_apis? +
Yes, that's the right tool. It gathers every major API definition in your account. This view gives you the broadest scope by grouping multiple related collections and versions under one name.
Can I check variable security or usage limitations using get_environment_details? +
Yes, the details include variable scopes and types. You can verify if a specific environment variable is marked as sensitive, restricted, or only available to certain deployment stages.
Can my AI automatically find the details of a specific collection just by providing its ID? +
Yes! Use the get_collection_details tool with the unique ID. Your agent will respond with complete structure, requests, and metadata in seconds.
How do I check my API monitors status? +
Simply ask the agent to run the list_monitors tool. It will compile all scheduled monitors and their latest results configured for your environment.
Does the integration permit modifying collections? +
No. The core set of tools focuses strictly on querying and analyzing API context—listing workspaces, collections, and environments. State alteration operations are not currently exposed.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.