Developer builds MCP server to stop AI coding agents from shipping breaking API changes
A developer built an open-source MCP server called specshield-mcp-server after witnessing an AI coding agent silently break a mobile client and partner integration by renaming an API field without flagging the consequences. AI agents like Cursor lack awareness of API contracts, meaning they can remove endpoints or alter response fields while tests still pass, leaving downstream consumers to discover breakage in production. The MCP server gives agents a tool called is_change_safe, which compares old and new OpenAPI specs and returns a verdict, risk level, and specific breaking reasons before any commit is made. Additional read-only tools cover plain-language impact explanations, migration guides, release notes, and raw spec diffs. The package is available on npm and the official MCP registry and requires an API key to connect to the backend analysis service.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in