Claus Ibsen created CAMEL-26360:
-----------------------------------
Summary: camel-mcp-server - Spring Boot and Quarkus engines: catch
up with the Camel Main engine
Key: CAMEL-26360
URL: https://issues.apache.org/jira/browse/CAMEL-26360
Project: Camel
Issue Type: Improvement
Components: camel-quarkus, camel-mcp-server,
camel-spring-boot-starters
Reporter: Claus Ibsen
Fix For: 4.24.0
The Camel Main engine is the reference. The Spring Boot (Spring AI MCP server)
and Quarkus (quarkus-mcp-server) engines lag behind:
* *Resources:* neither serves {{ai-resource}} routes; only a WARN is logged.
* *Structured output:* the Spring Boot engine drops {{outputSchema}} and
{{structuredContent}}, so its tool results are text only.
* *Caller identity:* neither engine passes a {{McpToolCallContext}}, so a tool
route's {{AuthorizationPolicy}} can't see the caller.
Then, as the Camel Main features land, both engines follow:
* resource templates, CAMEL-26354 ({{McpSyncServer.addResourceTemplate}} /
{{ResourceTemplateManager}});
* prompts, CAMEL-26355 ({{addPrompt}} / {{PromptManager}});
* caller identity from Spring's {{SecurityContext}} or Quarkus'
{{SecurityIdentity}}, CAMEL-26356;
* a docs page showing the native OAuth setup: Spring Security's protected
resource metadata, and {{quarkus.oidc.resource-metadata.*}};
* the {{Origin}} validation of CAMEL-26359: check what the Spring AI MCP server
and quarkus-mcp-server already do, and document or add the same rule.
This ticket tracks parity and does not block the Camel Main work. The Quarkus
work goes in a linked camel-quarkus GitHub issue.
_Filed by Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
