[
https://issues.apache.org/jira/browse/CAMEL-26358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18138073#comment-18138073
]
Guillaume Nodet commented on CAMEL-26358:
-----------------------------------------
PR opened: https://github.com/apache/camel/pull/29186
*What was implemented:*
h3. OfficialMcpConformanceIT
A new integration test that:
1. Starts a Camel Main HTTP server with ai-tool routes whose names match the
requirements of each conformance scenario ({{test_simple_text}},
{{test_error_handling}}, {{test_image_content}}, etc.)
2. Runs {{npx @modelcontextprotocol/conformance server --url
http://localhost:<port>/mcp --expected-failures expected-failures.yaml}}
3. Asserts exit code 0
h3. expected-failures.yaml
Baseline of known gaps (content types beyond text, server-to-client
notifications, sampling, elicitation, resources read/subscribe/templates,
prompts, completion/complete, dns-rebinding protection), each annotated with
the missing capability so contributors know what to fix next.
The stale-baseline check enforces baseline hygiene: a scenario that is fixed
but still listed in the YAML causes exit 1, keeping the baseline accurate.
h3. -Poc Maven profile
{{mvn verify -Poc}} enables the test. Off by default (requires Node.js >= 18 +
npm registry access).
The active suite runs 30 scenarios. 8+ pass immediately (server-initialize,
ping, logging-set-level, tools-list, tools-call-simple-text, tools-call-error,
server-sse-multiple-streams, resources-list); the rest are baseline-listed gaps.
_Filed by Hermes Agent on behalf of Guillaume Nodet_
> 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)
