gnodet commented on PR #23346:
URL: https://github.com/apache/camel/pull/23346#issuecomment-4502774368
_Claude Code on behalf of Guillaume Nodet_
### Design Update: Runtime tools via JBang MCP Server
Reworked the approach based on discussion. Instead of embedding an MCP
server inside each Camel application (which required hardcoding the route
filename or port in the MCP config), the runtime tools now live in the existing
`camel-jbang-mcp` Quarkus MCP Server.
**Key advantage**: The MCP config is static and trivial:
```json
{"command": "jbang", "args": ["camel", "mcp"]}
```
No route name, URL, or port — the server auto-discovers running Camel
processes via `~/.camel/` status files.
**Communication**: Uses the existing file-based IPC protocol that
`LocalCliConnector` already supports. Enhanced it with per-request file
multiplexing (`{pid}-action-{requestId}.json`) so multiple MCP clients can
operate concurrently without interfering with each other. Fully backward
compatible with existing CLI commands.
**21 runtime tools** added covering process discovery, context/route/health
inspection, route control, message sending, tracing, expression evaluation, and
endpoint browsing.
--
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]
