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

   ## Summary
   
   - Add `camel mcp` CLI subcommand as a new plugin (`camel-jbang-plugin-mcp`) 
that launches the Camel MCP server
   - Supports options: `--http`, `--port`, `--log-level`, `--version`
   - Restructure `camel-jbang-mcp.adoc` documentation: expanded intro, Getting 
Started, `java -jar` usage, setup/examples before tool reference tables
   
   ## Details
   
   The MCP server currently requires users to know the JBang GAV coordinates 
(`jbang org.apache.camel:camel-jbang-mcp:LATEST:runner`). This PR makes it a 
first-class CLI citizen:
   
   ```bash
   camel mcp                          # STDIO transport (default)
   camel mcp --http                   # HTTP/SSE transport
   camel mcp --http --port 9090       # Custom HTTP port
   camel mcp --log-level DEBUG        # Debug logging
   ```
   
   The plugin JAR is only 12KB (2 Java classes + service file) — it launches 
the MCP server as a JBang subprocess with inherited IO. No Quarkus dependencies 
in the plugin itself.
   
   Documentation restructured to be more user-friendly:
   1. Expanded introduction explaining what MCP is and what the server does
   2. Getting Started (3 steps)
   3. Running options: `camel mcp`, `jbang`, `java -jar` (no JBang needed)
   4. Setup/configuration moved up
   5. Tool reference tables moved to bottom
   
   ## Test plan
   
   - [x] `camel mcp --help` shows all options correctly
   - [x] Plugin appears in `camel --help` under "Other"
   - [x] Module builds successfully (`mvn install -DskipTests`)
   - [x] Service file generated correctly
   - [x] Unit tests pass (`camel-jbang-core`)
   - [ ] CI build passes
   
   _Claude Code on behalf of Claus Ibsen_
   
   Co-Authored-By: Claude Opus 4.6 <[email protected]>


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