[Improvement] Support MCP Server Prompts #8004
Description
What specific problem does this solve?
Title: Support for Selecting and Using MCP Server Prompts
Problem Description
Currently, RooCode does not allow users to discover or use prompts provided by MCP servers. MCP servers can include custom prompts—often with variables—that are specifically designed to help users leverage that server’s tools and resources more effectively.
Without support for these prompts, users miss out on valuable, server-specific guidance and must manually craft requests from scratch. This adds friction and makes the system less approachable, especially for users new to a given MCP server.
Who is Affected
All RooCode users who have MCP servers enabled, particularly those relying on MCP servers for complex tasks or specialized workflows.
When This Happens
Whenever a user interacts with an MCP server through RooCode and there are prompts available that could streamline or enhance that interaction.
Current vs. Expected Behavior
- Current: MCP server prompts exist but are invisible to the user within RooCode.
- Expected: Users should have a way to view, select, and use available prompts from each MCP server directly in RooCode. Ideally, prompts with variables should allow users to provide input through a user-friendly interface (with defaults and value constraints where applicable).
Impact
- Efficiency: Users waste time recreating prompts manually.
- Accessibility: New users have a steeper learning curve since they cannot rely on curated prompts designed for best practices.
- Up-to-Date Guidance: Because prompts are hosted by the MCP server, users automatically benefit from the latest improvements as soon as maintainers update them.
Suggested Direction (Optional)
Explore integrating MCP server prompts into RooCode’s existing / command pattern. For example, users could type /mcp.<mcpServer>.<registeredPrompt> to quickly invoke a prompt, similar to GitHub Copilot’s approach. This would provide a consistent and discoverable way to access both custom and server-provided prompts while ensuring users always have access to the most current versions.
Additional context (optional)
Roo Code Task Links (Optional)
No response
Request checklist
- I've searched existing Issues and Discussions for duplicates
- This describes a specific problem with clear impact and context
Interested in implementing this?
- Yes, I'd like to help implement this feature
Implementation requirements
- I understand this needs approval before implementation begins
How should this be solved? (REQUIRED if contributing, optional otherwise)
No response
How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)
No response
Technical considerations (REQUIRED if contributing, optional otherwise)
No response
Trade-offs and risks (REQUIRED if contributing, optional otherwise)
No response