Postman

Full API lifecycle management through the Postman MCP Server (111+ tools for workspaces, collections, specs, environments, mocks, and monitors). Sync specs, generate code, run tests, create mocks, publish docs, and audit security.

Prerequisites

Setup check: Call getAuthenticatedUser via MCP. If it succeeds, you're connected. If it fails, walk through Setup below.

Setup

If MCP tools are not available or getAuthenticatedUser fails:

1. Get a Postman API key at https://postman.postman.co/settings/me/api-keys — "Generate API Key", name it "Claude Code", copy the key (starts with PMAK-).
2. Set the environment variable — export POSTMAN_API_KEY=PMAK-your-key-here (add to ~/.zshrc or ~/.bashrc to persist).
3. Verify: call getAuthenticatedUser, then list workspaces and collection counts so the user sees they're connected.

Routing

Match the user's intent to a workflow, then read that workflow's reference file and follow it. Each file is loaded on demand — read one only when the task needs that depth (progressive disclosure).