Add Os-specific MCP configuration example to documentation

[samhvw8]

Important

Add platform-specific MCP configuration examples to documentation, including Windows and macOS/Linux setups.

• Documentation:
  • Adds platform-specific MCP configuration examples to using-mcp-in-roo.md.
  • Includes a Windows-specific example using cmd and npx for Puppeteer MCP server.
  • Provides a macOS/Linux example for comparison, using npx directly.

^{This description was created by for cffa726. It will automatically update as commits are pushed.}

[vercel]

@samhvw8 is attempting to deploy a commit to the Roo Code Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
roo-code-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 3, 2025 1:37am

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to cffa726 in 1 minute and 41 seconds

More details

• Looked at 56 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 5 drafted comments based on config settings.

1. docs/features/mcp/using-mcp-in-roo.md:236

• Draft comment:
  Consider using consistent note block delimiters. If your markdown processor expects triple colons (:::note), update '::::note' accordingly.
• Reason this comment was not posted:
  Comment looked like it was already resolved.

2. docs/features/mcp/using-mcp-in-roo.md:213

• Draft comment:
  Great JSON example for the Windows MCP configuration. Consider adding a brief note about potential npm version requirements for the '-y' flag (e.g. which npm versions support it), to help users on older setups.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is purely informative, suggesting to add a note about npm version requirements for a specific flag. It doesn't provide a specific code suggestion or ask for a test to be written. It also doesn't align with any of the additional rules provided.

3. docs/features/mcp/using-mcp-in-roo.md:236

• Draft comment:
  The admonition (note) block for macOS/Linux alternative configuration is clear. Ensure its syntax and style are consistent with other note blocks used throughout the documentation.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

4. docs/features/mcp/using-mcp-in-roo.md:253

• Draft comment:
  Overall, the added OS-specific configuration section is well integrated and clearly explains the Windows setup. Nice addition!
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

5. docs/features/mcp/using-mcp-in-roo.md:236

• Draft comment:
  Typographical issue: The admonition note block is initiated with '::::note' (four colons) on line 236. Typically, the correct syntax is ':::note' (three colons). Please update this to ensure consistent rendering of the note block.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50%
  This is a documentation formatting issue that could affect rendering. However, looking at the rules, we should not comment on pure UI/styling changes. The note block appears to be a new addition in this PR, but the exact syntax for admonitions may depend on the documentation platform being used. Without knowing the platform's requirements, we can't be certain this is actually incorrect.
  The documentation platform might actually support or require 4 colons for certain block types. We don't have enough context about the documentation system being used.
  Even if the platform does support both syntaxes, consistency in documentation is important. However, we don't have evidence that 3 colons is the standard in this codebase.
  Given the rules about not commenting on UI/styling changes and our lack of certainty about the documentation platform's requirements, we should not keep this comment.

Workflow ID: wflow_vcs2IGqvOmpOaZR3

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.