mcp: HasPrompts capability advertised but no prompts registered

Bug

The MCP server declares HasPrompts: true in its capabilities (pkg/mcp/mcp.go, line 84), but no prompts are registered anywhere in the codebase:

&mcp.ServerOptions{
    Instructions:       instructions(s.readonly),
    HasPrompts:         true,   // no prompts are registered
    HasResources:       true,
    HasTools:           true,
    InitializedHandler: ...,
}

Per the MCP specification, when a server declares prompts capability, clients may call prompts/list and expect results.

Impact

MCP clients that enumerate prompts will get an empty list, which is misleading
Some clients may present empty prompt UI or make unnecessary protocol round-trips
Incorrectly signals to MCP clients that the server supports a feature it does not

Fix

Set HasPrompts to false until prompts are actually implemented:

 &mcp.ServerOptions{
     Instructions:       instructions(s.readonly),
-    HasPrompts:         true,
+    HasPrompts:         false,
     HasResources:       true,
     HasTools:           true,
     InitializedHandler: ...,
 }

/assign

Duplicate of #3734. PR #3737 there adds an actual prompt instead of flipping the flag — closing this in favor of that path.

Navigation Menu

Repository navigation

mcp: HasPrompts capability advertised but no prompts registered #3689

Bug

Impact

Fix

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

mcp: HasPrompts capability advertised but no prompts registered #3689

Description

Bug

Impact

Fix

Activity

Elvand-Lie commented on May 9, 2026

lkingland commented on May 16, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions