zbendhiba commented on PR #8950: URL: https://github.com/apache/camel-quarkus/pull/8950#issuecomment-5178896516
> > The engine only uses ToolManager APIs from the core module. Would it be possible to depend on just the core and let users choose the transport (`quarkus-mcp-server-http` or `quarkus-mcp-server-stdio`) in their own pom? That would support both HTTP and stdio use cases without hardcoding the transport. > > mhhhh I would like to achieve the following, OOB Camel MCP will use the http transport, but somehow, the user can configure stdio if needed. As of now this is not possible, I'll do a research if this is feasible somehow on all the runtimes. WDYT @zbendhiba ? What I suggest is: instead of depending on `quarkus-mcp-server-http`, depend only on `quarkus-mcp-server-core-parent`. Then on the tests, users can pull either `quarkus-mcp-server-http` or `quarkus-mcp-server-stdio` (which probably means 2 flavor of integration tests) Or have 2 camel quarkus mcp server. I don't understand what's limiting us to HTTP. I don't know. WDYT @jamesnetherton @JiriOndrusek -- 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]
