gnodet commented on code in PR #26146:
URL: https://github.com/apache/camel/pull/26146#discussion_r3952452498
##########
dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/Run.java:
##########
@@ -3109,6 +3122,17 @@ static class ServerOptions {
+ "Also binds the management server to 127.0.0.1
(affecting health/metrics when --observe is used).")
boolean mcp;
+ @Option(names = { "--mcp-stdio" }, defaultValue = "false",
+ description = "Expose tagged ai-tool routes as MCP tools over
process stdin/stdout for IDE subprocess "
+ + "integration (no HTTP port). Requires
--mcp-tags or camel.server.mcp-tags. "
+ + "Logging and startup summaries are routed to
stderr so stdout carries MCP protocol only.")
+ boolean mcpStdio;
+
+ @Option(names = { "--mcp-tags" },
+ description = "Comma-separated ai-tool tags to expose when
--mcp-stdio is enabled (maps to "
+ + "camel.server.mcp-tags)")
Review Comment:
💬 **Open question (from @davsclaus review, still unanswered):** The
description says _"Comma-separated ai-tool tags to expose **when --mcp-stdio is
enabled**"_. But `camel.server.mcp-tags` is transport-agnostic — it applies to
HTTP transport too. Should `--mcp-tags` also be wired when `--mcp` (HTTP) is
active, or is it intentionally stdio-only for now? If the latter, please file a
follow-up JIRA and reference it in the description so the gap is tracked.
--
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]
