Multi-server composition demo (v0.6.0) - #4
Merged
Conversation
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
1 participant
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.
Summary
Companion to mcp-contracts/mcp-contracts#55 (v0.6.0 — Multi-Server & Composition).
notes-server.js, a second MCP server that deliberately exposes asearch_contactstool with a different schema than the contacts server — a conflicting tool name collision formcpdiff check-conflictsto catch.mcp.jsondefining the two-server composition.contracts/composition/baselines captured viamcpdiff snapshot --config mcp.json --all.Used to verify the v0.6.0 CLI end-to-end: clean composition diff (exit 0), breaking-drift and config-rename scenarios (exit 1 with hints), collision detection (exit 1), and graph rendering in terminal/mermaid.