[
https://issues.apache.org/jira/browse/CAMEL-24311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Mariani reassigned CAMEL-24311:
----------------------------------------
Assignee: Federico Mariani
> camel.server.mcp-* configuration properties and camel-main autowiring
> ---------------------------------------------------------------------
>
> Key: CAMEL-24311
> URL: https://issues.apache.org/jira/browse/CAMEL-24311
> Project: Camel
> Issue Type: Sub-task
> Components: camel-ai
> Reporter: Federico Mariani
> Assignee: Federico Mariani
> Priority: Major
> Labels: ai, mcp
>
> Add the {{camel.server.mcp-*}} configuration properties with camel-main
> autowiring so the server starts from properties alone (no route needed),
> consistent with the existing {{camel.server.*}} options in
> {{HttpServerConfigurationProperties}}.
> h3. Property ownership
> Properties are split by owner. *Bridge* properties control which tools exist
> and how they execute — they are honored identically on every runtime.
> *Engine* properties control serving — they are consumed by the default engine
> only; native engines (Quarkus) use their own configuration instead.
> ||Property||Owner||Default||On Quarkus (native engine)||
> |{{camel.server.mcp-enabled}}|bridge|false|honored — gates whether Camel
> publishes tools at all|
> |{{camel.server.mcp-tags}}|bridge|(none)|honored — tag selection is Camel
> domain|
> |{{camel.server.mcp-tool-timeout}}|bridge|20s|honored — execution is Camel
> domain|
> |{{camel.server.mcp-path}}|engine|/mcp|IGNORED — {{quarkus.mcp.server.*}}
> decides|
> |{{camel.server.mcp-server-name}}|engine|CamelContext name|passed via
> {{initialize()}} as a hint; native engines MAY ignore|
> h3. Precedence rule
> On runtimes with a native engine, the native configuration wins for serving
> concerns. To make this visible rather than a silent surprise: when an
> engine-owned property is set but the resolved engine does not consume it, log
> a WARN at startup naming the property and the native configuration to use
> instead.
> ----
> _This issue was drafted by Claude Code on behalf of Federico Mariani._
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
