mcp: either register prompts or set HasPrompts to false
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 365
- Forks
- 223
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 25
Description
Problem
pkg/mcp/mcp.go sets HasPrompts: true on ServerOptions, but New() only registers tools and resources thus no prompts are added anywhere under pkg/mcp/.
Clients that trust capability flags may assume prompts exist when they do not.
Options
- Set
HasPrompts: falseuntil prompts are implemented, or - Add one or more MCP prompts (e.g. guided “create / build / deploy” workflow) and tests.
References
pkg/mcp/mcp.go(HasPrompts: true, tools/resources registration below).
I guess this is kind of bug or area of implementing mcp. But will sure add a good solution :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in pkg/mcp/mcp.go, inspect ServerOptions and the registrations performed by New(). Confirm how the advertised prompt capability relates to the absence of registered prompts, then choose and document one of the issue's two options. Done means the capability accurately reflects the server behavior, with tests covering the selected behavior if prompts are added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100