feat(mcp): add tool registry to handle tools from different endpoints #1237
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
registry tracks tools and from which endpoints they originated from
keegancsmith
approved these changes
Dec 10, 2025
Member
keegancsmith
left a comment
keegancsmith
left a comment
There was a problem hiding this comment.
Should we just update the server now to include deep search tools on v1? That way we can avoid making this more complicated. Otherwise we can move forward with this.
Contributor
Author
A part of me think we should. I'd still keep this registry though but remove the endpoint tracking. Site note: should it be deep-search instead of deepsearch? |
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.
Add a tool registry which keeps tracks of tools and from which endpoints they originated from. We need to know the endpoint so that we a tool call is made it is made against the correct endpoint.
Test plan
go run ./cmd/src deepsearch -question 'which repo uses bazel?'