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

Postman MCP Server

Community
An MCP server providing access to the Postman API
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #272 of 438
Stars
★ 158 Popular
Transport
stdio (local process)
Runtime
Node.js
Credentials
API key / credential required
License
MIT
Last commit
⚠
49FMRS · D

A community-built TypeScript MCP server exposing Postman API capabilities—collections, environments, API management, role-based permissions, webhooks, and enterprise features—to AI clients. It supports Claude Desktop, Cline, and Smithery installation, but is early-stage with AI-generated code, best suited to advanced users comfortable with some risk.

Strongest · Documentation 13/20 Weakest · Reliability 7/20

Reliability
7/20
Security and permissions
8/20
Maintenance
9/20
Documentation
13/20
Setup experience
12/20
Why each score
Reliability 7/20
The README explicitly flags the project as under active development with expected breaking changes, and discloses the code was AI-generated via Cline + Claude 3.5 Sonnet. There is no mention of automated tests, CI workflows, or structured error handling anywhere in the text; debugging relies solely on manually running the MCP Inspector. Per the static calibration rule, without verifiable CI/test evidence the score cannot exceed 12; combined with the breaking-changes warning and total absence of test evidence, this is scored 7 (happy path plausible, but error handling and edge cases are essentially undocumented).
Security and permissions 8/20
The API key is supplied via the POSTMAN_API_KEY environment variable, and the README warns against committing keys to version control — a basic good practice. However, the tool feature list includes numerous delete operations (collections, environments, APIs, etc.) with no documented confirmation step or scope restriction before destructive actions. The README also states the API key grants access to 'all Postman resources you have permissions for,' indicating no least-privilege scoping is described, and there is no disclosure of data flow boundaries between the local server, Postman's API, and third parties like Smithery. These are deductions for missing evidence rather than confirmed red-line violations (the example config uses a placeholder CHANGEME, not a real secret), so no red line is triggered; scored 8.
Maintenance 9/20
The project uses the MIT license, is at v0.2.0, is not archived, and has 157 stars against 10 open issues — a reasonable ratio suggesting some active attention. However, the README does not describe a release cadence, changelog, dependency-update policy, or a security-response channel (no SECURITY.md mentioned), and the project self-describes as early-stage active development with immature governance/versioning. Scored 9.
Documentation 13/20
The README is well-structured with a table of contents, feature breakdown, install steps, Claude Desktop/Cline configuration examples, and a debugging guide, and it references further docs/ content (API references, summaries, handler documentation), giving reasonable layered documentation. However, the README itself does not enumerate individual MCP tool parameters/schemas (deferring to external docs), gives no concrete rate-limit or cost figures (only a link to Postman's own docs), and the author openly admits Zed client support is 'still trying to get this to work.' Scored 13.
Setup experience 12/20
Installation steps are clear (clone, pnpm install, pnpm run build, pnpm run watch), and a Smithery one-command install plus JSON config examples for Claude Desktop/Cline are provided, giving reasonable cross-client guidance. However, configuration requires manually editing an absolute path (/path/to/postman-api-server/build/index.js) and restarting the client to refresh cached tool definitions, which is a manual and error-prone step. Since this is a static review with no CI/test evidence verifying the install actually works end-to-end, the score is capped at 15 per the calibration rule; scored 12.

Static review · not runListed 2026-09-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

Best for

  • Teams running complex, multi-step Postman operations through AI assistants
  • Developers automating test workflows and API documentation upkeep
  • Postman users managing many collections and environments

Not for

  • Users who only need simple collection runs or single API calls
  • Developer-driven local iteration better served by CLI or direct API use
  • Anyone expecting an officially maintained Postman server (this is a community project)

Required permissions

  • Requires a Postman API key with access to the relevant resources (POSTMAN_API_KEY)
  • The API key grants access to all Postman resources the account has permissions for
  • Supports role-based permissions at workspace and collection levels

Risks and side effects

  • Project is under active development with potential breaking changes
  • Code is AI-generated (Cline with Claude 3.5 Sonnet) and should be reviewed carefully
  • The API key has broad access; leaking it could expose Postman resources to modification or deletion
  • The server communicates over stdio, which makes debugging harder

Setup

Before you start

Runtime：Node.js

POSTMAN_API_KEY requiredsecret Postman API key granting access to your Postman resources; generate it at Postman Account Settings (go.postman.co/settings/me/api-keys). It is shown only once.
  1. Install Node.js
  2. Clone the repository and cd into it
  3. Run pnpm install
  4. Run pnpm run build
  5. Generate an API key in Postman account settings and configure it as the POSTMAN_API_KEY environment variable
  6. Add the server config to Claude Desktop or Cline. Alternatively, install via Smithery: npx -y @smithery/cli install postman-api-server --client claude.
claude_desktop_config.json 
{"mcpServers":{"postman":{"command":"node","args":["/path/to/postman-api-server/build/index.js"],"env":{"POSTMAN_API_KEY":"CHANGEME"}}}}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "postman": {
      "command": "node",
      "args": [
        "/path/to/postman-api-server/build/index.js"
      ],
      "env": {
        "POSTMAN_API_KEY": "CHANGEME"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add postman -e POSTMAN_API_KEY=CHANGEME -- node /path/to/postman-api-server/build/index.js

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After connecting in Claude Desktop or Cline, run a simple query such as listing workspaces; if it returns your Postman workspaces, the POSTMAN_API_KEY is working. You can also run `pnpm run inspector` and check the Tools tab in the MCP Inspector.

Troubleshooting

  1. Verify POSTMAN_API_KEY is set correctly
  2. Confirm pnpm run build produced build/index.js
  3. Use MCP Inspector (pnpm run inspector, http://localhost:5173) for debugging; add the API key before connecting
  4. Restart Claude Desktop after updating the server, since it caches tool definitions
  5. Validate API key access with a simple query such as listing workspaces

Things to try

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

  • List all my Postman workspaces.
  • Show my Postman collections and how many requests each one has.
  • Create a new Postman environment called staging-test.
  • Add a comment to collection foo.

Use cases

Managing multiple Postman collections and folders
AI-driven automated testing and API documentation maintenance
Coordinating multi-environment management
Error-sensitive API testing and compliance checks

Supported clients

Claude Desktop
Cline
ZedPartial support

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

Overview

Postman MCP Server is a TypeScript-based MCP server that integrates with the Postman API, providing comprehensive management of Postman collections, environments, and APIs. Functionality is based on the official Postman OpenAPI specification. The project is under active development and may include breaking changes.

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 d29c2df5dedb Data synced 2026-10-19 Read the FMRS scoring method