API Change Watch

A structured feed of breaking changes and deprecations across major API providers, built for humans and coding agents.
Currently tracking: anthropic, aws, firebase, github, google, openai, shopify, slack, stripe, twilio.

Use from a coding agent (MCP)

Point your agent at the Streamable HTTP endpoint and it can query this feed directly — tools: list_breaking_changes (filter by provider / severity / date) and list_providers. The endpoint is https://apichangewatch.dev/mcp — any MCP client that speaks Streamable HTTP works, no auth required.

Claude Code

claude mcp add --transport http api-change-watch https://apichangewatch.dev/mcp

Cursor — .cursor/mcp.json

{ "mcpServers": { "api-change-watch": { "url": "https://apichangewatch.dev/mcp" } } }

VS Code (Copilot) — .vscode/mcp.json

{ "servers": { "api-change-watch": { "type": "http", "url": "https://apichangewatch.dev/mcp" } } }

Other clients (Codex CLI, Gemini CLI, Windsurf, …) — add a remote / Streamable HTTP MCP server pointing at https://apichangewatch.dev/mcp in your client's MCP settings.

Then try asking your agent:

• "Do any APIs this repo depends on have upcoming breaking changes?"
• "List breaking changes for stripe since 2026-01-01."
• "Which providers does this feed track?"

Agents can also read /llms.txt for a machine-readable overview.

Automate it

Combine this with your agent's scheduled runs (Claude Code routines, CI cron, etc.) and the check becomes fully hands-off — you only hear about it when something is actually affected. Example weekly prompt:

Call list_breaking_changes for the providers this repo depends on,
check the codebase for affected usage, and open a GitHub issue
(with file:line references) if anything is affected. If nothing is, do nothing.

Sorted by deadline proximity — upcoming effective dates first (red = within 30 days), then recently effective, then undated.