[
https://issues.apache.org/jira/browse/CAMEL-26358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18138055#comment-18138055
]
Guillaume Nodet commented on CAMEL-26358:
-----------------------------------------
This issue is being investigated by a coding agent (on behalf of gnodet).
Triage analysis: The existing conformance tests in camel-mcp-server use Camel's
own internal engine conformance kit (MCP Java SDK client) to verify that
different Camel MCP engine implementations behave identically. No integration
with the official @modelcontextprotocol/conformance npm suite exists yet. The
official suite (via npx) supports a --expected-failures YAML baseline, matching
the "knowingly skip" requirement. Feasible in a single PR: one new IT class
(OfficialMcpConformanceIT), one baseline YAML, and a Maven profile gate since
Node.js is required.
_Note: This comment was generated by an AI coding agent and requires manual
verification._
> camel-mcp-server - run the official MCP conformance suite against the Camel
> Main engine
> ---------------------------------------------------------------------------------------
>
> Key: CAMEL-26358
> URL: https://issues.apache.org/jira/browse/CAMEL-26358
> Project: Camel
> Issue Type: Test
> Components: camel-mcp-server
> Reporter: Claus Ibsen
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 4.24.0
>
>
> Our conformance kit checks that the engines behave the same as each other. It
> does not check that they match the MCP spec.
> The official MCP conformance suite (Node.js, {{npx}}) can run against a Camel
> Main server with test routes, with a baseline file for the checks we
> knowingly skip. Since the standalone server is the reference implementation,
> a clean run of the suite should be a release goal.
> It would run behind an opt-in property or the {{-Pit}} profile, because it
> needs Node.js and network access.
> _Filed by Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
