atiaomar1978-hub commented on PR #25203: URL: https://github.com/apache/camel/pull/25203#issuecomment-5148563759
_AI-generated reply on behalf of [atiaomar1978-hub](https://github.com/atiaomar1978-hub) — no code changes in this update._ Thanks @jamesnetherton — fair point, and I agree we should **not rush this to merge** without aligning on the broader design first. To answer your question directly: **most of the JIRA “notes” questions are not fully resolved in this PR.** This changeset is intentionally a narrow, dev-oriented slice: | JIRA design question | Addressed in this PR? | |----------------------|----------------------| | Embedded MCP for Spring Boot / Quarkus / standalone (not just CLI) | **Partially.** Camel Main gets the plumbing (`camel.mcp.*`, management HTTP endpoint, `EmbeddedMcpRequestHandler` SPI). Standalone Main can enable it via properties, but **only if a handler is registered on the registry**. JBang wires `JbangEmbeddedMcpRequestHandler` for `--mcp`. **No Spring Boot or Camel Quarkus integration** — Quarkus should use [quarkus-mcp-server](https://github.com/quarkiverse/quarkus-mcp-server) as you noted; that analysis is still TODO. | | Relation to standalone MCP ([CAMEL-23852](https://issues.apache.org/jira/browse/CAMEL-23852)) | **Not designed end-to-end here.** Standalone remains the Quarkus-based `camel mcp` server (catalog + tooling). Embedded is a lightweight Streamable HTTP JSON-RPC endpoint on the **management server** for local dev (`--mcp` / `camel.mcp.enabled`). Overlap and long-term consolidation need a design doc. | | Which tools — catalog, runtime introspection, or both? | **JBang path only:** exposes existing `ToolRegistry` tools (same family as CLI AI/MCP tooling — catalog lookup, route validation, runtime introspection against the local process). Not a general “expose any Camel app’s routes as tools” story. | | Routes automatically become MCP tools? | **No.** No route metadata / service-catalog opt-in in this PR. | | Relation to Wanaku | **Not addressed.** | So this PR is best seen as **plumbing + JBang dev flag**, not the full CAMEL-23853 vision from the ticket description. Happy to **pause merge**, open a short design discussion (possibly linked to @Croway’s [CAMEL-24308](https://issues.apache.org/jira/browse/CAMEL-24308)), and clarify boundaries with Quarkus/Spring Boot before we call it done. Let me know whether you’d prefer this PR **closed and redesigned**, **converted to draft** pending CAMEL-24308 alignment, or **scoped down further** (e.g. JBang-only behind `--mcp` without the `camel.mcp.*` Main surface) — I’ll follow your lead. -- 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]
