Skip to content

fix(conformance): use discover lifecycle for 2026 clients - #1013

Closed
0xzr wants to merge 1 commit into
modelcontextprotocol:mainfrom
0xzr:fix/conformance-client-draft-lifecycle
Closed

fix(conformance): use discover lifecycle for 2026 clients#1013
0xzr wants to merge 1 commit into
modelcontextprotocol:mainfrom
0xzr:fix/conformance-client-draft-lifecycle

Conversation

@0xzr

@0xzr 0xzr commented Jul 19, 2026

Copy link
Copy Markdown

Summary

  • select the conformance client lifecycle from the runner's protocol version, using discovery for 2026-07-28 while preserving initialization for legacy runners
  • exercise the discovery lifecycle in the affected tools, scope step-up, and standard-header scenarios
  • request the initial mcp:basic scope required by the draft scope step-up server
  • run the three affected draft scenarios in the conformance workflow

Closes #1002

Testing

  • cargo test -p mcp-conformance --bin conformance-client (3 passed)
  • 2025-11-25 client suite with conformance 0.1.16 (222/222 checks passed)
  • 2026-07-28 tools_call with conformance 0.2.0-alpha.9 (1/1 check passed)
  • 2026-07-28 auth/scope-step-up with conformance 0.2.0-alpha.9 (30/30 checks passed)
  • 2026-07-28 http-standard-headers with conformance 0.2.0-alpha.9 (3/3 applicable checks passed)

@0xzr
0xzr requested a review from a team as a code owner July 19, 2026 22:59
@github-actions github-actions Bot added T-CI Changes to CI/CD workflows and configuration T-config Configuration file changes labels Jul 19, 2026

@alexhancock alexhancock left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you look into the merge conflicts?

--spec-version draft \
-o conformance-client-results/sep-2575

- name: Run draft lifecycle client scenarios

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We're going to make a change shortly where we run the whole client suite

https://github.com/modelcontextprotocol/rust-sdk/pull/1010/changes#diff-e5ed24bc2f5084a1664419e35473c15466f87e7552ef1fad4d13cdde0eaed400

Mind backing this part out of the change and just doing the .rs changes?

@alexhancock

Copy link
Copy Markdown
Contributor

Given no reply on the feedback above I made some related changes in #1022

Thanks for finding this originally!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2026-07-28 T-CI Changes to CI/CD workflows and configuration T-config Configuration file changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Conformance client: legacy-lifecycle scenarios fail with -32020 missing MCP-Protocol-Version header at 2026-07-28

3 participants