Use oasdiff from your AI assistant
oasdiff runs as an MCP server, so Claude, Cursor, and other AI assistants can call it directly. Ask “does this change break the API?” and your assistant runs oasdiff on the two specs.
The server
It's a hosted, remote server over the Streamable HTTP transport. No install, no API key.
https://api.oasdiff.com/mcpConnect
Claude Code
claude mcp add --transport http oasdiff https://api.oasdiff.com/mcpCursor — add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project)
{
"mcpServers": {
"oasdiff": {
"url": "https://api.oasdiff.com/mcp"
}
}
}Other clients (Windsurf, VS Code, etc.)
Any MCP client that speaks Streamable HTTP works: point it at https://api.oasdiff.com/mcp. Most use the same mcpServers object shown above for Cursor.
Tools
You pass the OpenAPI specs as text (YAML or JSON), and your assistant gets a readable report back. Specs must be self-contained — external $ref URLs are not resolved.
oasdiff_breaking_changes— breaking and warning-level changes between a base and a revisionoasdiff_changelog— the full changelog, down to informational changesoasdiff_diff— the structural diffoasdiff_validate— validate a single spec against the OpenAPI and JSON Schema rules
Try it
Once connected, ask your assistant something like:
“Compare these two OpenAPI specs and tell me if anything breaks existing clients.”
Prefer the browser? The diff tool runs the same checks, no setup.