# Postman MCP for AI Agents AI Agent Connect > Postman connects your API lifecycle to your AI agent. It lets your agent browse collections, explore environments, check mock servers, and monitor health statuses without you having to copy-paste JSON schemas or cURL commands. It's about making your API documentation and testing workflows conversational. ## Overview - **Category:** loved-by-devs - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_0K4qtkIFA5sn8n9HRmta4uR6Lfy8jZ7oHngivRhy/ai-agent-connect - **Tags:** api-testing, api-documentation, request-management, collaboration, software-development ## Description Postman connects your developer keys to an AI agent so you can bring collaborative API design and monitoring into a pure conversational context. Instead of switching tabs to find a specific endpoint or manually copying headers into a prompt, you can just ask your agent to find the right data. It reads your collections to understand how your internal APIs actually behave, looks at your environments to distinguish between staging and production, and checks your mock servers to see what your front-end team is working against. If you're trying to figure out why a scheduled monitor failed, the agent can pull that history for you instantly. This setup is part of the Vinkius catalog, making it easy to plug into your existing workflow. You stop treating your API docs as a static file and start treating them as a live, queryable database for your AI. It removes the friction of context switching where you spend half your time just trying to get the AI to understand the shape of the data you're sending. You can get exact HTTP payloads and mock server URLs when building your UI bindings, or quickly verify if staging environment URLs differ from production without navigating the app. It turns your API infrastructure into a searchable knowledge base for your agent. ## Tools ### get_workspace_details Get details and items for a specific workspace ### list_apis APIs represent a higher-level grouping that can include multiple versions and schemas. List all API definitions ### list_environments Shows your development environments and their specific variables. This lets the AI know the difference between staging and production. ### list_workspaces Lists every engineering workspace available to your team. You can use this to see the full scope of your team's projects. ### get_collection_details Get details and requests for a specific collection ### list_mocks Lists the mock servers you've set up for front-end testing. It helps your agent find the right URLs for your UI bindings. ### get_environment_details Get variables and details for an environment ### list_collections Shows all API Collections in your Postman account. This helps the AI understand what APIs are available. ### list_monitors Shows your API health monitors and their recent success or failure history. You can use this to check for errors in your scheduled cron checks. ## Prompt Examples **Prompt:** ``` Are there any Mock servers currently simulating our Auth API? ``` **Response:** ``` I checked your Postman configurations and found 1 active mock server tied to 'User Onboarding Flows'. It exposes exactly 4 static JSON responses for `/login` and `/token` and operates at URL `https://c123.mock.pstmn.io`. Shall I pull its schema details? ``` **Prompt:** ``` Download our core API Collection. Tell me exactly what parameters I need to submit to the Create User endpoint. ``` **Response:** ``` I extracted Collection `col-x71...`, the 'Create User' endpoint (POST `/api/v2/users`) expects a JSON body containing `email` (string, required), `role` (string, defaults to 'viewer'), and `department_id` (number, required). Would you like me to write a Javascript snippet invoking it? ``` **Prompt:** ``` Did any of our scheduled Postman monitors fail over the weekend? ``` **Response:** ``` Looking at the monitor data, your 'Checkout Flow Monitor' failed consecutively on Saturday morning. The internal log indicates an assertion error mapping a `502 Bad Gateway` status on step 3 (`POST /cart`). All other monitors are currently healthy and passing. ``` ## Capabilities ### Browse API Collections Your agent can see all available API collections in your account to understand your full API surface. ### List Engineering Workspaces See every workspace your team uses to keep your agent aware of different project scopes. ### View Environment Variables The agent can see your variables for staging and production to avoid using the wrong URLs. ### Identify Active Mocks Quickly find active mock servers when you need to test front-end components against simulated data. ### Check Monitor Status Get immediate updates on your scheduled health checks and see which monitors are failing. ### Download Collection Schemas Your agent can pull complete JSON schemas to learn exactly how to hit your internal endpoints. ## Use Cases ### Finding mock URLs for UI bindings A frontend dev is stuck on a login page. They ask the agent to find the mock server for the auth flow. The agent uses list_mocks to find the URL and the JSON schema. ### Verifying staging environment URLs A backend engineer needs to know if the staging URL changed. They ask the agent to check the environments. The agent uses list_environments to provide the latest URLs. ### Debugging failed scheduled monitors A QA tester sees a red light on a dashboard. They ask the agent to check the health monitors. The agent uses list_monitors to report the specific failure history. ### Learning internal API schemas A new hire needs to know how to call the Create User endpoint. They ask the agent to pull the collection. The agent uses get_collection to explain the required headers and body. ## Benefits - Stop copy-pasting JSON: Use get_collection to give your agent the full schema of any API instantly without manual exports. - Environment awareness: Use list_environments so your agent knows exactly which variables belong to staging versus production. - Faster front-end dev: Use list_mocks to quickly find the correct mock URLs when building out UI components and bindings. - Proactive monitoring: Use list_monitors to have your agent alert you to failed cron checks without you having to check a dashboard. - Workspace visibility: Use list_workspaces to let your agent see the full scope of your team's engineering projects and collections. ## How It Works The bottom line is that your AI finally has the same map of your API infrastructure that your dev team uses every day. 1. Subscribe to this Connector and enter your Postman Developer API Key. 2. Connect the Connector to your AI client like Claude, Cursor, or Windsurf. 3. Ask your agent to describe an endpoint, check a mock server, or pull a collection schema. ## Frequently Asked Questions **Can the Postman MCP help me write better API requests?** Yes. It pulls the full schema of your collections so your agent knows exactly which headers, methods, and body parameters are required for your specific endpoints. **How do I use Postman MCP to check my production health?** Your agent can check your scheduled monitors to see the success or failure history of your API health checks without you having to open a separate dashboard. **Can my AI agent see my different environments?** Yes. It can list your environments and their variables, which helps the agent distinguish between your staging, production, and local setups. **How does Postman MCP handle mock servers?** It lets your agent identify active mock servers so you can quickly get the correct URLs and simulated responses for your front-end testing. **Can I use this to learn my internal API schemas?** Yes. By pulling your collections, the agent learns the internal structure of your APIs, making it much more accurate when generating code or documentation. **Does Postman MCP work with Cursor?** Yes, it works with any MCP-compatible client, including Cursor, Claude, and Windsurf, to bring your API data into your workspace. **Will my AI agent know the difference between staging and prod?** Yes. Because the agent can read your environment variables, it understands the specific configurations for different stages of your deployment. **Can the AI automatically write code using my internal API documentation?** Absolutely. If you use `get_collection` the AI unpacks the entire Postman hierarchy. Combine this by asking the AI to 'write a Python script to hit my Users Endpoint' and it will natively respect your headers, payload requirements, and auth settings without any context copy-pasting. **How does the agent handle environments like production vs staging variables?** The agent can call `list_environments` exposing active configurations inside your workspace. If a collection points to `{{base_url}}`, the AI reads your environments array to resolve exactly what URLs or access keys map to staging versus production natively. **Can I query test success rates via AI instead of dashboards?** Yes. The `list_monitors` connection unrolls the cron checks tied to your Postman collections. The AI inherently sees whether the latest automated integration tests succeeded or failed, making status reports conversational. **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.