Feature: Include MCP Prompts

[cstroliadavis]

Description:

MCP Servers have the ability to provide Prompts. When they do, it's likely to be prompts that would assist you in using that particular MCP server's tools and/or resources.

It would be useful if we had a way of selecting and using those prompts if they are available within any MCP servers we have enabled.

It would likely be best if at least #968 is complete before starting this one.

Reason:

I sort of mentioned this already, but basically, even though many have not been doing it yet (because they are about as sexy as documentation for most devs), MCP Servers have the ability to include custom prompts, and those prompts can include variables, BTW. These prompts could simply be a specialized prompt library by some prompt guru, they could be an MCP that stores custom prompts for the user themselves, or they might be prompts that are designed to help make full usage of the MCP server's tools and resources, knowing explicitly what to say to get the most benefit from the server.

This might make this a compelling reason for including the ability to use these custom prompts. (Possibly, this could be done before #969 and pave the way for people who don't want to wait around for it to be embedded in the tool).

Examples:

I normally like to put together examples, but this time I ran out of time. What I envision is that if you were to go to the MCP tab in the tool, you would see a third MCP tab for the server itself that says "Prompts" on it.

I'm not sure if this makes sense or not, so we could potentially create some other property if it does not, but I think if we put these into the "alwaysAllow" list, they would show up in the list (from #968), but otherwise they would not show up. That way a person could decide not to have those prompts clutter their list if they prefer. I leave it up to the dev to decide what make the most sense here.

Anyway, it would be useful if, similar to some of the suggestions I made in #970, we could augment the variables that come with the MCP server to handle how they are shown to us (it's a shame that these were not provided the same level of detail that tools are). If we don't I would imagine that they would just show as shortText with no default value, and the text to show would be the "name" of the variable (argument). But, if we could augment this to allow us to set defaults, or limit choices for fields that are supposed to only be specific values, or true false, etc, that would be very useful, it would also be potentially useful if we could automatically include certain types of roo variables.

Here is at least an example of what the prompts might look like in the chat selection: