Repository navigation
feat: add scenario requires metadata and --production server mode - #587
Draft
sebastienrousseau wants to merge 1 commit into
Draft
sebastienrousseau wants to merge 1 commit into
sebastienrousseau wants to merge 1 commit into
Conversation
Add declarative ScenarioRequirements metadata on ClientScenario to distinguish optional MCP server capabilities and extensions from everything-server reference fixtures, and gate SEP-2549 caching probes on declared capabilities while keeping emitted check IDs stable. Introduce an opt-in --production flag on the server command that skips unmet capability, extension, and fixture requirements with structured SKIPPED details while keeping default SDK conformance strict. Closes modelcontextprotocol#516 Assisted-by: Antigravity:Claude-Opus-4.6 [tsgo,eslint,prettier,vitest] Signed-off-by: Sebastien Rousseau <[email protected]>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi @olaservo,
This PR adds declarative scenario requirements metadata and an opt-in
--productionserver conformance mode.Capability-partial production servers now run all applicable protocol checks and report undeclared capabilities or reference-fixture contracts as
SKIPPED, while default SDK conformance stays strict.Highlights ⭐️
ScenarioRequirements(capabilities,anyCapability,extensions, andfixture) toClientScenarioacross the 64 server scenarios, separating optional MCP capabilities fromeverything-serverreference-fixture contracts (test_*tools/prompts andtest://resources).--productionServer Mode: Evaluatesscenario.requiresagainst capabilities discovered frominitialize(2025-x) orserver/discover(2026-07-28), emitting structuredSKIPPEDchecks (skippedReason: 'missing-capability' | 'missing-extension' | 'requires-fixture') without relaxing default SDK conformance (#248,#372) or masking broken capability handlers and unreachable servers.CachingScenarioto inspect declared capabilities viaconn.discover()so servers advertising a subset oftools,prompts, orresourcesonly receive probes for declared endpoints while keeping all seven SEP-2549 check IDs stable for traceability.What's Changed
Validation
npm run check: 0 TypeScript errors (tsgo --noEmit), 0 ESLint findings, Prettier clean across all files.npm run build: Builtdist/index.js(885.81 kB) in 147ms with 0 warnings.npm test: 50/50 test files passed, 664/664 tests passed (including 23 new unit, runner, and CLI--productionintegration tests across stateful 2025-11-25 and stateless 2026-07-28 servers).Checksums
Closes #516
Full Changelog: main...sebastienrousseau:feat/scenario-requires-production-mode