docs(roadmap): give the MCP server its M5 row - #389
Open
QSchlegel wants to merge 1 commit into
Open
Conversation
Eleven PRs of MCP work merged in August — the stateless endpoint and its OAuth 2.1 authorization server (#357), governance tools, scope-by-scope consent (#367), connection management and per-wallet activity (#363, #365), the published tool list, GUI-client setup docs (#370) and read-only document tools on a v1 REST surface (#376) — against no roadmap row at all. The roadmap named MCP exactly once, in Andre's M6. Also cross-references that M6 row, because M5 now delivers the endpoint, OAuth, scopes and tool registry it was implicitly going to build: what remains there is the unsigned-transaction write path, not a second server. The shipped surface is 15 tools over 4 scopes with only `ballots:write` writing and nothing signing or broadcasting, so M6's "must not sign or broadcast" constraint already holds by construction.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Eleven PRs of MCP server work merged in August against no roadmap row at all. Before this,
ROADMAP.mdmentioned MCP exactly once — in Andre's M6, as "MCP unsigned transaction creation" — which reads as though the server is still to be built.What actually shipped in M5
BotClaimTokenpatternSurface as shipped: 15 tools over 4 scopes —
wallets:read,governance:read,documents:read,ballots:write. One write scope; nothing signs or broadcasts.Why M6 changed too
M5 now delivers the endpoint, OAuth, scopes and tool registry that Andre's M6 row was implicitly going to build, so that row is cross-referenced: what remains there is the unsigned-transaction write path, not a second server.
Worth noting for that month — M6's own constraint, "MCP must not sign or broadcast on the user's behalf", already holds by construction:
src/lib/mcp/scopes.tsdefines no signing or broadcast scope, so it is enforced by the grant model rather than by care.Scope
ROADMAP.mdonly — three lines. No code, no schema, no migration.