Spark
Sign In
MCP Connector

Integrate Postman with AI for API Management

MCP server giving AI agents access to Postman workspaces, collections, environments, and API tooling via natural language.

Connect
Works with postmangemini
Postman Inc.
Maintainer?
91
Spark score
out of 100
Updated last month
Version 2.9.1
Models
universal
Add to Favorites

Why it matters

Empower AI agents and assistants to interact with Postman workspaces, manage API collections and environments, and automate workflows through natural language.

Outcomes

What it gets done

01

Connect AI tools to Postman for API evaluation and management.

02

Automate API testing and code synchronization with Postman collections.

03

Generate client code and API specifications from your codebase.

04

Manage Postman workspaces, environments, and collections via natural language.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-postman-api | bash

Overview

Postman API MCP Server

An MCP server giving AI agents access to Postman collections, workspaces, environments, and API tooling, with Minimal/Code/Full tool configurations for remote or local use. Use when you want an AI assistant to test APIs, manage Postman collections/environments, or generate client code directly from your editor.

What it does

The Postman MCP Server connects Postman to AI tools, giving AI agents and assistants the ability to access workspaces, manage collections and environments, evaluate APIs, and automate workflows through natural language interactions. It's also distributed as an npm package. A companion Postman MCP Server collection lets you browse the full list of available tools across configurations and test both the remote and local servers directly from Postman.

When to use - and when NOT to

Use this connector when you want an AI assistant to work with Postman collections, workspaces, environments, or API specs directly - testing APIs, generating client code, or automating collection management. Use the local server rather than the remote one for API testing against local/workstation-only APIs, since the remote server has no network access to your machine.

Capabilities

Three tool configurations trade off scope for footprint: Minimal (the default) includes only essential tools for basic collection/workspace/environment operations; Code adds tools for generating high-quality client code from public and internal API definitions; and Full includes all 100+ available Postman API tools, aimed at advanced collaboration and Postman Enterprise features. Documented use cases include continuous API testing against a Postman collection, keeping code in sync with Postman collections and specs, collection management (creating/tagging collections, updating documentation, adding comments across multiple collections without leaving the editor), workspace and environment management (including environment variables), automatic spec creation from code, and generating production-ready client code that follows project conventions.

How to install

For the remote server, the best developer experience uses OAuth (fully compliant with the MCP Authorization specification, no manual API key needed) by adding https://mcp.postman.com/minimal (or /code//mcp for Code/Full mode) to an OAuth-compatible MCP host's config. The EU remote server and the local server support only Postman API key authentication (Authorization: Bearer <POSTMAN_API_KEY> as a header, or the POSTMAN_API_KEY environment variable locally). Locally, run npx @postman/postman-mcp-server, adding --code or --full for those modes. EU support is available for both remote (https://mcp.eu.postman.com/mcp, /code, /minimal) and local servers (via --region eu or the POSTMAN_API_BASE_URL environment variable); OAuth isn't supported for the EU server. Docker setup is documented separately in DOCKER.md.

Who it's for

Developers and teams already using Postman for API design and testing who want an AI assistant in their editor or CLI to test APIs, manage collections/workspaces/environments, and generate client code - supported across Claude Code, Claude Desktop, Cursor, VS Code, Codex, Windsurf, Antigravity, GitHub Copilot CLI, Gemini CLI, Kiro, and Docker (remote and/or local, per the IDE's own setup docs).

Source README

Postman MCP Server

The Postman MCP Server connects Postman to AI tools, giving AI agents and assistants the ability to access workspaces, manage collections and environments, evaluate APIs, and automate workflows through natural language interactions. Learn more on the Postman MCP Server product page.

Postman also offers the server as an npm package.

Postman MCP Server collection

The Postman MCP Server collection is the quickest way to explore, test, and connect to the Postman MCP Server. Use it to:

  • Browse the complete list of available tools across all configurations.
  • Connect to and test the remote server - Full and Minimal.
  • Connect to and test the local server.

Tool configurations

  • Minimal - (Default) Only includes essential tools for basic Postman operations. Ideal for users who want to modify a single Postman element, such as collections, workspaces, or environments.
  • Code - Includes tools to generate high-quality, well-organized client code from public and internal API definitions. Ideal for users who need to consume APIs or get API context to their agents.
  • Full - Includes all available Postman API tools (100+ tools). Ideal for users who engage in advanced collaboration and Postman's Enterprise features.

Authentication

For the best developer experience and fastest setup, use OAuth on the remote server (https://mcp.postman.com). OAuth is fully compliant with the MCP Authorization specification and requires no manual API key configuration.

The EU remote server and the local server support only Postman API key authentication.

Quick start

Remote (any OAuth-compatible MCP host):

Add this URL to your MCP host's configuration:

https://mcp.postman.com/minimal

Change /minimal to /code or /mcp for Code or Full mode. For EU or API key auth, pass Authorization: Bearer <POSTMAN_API_KEY> as a header.

Local:

npx @postman/postman-mcp-server

Add --code or --full for Code or Full mode. Set POSTMAN_API_KEY as an environment variable.

For IDE-specific setup instructions, see the table below. For more information, see the Postman MCP Server docs.

Supported agents and IDEs

Agent / IDE Remote Local
Claude Code Docs Docs
Claude Desktop - Docs
Cursor Docs Docs
VS Code Docs Docs
Codex Docs Docs
Windsurf Docs Docs
Antigravity Docs Docs
GitHub Copilot CLI Docs Docs
Gemini CLI Docs Docs
Kiro Docs Docs
Docker - Docs

EU support

The Postman MCP Server supports the EU region for remote and local servers:

  • For streamable HTTP, the remote server is available at https://mcp.eu.postman.com/mcp (Full), https://mcp.eu.postman.com/code, and https://mcp.eu.postman.com/minimal.
  • For the STDIO public package, use the --region eu flag, or set the POSTMAN_API_BASE_URL environment variable directly.
  • OAuth isn't supported for the EU server. The EU remote server only supports API key authentication.

Use cases

  • API Testing - Continuously test your API using your Postman collection. Use the local server to test local APIs, as the remote server won't have network access to your workstation.
  • Code synchronization - Keep your code in sync with your Postman Collections and specs.
  • Collection management - Create and tag collections, update documentation, add comments, or perform actions across multiple collections without leaving your editor.
  • Workspace and environment management - Create workspaces and environments, plus manage environment variables.
  • Automatic spec creation - Create specs from your code and use them to generate collections.
  • Client code generation - Generate production-ready client code that consumes APIs following best practices and project conventions.

Docker

For Docker setup and installation, see DOCKER.md.

Questions and support

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.