Repository navigation
fix(mcp): expose full-page board deep links to agents - #51
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
Agents could list and modify boards but received no browser URL, leading users to the embedded view. Board summaries and full-board responses now include a canonical
urlpointing to the existing/board/:boardIdpage. This covers list/read/create and full-board mutation responses and honorsZEROBOARD_WEB_URL.The existing route retains sign-in and access checks. Agent documentation directs user-facing links to this field and reserves embed URLs for embedding.
Validation: all 181 MCP tests pass, including public/private summary, read, and mutation URL checks. All 49 board-data checks also pass with a custom web origin and trailing slash. No frontend behavior changes or new browser verification.
Closes #50.