Postman MCP Server: Collections and API Specs in Claude
Postman's official MCP server connects Claude to workspaces, collections, specs and environments. Minimal, Code and Full modes, Claude Code commands.
By Claudekit Team Published 2 min read
- Type
- MCP Server
- Pricing
- Freemium
- Repository
- github.com
- GitHub stars
- 325
- Website
- learning.postman.com
The Postman MCP Server is Postman’s official Model Context Protocol server. It connects Claude to your Postman workspaces, collections, specifications and environments, so Claude can create and update collections, manage environment variables, build specs from code and generate client code from API definitions.
Who it is for
API developers and QA teams who keep their APIs in Postman and want Claude Code to keep code, specs and collections in sync.
Install
Pick a mode first. Postman’s docs give one Claude Code command per mode. Minimal, with OAuth:
claude mcp add --transport http postman https://mcp.postman.com/minimal
Swap the path for /code (code generation), /mcp (Full, 100+ tools) or /learn (Postman docs search). To use an API key instead of OAuth:
claude mcp add --transport http postman https://mcp.postman.com/minimal --header "Authorization: Bearer <POSTMAN_API_KEY>"
EU accounts use mcp.eu.postman.com with an API key. To run the server locally, the README’s command is npx @postman/postman-mcp-server with a POSTMAN_API_KEY environment variable. Treat that key like a password.
Use cases
- API testing: run your collection against an API you just changed. Use the local server for localhost APIs.
- Spec from code: “Create an OpenAPI spec from these route handlers and generate a collection.”
- Collection upkeep: tag collections, update docs and add comments across several at once.
- Client code: generate a typed client for an internal API from its definition.
Pros
- Official, Apache-2.0 licensed, with hosted and local options.
- Mode choice keeps the tool list small by default.
- OAuth on the US remote server, so no key in your config.
- Documented Claude Code commands for every mode.
Cons and caveats
- Full mode loads 100+ tools, which takes up context. Start with Minimal.
- The remote server cannot reach APIs on your machine.
- EU accounts must use an API key.
- Server code changes are synced from Postman’s internal source, so the repo takes issues rather than code PRs under
src/.
Links
- Repo: postmanlabs/postman-mcp-server
- Docs: Postman MCP Server
- Package: @postman/postman-mcp-server on npm
- Related: GitHub MCP server, MCP Inspector, MCP servers guide
Checked 24 Oct 2026 against the vendor repo, the Postman docs and the MCP registry.
Frequently asked questions
What is the difference between Minimal, Code and Full?
Minimal (the default) has essential tools for single collections, workspaces or environments. Code generates client code from API definitions. Full includes all Postman API tools, more than 100.
Does the remote server support OAuth?
Yes, the US remote server at mcp.postman.com uses OAuth. The EU remote server and the local server support only Postman API key authentication.
Can it test APIs running on my machine?
Use the local server for that. Postman notes the remote server has no network access to your workstation.
What license is it under?
The repository is Apache-2.0 licensed.