feat(server): expose board prompts and resources over MCP - #49
Merged
Conversation
Tools were the server's only MCP surface, so clients that support prompt templates and attachable context (and the LobeHub score's optional items) saw none. Register two resources — bob://board/status (JSON) and bob://board/report (markdown) — sharing the board_status / board_report tool logic via extracted builders, and two prompts: new-task (rough ask -> well-formed task) and triage-board (audit + safe fixes).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The MCP server registered tools only. Clients that surface prompt templates and attachable context resources got nothing, and the two optional LobeHub score items (Includes Prompts / Includes Resources) sat at zero.
bob://board/status(JSON dispatch state) andbob://board/report(markdown standup/audit), reusing the board_status/board_report tool logic through extractedboardStatusPayload()/renderBoardReport()builders — no behavior change to the tools.new-task(arg: request — provisions one well-formed task, dedupe + staged-create guidance) andtriage-board(board audit, propose-then-apply-safe-fixes).Verified over stdio:
prompts/list,resources/list,resources/read(live board state), andprompts/getall answer correctly alongside the existing 23 tools.