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
P
Postman MCP Server
Community
An MCP server providing access to the Postman API
GitHub source repository ↗
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.
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.
Setup
- 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"}}}}
Fit and risk
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
Troubleshooting
- Verify POSTMAN_API_KEY is set correctly
- Confirm pnpm run build produced build/index.js
- Use MCP Inspector (pnpm run inspector, http://localhost:5173) for debugging; add the API key before connecting
- Restart Claude Desktop after updating the server, since it caches tool definitions
- Validate API key access with a simple query such as listing workspaces
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 DesktopFull support
ClineFull support
ZedPartial support