feat(mcp): Add customizable tool name prefix generation #4326
+503
−88
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
- Introduce McpToolNamePrefixGenerator interface for flexible tool naming - Add default and no-prefix generator implementations - Update SyncMcpToolCallback and AsyncMcpToolCallback to accept prefixed names - Enhance tool callback providers to use the prefix generator - Add comprehensive tests for prefix generation functionality - Update documentation with tool name prefix generation examples - Rename McpMetadata to McpConnectionInfo with builder pattern This change allows users to customize how MCP tool names are prefixed, helping to avoid naming conflicts when integrating tools from multiple MCP servers. By default, the MCP client name is used as a prefix, but users can provide custom implementations or disable prefixing entirely. The McpConnectionInfo record now provides a cleaner API with a builder pattern and better encapsulates the connection metadata including client capabilities, client info, and initialization results. BREAKING CHANGE: McpMetadata renamed to McpConnectionInfo. Constructors for SyncMcpToolCallback and AsyncMcpToolCallback that don't accept prefixedToolName parameter are deprecated. Signed-off-by: Christian Tzolov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This change allows users to customize how MCP tool names are prefixed, helping to avoid naming conflicts when integrating tools from multiple MCP servers. By default, the MCP client name is used as a prefix, but users can provide custom implementations or disable prefixing entirely.
The McpConnectionInfo record now provides a cleaner API with a builder pattern and better encapsulates the connection metadata including client capabilities, client info, and initialization results.
BREAKING CHANGE: McpMetadata renamed to McpConnectionInfo. Constructors for SyncMcpToolCallback and AsyncMcpToolCallback that don't accept prefixedToolName parameter are deprecated.