Gucvii commented on issue #15332: URL: https://github.com/apache/dubbo/issues/15332#issuecomment-2821500651
Thank you for your proposal! I think the idea of extending Dubbo with MCP functionality is fantastic, and I've carefully read the proposal and comments. I particularly appreciate the approach of leveraging OpenAPI annotations to provide method descriptions. However, I have a couple of questions and suggestions for consideration: 1. MCP Primitives: In MCP, there are three primary primitives for server-side functionality: Tool, Prompt, and Resource. The mcp-java-sdk utilizes distinct methods (addTool, addResource, addPrompt) for registering these different types. I believe it would be highly beneficial for Dubbo to consider adding either a new annotation or annotation attributes to better align with the MCP standard. 2. Granular Control Over Exposed Methods: My second point concerns which methods within a class annotated with @DubboService will be exposed to the MCP server endpoint. Users might have sensitive methods within their Dubbo services that they would not want large language models (LLMs) or other AI systems to be able to access (as this could potentially be hacked). Therefore, I think it's important to consider mechanisms for more granular control over which specific methods are exposed as MCP tools. These are just my initial thoughts, and I'm eager to hear the community's perspectives on these points. I believe addressing these aspects will make the Dubbo MCP integration even more robust and secure. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
