feat(sdlc-pipeline): add Postman MCP, auto-select Newman, update onbo… - #12
feat(sdlc-pipeline): add Postman MCP, auto-select Newman, update onbo…#12codeartstest wants to merge 1 commit into
Conversation
…arding - mcp-settings.json: add Postman HTTP MCP entry (https://mcp.postman.com/mcp) - config-reference.md: add Postman + terraform to MCP table - service-onboarding.md: update Postman MCP config note, expand table with Postman install and Newman cloud collection steps - multi-tool-selection-plan.md: add Postman->Newman auto-select rule (post-processing), update Q3 option descriptions, remove soft warning
📝 WalkthroughWalkthroughPostman is added to MCP selection and HTTP server configuration. Tool-selection documentation now auto-selects Newman when Postman is chosen. Onboarding documentation adds Postman installation, API-key configuration, smoke testing, and Newman collection execution instructions. ChangesPostman MCP setup
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@skills/sdlc-agentic-pipeline/references/setup/service-onboarding.md`:
- Line 144: Update the Postman row in the smoke-test table to replace the
invalid `postman MCP list workspaces` command with the documented `postman
search workspaces` CLI command, unless the row specifically requires an MCP
invocation format.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 3f28fcaa-3f87-4551-a6b7-ea167580e1f1
📒 Files selected for processing (4)
skills/sdlc-agentic-pipeline/references/config-reference.mdskills/sdlc-agentic-pipeline/references/setup/multi-tool-selection-plan.mdskills/sdlc-agentic-pipeline/references/setup/service-onboarding.mdskills/sdlc-agentic-pipeline/references/templates/mcp-settings.json
| | SDD Toolkit | N/A (built-in) | N/A | N/A | | ||
| | OpenSpec | `openspec --version` | `npm install -g @fission-ai/openspec@latest` | `openspec list` | | ||
| | Postman | N/A (MCP) | N/A | `postman MCP list workspaces` | | ||
| | Postman | N/A (MCP) | Copy `references/templates/SKILL.md` to `.codeartsdoer/skills/postman/SKILL.md` | `postman MCP list workspaces` | |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
postman search workspaces --help
postman MCP list workspaces --helpRepository: CodeArtsAgent/CodeArtsSkills
Length of output: 252
🌐 Web query:
Postman CLI search workspaces command documentation
💡 Result:
The Postman CLI includes a dedicated command to search for workspaces, which is part of its broader search functionality. The command to search for workspaces is: postman search workspaces This command allows you to search for workspaces by name or keyword [1][2]. In addition to searching, the Postman CLI provides separate workspace management commands for CI/CD pipelines, such as postman workspace prepare (to validate local elements) and postman workspace push (to synchronize local elements with the Postman cloud) [3][4][5]. Note that these workspace management commands are distinct from the search commands [2]. For a complete reference of all available Postman CLI commands, you can consult the official Postman CLI documentation [1][6].
Citations:
- 1: https://learning.postman.com/docs/postman-cli/postman-cli-options.md
- 2: https://learning.postman.com/docs/postman-cli/postman-cli-options
- 3: https://learning.postman.com/v11/docs/postman-cli/postman-cli-options
- 4: https://learning.postman.com/docs/postman-cli/postman-cli-workspace
- 5: https://learning.postman.com/docs/postman-cli/postman-cli-workspace.md
- 6: https://learning.postman.com/docs/postman-cli/postman-cli-overview.mdx
🌐 Web query:
Postman CLI MCP list workspaces command documentation
💡 Result:
There is no specific "Postman CLI" command for listing workspaces within the Model Context Protocol (MCP). The Postman CLI and the Postman MCP Server are distinct tools with different purposes [1][2][3]. The Postman CLI is a standalone terminal application used for tasks such as running collections, monitoring APIs, and synchronizing local files with Postman cloud [3]. It does not natively implement MCP [3]. The Postman MCP Server is a separate integration that allows AI agents and IDEs (such as Cursor, Claude, or VS Code) to interact with Postman resources [1][2][4]. Within the Postman MCP Server, the tool to list workspaces is defined as list_workspaces [5][6]. To use the list_workspaces tool: 1. Ensure you have the Postman MCP Server configured [1][4]. 2. The tool is typically invoked by an AI agent through the Model Context Protocol interface rather than via a direct terminal command [2][7]. 3. If you are interacting with the tool programmatically (e.g., via an MCP SDK), you would call the tool list_workspaces [5][6]. The tool accepts optional parameters such as type and createdBy to filter the results [5]. It is recommended to use the official Postman MCP Server to ensure compatibility with your AI agents, as documented in the official Postman learning resources [2][8][9]. Prompts to AI agents should explicitly mention using the Postman MCP server to avoid confusion with CLI commands [7].
Citations:
- 1: https://github.com/postmanlabs/postman-mcp-server
- 2: https://www.postman.com/product/mcp-server/
- 3: https://learning.postman.com/docs/postman-cli/postman-cli-overview
- 4: https://github.com/postmanlabs/postman-api-mcp/
- 5: https://glama.ai/mcp/servers/@PostmanV3/mcp-PostmanV3/tools/list_workspaces
- 6: https://github.com/SalehKhatri/postman-mcp
- 7: https://learning.postman.com/docs/developer/postman-api/postman-mcp-server/postman-mcp-server-tips
- 8: https://learning.postman.com/docs/reference/postman-api/postman-mcp-server/overview
- 9: https://learning.postman.com/docs/reference/postman-api/postman-mcp-server/postman-mcp-local-server
Replace the invalid shell command in the Postman smoke-test row.
postman MCP list workspaces is not a documented Postman CLI command; the documented CLI workspace search command is postman search workspaces. Use the valid CLI command here, or if this row is meant to describe an MCP tool invocation, rewrite it as the actual MCP tool call format instead of a shell command.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/sdlc-agentic-pipeline/references/setup/service-onboarding.md` at line
144, Update the Postman row in the smoke-test table to replace the invalid
`postman MCP list workspaces` command with the documented `postman search
workspaces` CLI command, unless the row specifically requires an MCP invocation
format.
2 participants
…arding
Summary by CodeRabbit