Federico Mariani created CAMEL-27174:
----------------------------------------
Summary: camel-mcp-server-starter - serve MCP protocol version
2026-07-28 once Spring AI 2.1.0 is GA
Key: CAMEL-27174
URL: https://issues.apache.org/jira/browse/CAMEL-27174
Project: Camel
Issue Type: Improvement
Components: camel-spring-boot-starters
Reporter: Federico Mariani
The Camel Spring Boot MCP server starter registers Camel {{ai-tool}},
{{ai-resource}} and {{ai-prompt}} routes on the {{McpSyncServer}} that Spring
AI auto-configures, so it serves only the MCP protocol versions that open with
an {{initialize}} handshake (2025-11-25 and earlier).
Spring AI 2.1.0 (2.1.0-RC2 at the time of writing, not GA yet) adds
{{spring.ai.mcp.server.protocol=MODERN}}, the stateless MCP protocol version
2026-07-28, built on the {{io.modelcontextprotocol.modern}} server of the MCP
Java SDK 2.2.0. That server takes its tools, resources and prompts from
repositories ({{McpSyncToolRepository}}, {{McpSyncResourceRepository}},
{{McpSyncPromptRepository}}) instead of an {{McpSyncServer}}, so the starter
needs:
* an {{McpServerEngine}} for {{MODERN}} that fills those repositories as routes
start and stop, and broadcasts list changes for {{subscriptions/listen}} (the
Camel Main engine does the same in {{McpModernCatalog}}, CAMEL-27145);
* the caller identity (principal, OAuth) carried from the request into the
tool-call context;
* tests with the MCP Java SDK client for 2026-07-28, and the starter
documentation.
Spring AI serves one protocol per application: with {{MODERN}}, clients that
open with {{initialize}} are not served. The documentation should say so, as
Camel Main's {{camel.server.mcp-protocol-era=dual}} serves both.
Blocked until Spring AI 2.1.0 is released and {{spring-ai-version}} is upgraded
in the Camel parent.
_Claude Code on behalf of Croway_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)