[ 
https://issues.apache.org/jira/browse/CAMEL-24331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-24331 started by Federico Mariani.
------------------------------------------------
> camel-mcp-server-starter - Spring Boot engine over the Spring AI MCP server
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-24331
>                 URL: https://issues.apache.org/jira/browse/CAMEL-24331
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-spring-boot
>            Reporter: Federico Mariani
>            Assignee: Federico Mariani
>            Priority: Major
>
> Spring Boot runtime for CAMEL-24308: a {{camel-mcp-server-starter}} in the 
> camel-spring-boot repo providing an {{McpServerEngine}} over the Spring AI 
> 2.x MCP server ({{spring-ai-starter-mcp-server-webmvc}}, 
> {{spring.ai.mcp.server.protocol=STREAMABLE}}).
> * Depends on {{camel-mcp-server-api}} (bridge + SPI) — NOT the Vert.x engine 
> module; the MCP Java SDK arrives via Spring AI (2.x pins SDK 2.0.0, same as 
> camel).
> * {{SpringAiMcpServerEngine}}: {{toolAdded}}/{{toolRemoved}} map to the 
> auto-configured {{McpSyncServer}} bean's {{addTool}}/{{removeTool}} 
> ({{tools/list_changed}} emitted by the SDK). 
> {{consumesServingConfiguration()}} = false.
> * Auto-configuration with {{camel.mcp-server.*}} properties (enabled default 
> true — adding the starter is the opt-in; tags unset = no tools exposed; 
> tool-timeout 20s). Serving concerns (path, protocol, server identity, auth) 
> are owned by {{spring.ai.mcp.server.*}} per the CAMEL-24311 precedence rule.
> * Tests: auto-configuration conditions (ApplicationContextRunner) + a full 
> WebMVC {{@SpringBootTest}} running the engine conformance scenarios with the 
> official MCP SDK client (tag filtering, call success, sanitized errors, 
> timeout, list changes).
> ----
> _This issue was drafted by Claude Code on behalf of Federico Mariani._



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to