modelcontextprotocol / modelcontextprotocol/inspector

MCP Server Interface Diff Tool

Open
#1,034 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement v2
Dominant language
TypeScript
Stars
10.9k
Forks
1.5k
Avg merge
6h 17m
Merged PRs (30d)
151

Description

Summary

@SamMorrowDrums has built an MCP server diff tool that compares the public interfaces of MCP servers from a client's perspective. He's proposing potential integration into the Inspector CLI as a sub-command.

The Tool

Image

Use Cases
  1. Catching regressions during refactors - Architecture refactors and SDK changes shouldn't cause schema diffs. This has caught mistakes in refactors and would have prevented a breaking client issue caused by an OpenAI strict mode regression (SDK upgrade removed a schema fix).

  2. Version comparison - See concrete schema differences between two versions of the same server, or what user-facing changes a fork has made.

  3. Cross-language consistency - Sam uses it to reduce diffs between 7 repos in different languages meant to provide the same server interface. Makes it easy to get agents to fix or reduce differences.

  4. SDK compliance testing - Interest expressed in using it with the everything server to clearly see client-facing changes for SDK compliance validation.

  5. PR review - Useful output for reviewing PRs that add tools or modify server interfaces.

  6. Toolset/mode validation - In GitHub MCP, used to check multiple toolsets and modes aren't accidentally impacted or changed.

Examples
Open Questions
  • Should this live as a separate project or be bundled into Inspector?
  • May be worth seeing adoption before considering bundling
  • May also be a plugin?
Additional Context

Discord threads:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Inspector CLI and the proposed mcp-server-diff repository, invoked with npx mcp-server-diff@latest. The issue leaves project placement, plugin versus sub-command design, and acceptance criteria open; done would require an agreed integration approach and verified interface-diff behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.