You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an MCP server advertises the prompts capability during initialization, Warp's MCP client should query prompts/list and store the returned prompts on the server's info struct, mirroring the existing handling for tools and resources.
Currently, the post-init block in app/src/ai/mcp/templatable_manager/native.rs (the same block #9436 just touched) queries tools/list and resources/list but never prompts/list. As a result, MCP servers whose primary surface is prompt templates are invisible to Warp.
Query prompts/list per advertised capability, fail-soft on errors (log + empty vec), matching the existing branches.
Store the result on TemplatableMCPServerInfo (new prompts: Vec<rmcp::model::Prompt> field).
Extend the each_capability_is_queried_independently regression test with the prompts dimension.
The UI surface for prompts (slash-command dispatch like /<server>:<prompt>, argument prompts UI) is a separate, larger lift and warrants its own issue — plausibly the ready-to-spec flow.
I'd be happy to pick this up with a PR once the issue is labeled.
Is your feature request related to a problem? Please describe.
MCP servers that primarily expose prompt templates — e.g., prompt galleries, prompt-collection servers — are unusable in Warp today because the client never asks the server for them. The user has no signal that the server has anything to offer; from their perspective the server appears empty even though its main surface is fully populated.
Affects all platforms — selecting macOS in the OS field only because the form requires a single value.
Worth verifying before final scope: that the warpdotdev/rmcp fork at the pinned revision exposes service.list_all_prompts() (it already exposes list_all_tools and list_all_resources, so this is highly likely).
Pre-submit Checks
Describe the solution you'd like?
When an MCP server advertises the
promptscapability during initialization, Warp's MCP client should queryprompts/listand store the returned prompts on the server's info struct, mirroring the existing handling fortoolsandresources.Currently, the post-init block in
app/src/ai/mcp/templatable_manager/native.rs(the same block #9436 just touched) queriestools/listandresources/listbut neverprompts/list. As a result, MCP servers whose primary surface is prompt templates are invisible to Warp.Per the MCP 2025-03-26 spec — capability negotiation, a client should invoke a list method when (and only when) the corresponding capability has been advertised by the server.
Proposed scope (v1, data-only):
should_query_prompts()predicate next to the resources/tools predicates introduced in fix(mcp): query tools/resources independently per advertised capability (#6798) #9436.prompts/listper advertised capability, fail-soft on errors (log + empty vec), matching the existing branches.TemplatableMCPServerInfo(newprompts: Vec<rmcp::model::Prompt>field).each_capability_is_queried_independentlyregression test with the prompts dimension.The UI surface for prompts (slash-command dispatch like
/<server>:<prompt>, argument prompts UI) is a separate, larger lift and warrants its own issue — plausibly theready-to-specflow.I'd be happy to pick this up with a PR once the issue is labeled.
Is your feature request related to a problem? Please describe.
MCP servers that primarily expose prompt templates — e.g., prompt galleries, prompt-collection servers — are unusable in Warp today because the client never asks the server for them. The user has no signal that the server has anything to offer; from their perspective the server appears empty even though its main surface is fully populated.
Additional context
spawn_serverinapp/src/ai/mcp/templatable_manager/native.rs). fix(mcp): query tools/resources independently per advertised capability (#6798) #9436 should merge first; this change conflicts with it.service.list_all_prompts()(it already exposeslist_all_toolsandlist_all_resources, so this is highly likely).Operating system (OS)
macOS
How important is this feature to you?
3
Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1
None