Compare Cli Mcp
Let your coding agent diff API or contract versions and block merges when specs drift from the approved baseline.
Overview
compare-cli-mcp is a MCP server for the Ship phase that exposes contract version diff, redline, and drift-gate checks as agent-callable tools.
What is this MCP server?
- Exposes compare-cli as MCP tools for version-to-version contract diff and redline output
- Drift gate tool to fail agent-driven workflows when live contracts diverge from locked versions
- stdio npm package (compare-cli-mcp) for local-first, agent-invoked checks
- Pairs with contract-ops suite workflows for end-to-end API contract hygiene
- No cloud dependency implied—runs through your registered MCP transport
- MCP server version 0.1.4
- stdio transport via npm identifier compare-cli-mcp
- Two primary capabilities: version diff/redline and drift gate
What problem does it solve?
Agents and fast iteration make it easy to silently change API contracts without a visible diff or a hard stop before you ship.
Who is it for?
Indie API and SaaS builders who want agent-driven refactors gated by explicit contract version comparison.
Skip if: Teams that only need informal README changelog notes and do not maintain versioned contract files.
What do I get? / Deliverables
Your agent can produce structured contract diffs and enforce a drift gate so incompatible spec changes surface before release.
- Structured diff or redline between two contract versions
- Drift-gate pass or fail signal for agent workflows
- Repeatable contract check without manual CLI copy-paste
Recommended MCP Servers
Journey fit
Contract redlines and drift gates belong on the path to release, where you catch breaking changes before users or partners do. Review is the canonical shelf for automated spec comparison and CI-style gates that complement human code review.
How it compares
MCP bridge to compare-cli, not a standalone OpenAPI editor or hosted contract registry.
Common Questions / FAQ
Who is compare-cli-mcp for?
Solo and small-team builders using AI coding agents who maintain versioned API or contract artifacts and want diff and drift checks inside the agent loop.
When should I use compare-cli-mcp?
Use it during Ship-phase review whenever you change specs, before merging agent-produced backend changes, or when validating that deployed contracts still match a locked baseline.
How do I add compare-cli-mcp to my agent?
Install the npm package compare-cli-mcp, add a stdio MCP server entry in Claude Code or Cursor pointing at that binary, then call the compare and drift-gate tools from your session.