Repository navigation
Fix MCP dispatch for path-mounted boards - #56
Merged
Merged
Conversation
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.
What changed
MCP tool calls use
BoardClientwith the board's public base URL, then dispatch the resulting REST request back into the Hono app. On boards mounted under a path such as/bbs, that internal dispatch was sent directly to the root-based app, leaving the/bbsprefix in place and returning 404s.Route internal MCP dispatch through the same
mountAtadapter as the network listener. Root-mounted boards keep the empty-prefix behavior; path-mounted boards now reach the same REST handlers as browser and API requests.Verification
Production reproduction confirmed MCP initialization and
tools/listworked on the/bbsboards, while every MCP tool call failed with 404. The fix will be verified with authenticatedboard_overview, read, and reply calls on both mounted boards after deployment.