davsclaus opened a new pull request, #23730:
URL: https://github.com/apache/camel/pull/23730

   ## Summary
   
   Adds 6 new runtime MCP tools to the standalone camel-jbang-mcp server, 
exposing CLI capabilities that were previously not available via MCP:
   
   - **`camel_runtime_route_topology`** — Inter-route topology graph with 
optional metrics and external endpoint nodes (action IPC: `route-topology`)
   - **`camel_runtime_errors`** — Captured routing errors from ErrorRegistry 
with exchange context (reads `{pid}-error.json`)
   - **`camel_runtime_thread_dump`** — JVM thread dump with thread names, 
states, and stack traces (action IPC: `thread-dump`)
   - **`camel_runtime_history`** — Last completed exchange trace, always 
captured without enabling tracing (reads `{pid}-history.json`)
   - **`camel_runtime_stop`** — Graceful shutdown via PID file deletion (uses 
existing `RuntimeHelper.stopApplication`)
   - **`camel_runtime_receive`** — Poll/receive a message from an endpoint, 
complement to existing `camel_runtime_send` (action IPC: `receive`)
   
   Also adds `readErrorFile()` and `readHistoryFile()` helper methods to 
`RuntimeHelper` and `RuntimeService` following the existing `readStatus()` 
pattern.
   
   ## Test plan
   
   - [ ] Build succeeds: `cd dsl/camel-jbang/camel-jbang-mcp && mvn install 
-DskipTests`
   - [ ] Full reactor build succeeds: `mvn clean install -DskipTests`
   - [ ] `camel_runtime_route_topology` returns nodes/edges for running 
integration
   - [ ] `camel_runtime_errors` returns error data (or empty array when no 
errors)
   - [ ] `camel_runtime_thread_dump` returns thread list
   - [ ] `camel_runtime_history` returns last exchange trace
   - [ ] `camel_runtime_stop` triggers graceful shutdown
   - [ ] `camel_runtime_receive` polls message from endpoint
   
   _Claude Code on behalf of Claus Ibsen_


-- 
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]

Reply via email to