René's URL Explorer Experiment

Title: test: interaction-model end-to-end suite with a requirements manifest by maxisbey · Pull Request #2691 · modelcontextprotocol/python-sdk · GitHub

Open Graph Title: test: interaction-model end-to-end suite with a requirements manifest by maxisbey · Pull Request #2691 · modelcontextprotocol/python-sdk

X Title: test: interaction-model end-to-end suite with a requirements manifest by maxisbey · Pull Request #2691 · modelcontextprotocol/python-sdk

Description: Adds tests/interaction/: an end-to-end suite that enumerates the MCP interaction model — one test per behaviour, asserting full client↔server round trips through the public API only — backed by a requirements manifest that maps every behaviour the SDK must satisfy to the spec section that mandates it, the tests that prove it, and the gaps that remain. Where to look tests/interaction/README.md — the conventions, the manifest model, the divergence lifecycle, and the transport matrix. Read this first. tests/interaction/_requirements.py — the manifest itself: 360 entries, each with a spec link, the required behaviour, and (where the SDK falls short) a structured divergence or deferred note. The 50 divergences are the SDK's spec-compliance gap report; the 61 deferred entries are the feature backlog. src/ — almost entirely coverage-pragma adjustments (removals where the new tests now reach the line, narrowings where a removed block-level pragma exposed a still-uncovered branch). The one behaviour change is in src/mcp/server/sse.py: connect_sse now closes sse_stream_reader after EventSourceResponse returns, fixing a resource leak the in-process SSE tests surfaced. tests/interaction/transports/_bridge.py — the in-process streaming ASGI transport that lets the suite drive the real streamable-HTTP and SSE apps with no sockets. tests/interaction/_connect.py — the connection factories and the connect fixture that runs every transport-agnostic test over in-memory, streamable HTTP, and SSE. tests/interaction/auth/_provider.py / _harness.py — the in-process authorization-server provider and OAuth harness. Motivation and Context Two purposes: A parity bar for internal rewrites of the send/receive path. The suite pins the SDK's current observable behaviour exactly, so before/after runs against the same suite prove the rewrite equivalent. Tests never xfail; where current behaviour falls short of the spec, the test pins the divergent output and the gap is recorded as data on the manifest entry. A complete, queryable ledger of the SDK's behaviour surface against the 2025-11-25 spec. The manifest tracks the full requirements surface — including behaviours the SDK has not implemented, each with a precise reason and a slot for a tracking issue. The ID vocabulary is aligned with the TypeScript SDK's end-to-end requirements suite so coverage and gaps can be compared across the two SDKs entry by entry. What's covered 529 tests across 360 tracked requirements: Every protocol feature: tools, resources, prompts, completion, logging, sampling, elicitation, roots, ping, progress, cancellation, pagination, timeouts, _meta, lifecycle and version negotiation, list-changed notifications, wire-level invariants. Transports: every transport-agnostic test runs over the in-memory transport, the real streamable HTTP app, and the legacy SSE transport — all in-process via the streaming ASGI bridge — plus a single SDK-client↔SDK-server stdio subprocess test. Transport-specific tests cover session management, resumability and Last-Event-ID replay, the GET-stream routing rules, stateless mode, origin validation, and stdio framing. OAuth: the full authorization-code flow against an in-process authorization server (discovery, PRM, DCR, PKCE, state, the resource parameter), the bearer middleware error plane, transparent refresh, step-up on 403, CIMD, and the M2M extension providers. Composed flows: resource-link follow-through, multi-step elicitation chains, terminate-then-reconnect, dual-transport servers. How Has This Been Tested? uv run --frozen pytest tests/interaction/ — fully in-process and event-driven (no sockets, threads, or sleeps, with one subprocess for stdio); runs in ~10 s. 100% line and branch coverage including the test code itself. Breaking Changes None — tests and test-support only. Types of changes Test/infrastructure addition Checklist I have read the MCP Documentation My code follows the repository's style guidelines New and existing tests pass locally I have added appropriate error handling I have added or updated documentation as needed (tests/interaction/README.md) Additional context Known SDK gaps surfaced while writing the suite will be filed as issues separately and linked from the manifest entries' issue fields. AI Disclaimer

Open Graph Description: Adds tests/interaction/: an end-to-end suite that enumerates the MCP interaction model — one test per behaviour, asserting full client↔server round trips through the public API only — backed by a r...

X Description: Adds tests/interaction/: an end-to-end suite that enumerates the MCP interaction model — one test per behaviour, asserting full client↔server round trips through the public API only — backed by a r...

Opengraph URL: https://github.com/modelcontextprotocol/python-sdk/pull/2691

X: @github

direct link

Domain: github.com

Links:

Viewport: width=device-width