jamesnetherton commented on PR #25203: URL: https://github.com/apache/camel/pull/25203#issuecomment-5140483260
Can we slow down a bit and think things through before PR approval. From the Jira ticket: > This would allow any Camel application (Spring Boot, Quarkus, standalone) to embed an MCP server, not only applications started via the Camel CLI. Quarkus already has a solution for MCP [optimized](https://github.com/quarkiverse/quarkus-mcp-server) for the runtime. So some analysis is needed here and in Camel Quarkus for how best to leverage that. There's also a notes section in the ticket: > - This needs more design thinking — created this issue to capture the idea before it gets lost. Key questions to consider: > - How does the embedded MCP server relate to the standalone MCP server ([CAMEL-23852](https://issues.apache.org/jira/browse/CAMEL-23852))? > - Which MCP tools should be exposed — catalog tools, runtime introspection tools, or both? > - Should routes automatically become MCP tools, or require explicit opt-in (e.g. via route metadata or a service catalog)? > - How does this relate to Wanaku for enterprise-scale MCP governance? Not sure if any of those points have been addressed here? -- 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]
