
schema-mcp
JSON Schema toolkit: version diff with breaking-change classification, draft-07/2020-12 validation
- tools
- 2
- transport
- STDIO
- last updated
- Nov 16, 2026
Tools
2 toolsPublic tool metadata for what this MCP can expose to an agent.
schema_diffTwo schema versions in → classified change list out, with each entry carrying a path, kind, severity (breaking, non_breaking, not_supported), description, and old/new values.
Two schema versions in → classified change list out, with each entry carrying a path, kind, severity (breaking, non_breaking, not_supported), description, and old/new values.
No parameter schema in public metadata yet.
schema_validateValidate an instance document against a schema (draft-07 or 2020-12, auto-detected from $schema).
Validate an instance document against a schema (draft-07 or 2020-12, auto-detected from $schema).
No parameter schema in public metadata yet.
Sponsors
Readme
schema-diff-tools
Deterministic JSON Schema tools for agents and humans: path-level diff + breaking-change classification + instance validation, as an npm engine (@nopilot/schema-diff-engine) plus a local-first MCP server (@nopilot/schema-mcp).
Why not just "ask the model"? LLMs are famously unreliable at "is this schema change backwards-compatible?" — they miss nested required additions and misjudge type narrowing. This engine answers deterministically: same input → byte-identical output, every time.
The local-first difference
The npm side proves the demand (json-schema-diff: ~270k weekly downloads); the MCP side is nearly empty — the closest existing server sees ~36 weekly visitors and validates single schemas only. Most hosted API-diff services upload your schemas to their gateway. Proprietary API contracts should not take that trip.
schema-mcp runs entirely on your machine:
Details
- Repository
- github.com/latbert/schema-diff-tools
- Website
- github.com/latbert/schema-diff-tools
- Category
- Data & Analytics
- Package
@nopilot/schema-mcp- Transport
- STDIO
- Registry
- MCP registry, active