Add MCP documentation and images for enhanced guidance

[hannesrudolph]

Important

Add comprehensive MCP documentation to Roo Code, including usage, transport mechanisms, and API comparisons, and update the sidebar accordingly.

• Documentation:
  • Adds mcp/overview.md to introduce MCP and its documentation structure.
  • Adds mcp/what-is-mcp.md explaining MCP's purpose and architecture.
  • Adds mcp/using-mcp-in-roo.md detailing how to configure and use MCP in Roo Code.
  • Adds mcp/server-transports.md comparing STDIO and SSE transport mechanisms.
  • Adds mcp/mcp-vs-api.md comparing MCP with REST APIs.
• Redirection:
  • Replaces content in advanced-usage/mcp.md with a redirect to mcp/using-mcp-in-roo.md.
• Sidebar Update:
  • Updates sidebars.ts to include new MCP documentation under a dedicated category.

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

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to 51a32cd in 1 minute and 28 seconds

More details

• Looked at 724 lines of code in 7 files
• Skipped 9 files when reviewing.
• Skipped posting 12 drafted comments based on config settings.

1. docs/advanced-usage/mcp.md:6

• Draft comment:
  The redirect looks good; ensure the target URL (/mcp/using-mcp-in-roo) exists and is correct.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

2. docs/mcp/mcp-vs-api.md:1

• Draft comment:
  Markdown formatting and content are clear and consistent with our standards.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

3. docs/mcp/overview.md:1

• Draft comment:
  The overview page structure is well-organized and meets documentation standards.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

4. docs/mcp/server-transports.md:1

• Draft comment:
  Comprehensive details on STDIO and SSE transports; code examples follow best practices.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

5. docs/mcp/using-mcp-in-roo.md:1

• Draft comment:
  The guide is thorough, clearly detailing steps to configure and manage MCP servers.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

6. docs/mcp/what-is-mcp.md:1

• Draft comment:
  Content provides a clear, concise explanation of MCP and its use cases.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

7. sidebars.ts:38

• Draft comment:
  Consider removing the 'advanced-usage/mcp' entry from the Advanced Usage category since MCP now has its own dedicated category. This will avoid redundancy in navigation.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

8. docs/advanced-usage/mcp.md:6

• Draft comment:
  Good use of Docusaurus redirect. Consider a brief inline comment explaining the purpose of the redirect for future maintainers.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

9. docs/mcp/mcp-vs-api.md:12

• Draft comment:
  Table formatting and content are clear and informative. No changes required.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

10. docs/mcp/using-mcp-in-roo.md:24

• Draft comment:
  Excellent step-by-step guide with images. Ensure all image assets referenced (e.g., ‘/img/using-mcp-in-roo/using-mcp-in-roo.png’) are available and optimized for accessibility.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

11. sidebars.ts:48

• Draft comment:
  New MCP category in sidebars is well organized. Confirm the ordering is intentional and matches your documentation structure.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

12. docs/mcp/mcp-vs-api.md:97

• Draft comment:
  It looks like there's no newline at the end of the file. Please add a newline at the end for consistency and to follow best practices.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%
  While having a trailing newline is generally considered good practice and follows POSIX standards, this is a very minor formatting issue that should be handled automatically by EditorConfig, Prettier, or similar tools. Our rules state that we should not comment on things that should be handled by automated tools. Additionally, this is a documentation file, not code, so the impact is even less significant.
  The comment is technically correct about following best practices. Missing trailing newlines can cause issues with some tools and version control systems.
  While technically correct, this is exactly the kind of formatting issue that should be handled by automated tools rather than manual review comments. It adds noise to the review process.
  Delete the comment as it addresses a minor formatting issue that should be handled by automated tools rather than manual review.

Workflow ID: wflow_h3F5ue9vC37MdcV4

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[mrubens]

🚀