Federico Mariani created CAMEL-24352:
----------------------------------------
Summary: camel-jbang - Serve ai-tool routes over the MCP stdio
transport
Key: CAMEL-24352
URL: https://issues.apache.org/jira/browse/CAMEL-24352
Project: Camel
Issue Type: Improvement
Components: camel-jbang, camel-ai
Reporter: Federico Mariani
Follow-up to CAMEL-24308. Local coding agents and IDEs launch MCP servers as
child processes speaking JSON-RPC over stdin/stdout (the {{"command": ...}}
entry in an {{mcp.json}}). A developer should be able to register {{camel run
tools.yaml}} that way and have the tagged {{ai-tool}} routes served as local
tools — no port, no URL, process lifetime = session.
The transport is nearly free: the MCP Java SDK ships
{{StdioServerTransportProvider}}, so this is a thin engine variant behind the
existing {{McpServerEngine}} SPI (e.g. a
{{camel.server.mcp-transport=http|stdio}} option or a JBang flag such as
{{--mcp-stdio}}), with the bridge unchanged.
The actual work is stdout hygiene: in stdio mode stdout must carry only
protocol frames, so JBang needs to route all logging, the banner and
route-startup summaries to stderr (or a file) and suppress anything else
printed to stdout.
Spring Boot and Quarkus already document their stdio setups via their native
MCP stacks (camel-mcp-server-starter / camel-quarkus-mcp-server usage docs);
this issue covers Camel Main / JBang.
_Filed by Claude Code on behalf of Federico Mariani_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
