| FMRS | 55 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 9 / 20 | 12 / 20 |
|---|
| Security and permissions | 9 / 20 | 18 / 20 |
|---|
| Maintenance | 11 / 20 | 16 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| 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
| - Engineering teams scaling AI coding agents while controlling spend
- Platform teams that need auditable, rollback-aware agent execution records
- Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
|
|---|
| 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
| - Developers who just want a simple code-completion helper without run governance
- Teams unwilling to accept local JSONL run records with HMAC signing
- Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
|
|---|
| 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
| - Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
- Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
- Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
- Execution of user-configured verifier commands (e.g. npm test)
|
|---|
| 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
| - Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
- Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
- Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
- Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
|
|---|
| Supported clients | Claude Code, Claude Desktop, Cursor, VS Code, Codex, Antigravity CLI, GitHub Copilot CLI, Kiro, Gemini CLI | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 0 | 0 |
|---|