# Add Postman’s MCP Server to Cursor in Minutes

Source: https://www.youtube.com/watch?v=cKUXopUlGPg
Recap page: https://rapidrecap.app/video/cKUXopUlGPg
Generated: 2026-02-09T19:05:06.34+00:00

---
## Quick Overview

The video guides users through quickly setting up Postman's Minimal MCP (Managed Code Provider) Server within the Cursor IDE by obtaining a Postman API key, configuring the server settings in Cursor with the minimal URL, and then demonstrating its functionality by querying Postman collections and updating an OpenAPI spec via natural language prompts to the Cursor Agent.

**Key Points:**
- The setup involves navigating to Cursor Settings -> Tools & MCP to install the Postman MCP Server using the streamable HTTP type and the URL `https://mcp.postman.com/minimal`.
- Users must retrieve a Postman API key from their Postman account settings under 'API keys' and paste it into the Authorization header as `Bearer YOUR_API_KEY`.
- The Minimal configuration is recommended by the presenter for faster performance when only basic Postman operations are needed.
- After installation, the `postman_mcp_server` enables 40 tools, allowing the Cursor Agent to interact with Postman data, such as fetching collections from a specified workspace ID.
- The demonstration confirms the integration works by prompting the Agent to update the 'Fleet Logistics Backend' collection after adding new 'incidents' endpoints to the `openapi.yaml` file.
- The Agent successfully fetches the collections, identifies the existing 'Fleet Logistics Backend' collection, and updates it with the new incident endpoints, proving bidirectional communication.

![Screenshot at 00:00: Demonstration of the Cursor Settings panel where the user inputs the necessary configuration details to install the Postman MCP Server, including the name, type \(streamableHttp\), and the minimal URL.](https://ss.rapidrecap.app/screens/cKUXopUlGPg/00-00-00.jpg)

**Context:** Sterling Chin, Sr. Developer Advocate at Postman, provides a tutorial demonstrating how to integrate Postman's Managed Code Provider (MCP) server capabilities directly into the Cursor AI-powered code editor. This integration allows Cursor Agents to interact with Postman workspaces, collections, and environments using natural language, bridging the gap between development context (code in Cursor) and API management context (Postman).

## Detailed Analysis

The tutorial outlines the process of integrating Postman's MCP Server into Cursor to enable AI agents to manage Postman resources. First, users need a Postman API key, obtained via Postman settings under 'API keys'. The installation occurs in Cursor settings under 'Tools & MCP'. The required setup involves naming the server (e.g., 'postman_mcp_server'), setting the type to 'streamableHttp', and using the minimal URL `https://mcp.postman.com/minimal` (or 'full' or 'code' variants depending on required capabilities). The crucial step is supplying the API key in the Authorization header using the 'Bearer YOUR_API_KEY' format. Once installed, the server activates 40 tools. The presenter verifies functionality by asking the Agent to list collections in the 'Fleet Logistics' workspace, providing the specific workspace ID. The Agent successfully executes `getCollections`, finds the 'Fleet Logistics Backend' collection, and subsequently updates it after the presenter modifies the `openapi.yaml` file to include new 'incidents' endpoints, demonstrating the seamless interaction between the code editor's AI and Postman's API tools.

### Postman MCP Server Installation in Cursor

- Access Cursor Settings -> Tools & MCP
- Input server name 'postman_mcp_server'
- Set Type to 'streamableHttp'
- Use URL 'https://mcp.postman.com/minimal'
- Add API Key to Authorization header as 'Bearer YOUR_API_KEY'
- Click Install

### API Key Retrieval

- Navigate to Postman Home -> Profile -> Settings -> API Keys
- Generate a new API Key (e.g., 'postman-cursor-mcp-server')
- Copy the generated key

### Server Configuration Options

- Minimal (default) for basic operations
- Full for all 100+ API tools
- Code for generating client code from API definitions
- URLs are adjusted based on the desired mode (e.g., '/minimal', '/full', '/code')

### Functionality Demonstration

- Agent is prompted to list collections in 'Fleet Logistics' workspace using the provided Workspace ID
- Agent executes `getCollections:postman_mcp_server` tool
- Agent confirms finding one collection: 'Fleet Logistics Backend'

### Updating Collections via Spec Changes

- Presenter modifies `openapi.yaml` to add 'incidents' endpoints
- Agent is prompted to update collections based on the spec change
- Agent fetches the collection, reviews its structure, adds the new incident endpoints, and confirms the update is complete.

![Screenshot at 00:00: Configuration screen in Cursor showing the fields for installing a new Postman MCP Server, including the URL field being populated.](https://ss.rapidrecap.app/screens/cKUXopUlGPg/00-00-00.jpg)
![Screenshot at 00:09: Close-up on the Authorization header configuration, highlighting the required 'Bearer YOUR\_API\_KEY' format.](https://ss.rapidrecap.app/screens/cKUXopUlGPg/00-00-09.jpg)
![Screenshot at 00:22: The Postman MCP Server GitHub repository page, indicating the source of the required tools.](https://ss.rapidrecap.app/screens/cKUXopUlGPg/00-00-22.jpg)
![Screenshot at 01:52: The Postman UI showing the process to generate a new API key, prompting the user to name the key.](https://ss.rapidrecap.app/screens/cKUXopUlGPg/00-01-52.jpg)
![Screenshot at 02:21: The Cursor IDE displaying the active Postman MCP Server tools list, showing 'postman\_mcp\_server' with 40 tools enabled.](https://ss.rapidrecap.app/screens/cKUXopUlGPg/00-02-21.jpg)