M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
P

Postman MCP Server

Official
Connect AI agents directly to the Postman API.
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #192 of 438
Stars
★ 324 Very popular
Transport
stdio (local process) · Streamable HTTP
Runtime
Node.js · Docker · Hosted (no local runtime)
Credentials
API key / credential required
License
Apache-2.0
Last commit
55FMRS · C

An official Postman MCP Server offering stdio and streamable HTTP connections, with Minimal, Code, Full, and Learn configurations.

Strongest · Setup experience 13/20 Weakest · Reliability 9/20

Reliability
9/20
Security and permissions
9/20
Maintenance
11/20
Documentation
13/20
Setup experience
13/20
Why each score
Reliability 9/20
The manifest provides a version, stdio and HTTP transports, required credential declarations, and hashes for MCPB artifacts; the README also distinguishes tool configurations, making the basic startup path plausible. However, the supplied material contains no source code, CI, commit history, tests, or evidence about actual tool behavior and error handling. Initialization, tool-list negotiation, and edge cases therefore cannot be verified, warranting substantial deductions.
Security and permissions 9/20
Credentials are marked required and secret, remote service OAuth is documented, and EU endpoints and API-key authentication are distinguished. Nothing supplied indicates malware or credential theft. However, the Full configuration exposes more than 100 API tools and the documented capabilities include creating, updating, and managing resources. Evidence of least privilege, confirmation for dangerous actions, data boundaries, auditing, and network data flows is absent, so security controls are incomplete.
Maintenance 11/20
The repository is not archived, has an Apache-2.0 license, and identifies a concrete 2.11.2 release, npm package, and GitHub source. This establishes basic release and licensing information only. No commit history, release cadence, dependency-update policy, maintainer ownership, or security-response channel is supplied, so sustained maintenance cannot receive a high score.
Documentation 13/20
The README covers remote and local installation, authentication, tool configurations, regional support, supported clients, Docker entry points, and the limitation that the remote server cannot access the local workstation network. It is reasonably layered, but tool parameters, permission scope, costs, troubleshooting, compatibility details, and reviewable test evidence are missing; important client instructions are only linked externally.
Setup experience 13/20
The material provides remote URLs, a local npx command, mode switches, the environment variable, and documentation entry points for many mainstream clients, so the main connection paths are clear. Deductions apply because runtime prerequisites, the full client configuration steps, concrete OAuth/API-key setup details, and troubleshooting are not included in the supplied material; some paths remain manual.

Static review · not runListed 2026-07-30

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

Best for

  • Development teams managing API assets in Postman
  • Users who need collection, specification, and environment context in coding assistants
  • Developers who need generated API client code

Not for

  • Users who need a remote server to access APIs on their local workstation
  • Users who do not use Postman workspaces, collections, specifications, or environments
  • Deployments unable to provide OAuth authorization or a valid Postman API key

Required permissions

  • The remote OAuth flow requires OAuth authorization
  • The EU remote server and local server require a valid Postman API key
  • The local process receives the API key through the POSTMAN_API_KEY environment variable

Risks and side effects

  • The server can perform management operations on collections, workspaces, and environments, which may modify Postman resources
  • API keys and Authorization Bearer credentials are sensitive authentication data and should not be exposed
  • The remote server cannot access APIs on the user's workstation

Setup

Before you start

Runtime：Node.js · Docker · Hosted (no local runtime)

POSTMAN_API_KEY requiredsecret A Postman API key, required to run the local server; get one at postman.postman.co/settings/me/api-keys.
Other optional settings (1)
POSTMAN_API_BASE_URL optional Optional; points the local server at the EU region API endpoint, alternatively use the --region eu flag.

Remote: add https://mcp.postman.com/minimal to an OAuth-compatible MCP host; change the path to /code or /mcp for other modes. EU endpoints and the local server use a Postman API key. Local: run npx @postman/postman-mcp-server and set POSTMAN_API_KEY; use --code or --full for those configurations.

Check that it works

After adding the server to your MCP client, check that Postman tools appear in the client's tool list; or ask it to 'list my Postman collections' — a real collection listing confirms the connection works.

Troubleshooting

  1. Verify that OAuth or Authorization Bearer credentials are valid
  2. Verify that POSTMAN_API_KEY is set for the local server
  3. Verify that the remote endpoint matches the required mode: Minimal, Code, or Full
  4. Use the local server for local API testing because the remote server cannot access the workstation network
  5. Do not use OAuth with EU endpoints; the EU server supports API-key authentication only

Things to try

Once connected, you can ask your AI assistant things like:

  • List all collections in my Postman workspace
  • Create a new collection from my OpenAPI spec and update its documentation
  • Generate client code from this API definition
  • Create a new environment in my workspace and add variables to it

Use cases

Continuously test APIs with Postman collections
Synchronize code with Postman collections and specifications
Manage collections, workspaces, and environments
Create specifications from code and generate collections
Generate client code

Supported clients

Claude Code
Claude Desktop
Cursor
VS Code
Codex
Antigravity CLI
GitHub Copilot CLI
Kiro
Gemini CLIPartial support

Listed from the project's documentation, not tested by this site.

Overview

Postman MCP Server implements the Model Context Protocol (MCP) to connect AI agents and coding assistants to Postman workspaces, collections, API specifications, and environments for API testing, resource management, specification creation, and client code generation.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision a56d18bd98b8 Data synced 2026-10-19 Read the FMRS scoring method