Api Changelog Tracker
Let your coding agent watch third-party API changelog feeds so you catch deprecations before a production integration breaks.
Overview
api-changelog-tracker is a MCP server for the Operate phase that lets agents track third-party API changelog updates over streamable-http.
What is this MCP server?
- Remote MCP server on Cloudflare Workers with streamable-http transport at api.lazy-mac.com
- Agent-callable workflow for surfacing API version and changelog signals without leaving Claude Code or Cursor
- Pairs naturally with contract validation and diff monitoring in a lazy-mac API tooling stack
- Suited to SaaS and agent products that integrate many vendor REST or GraphQL APIs
- Version 1.0.0 server schema aligned with Model Context Protocol 2025-09-29
- Server version 1.0.0 per Model Context Protocol server schema 2025-09-29
- Single streamable-http remote endpoint on Cloudflare Workers
- Published repository: github.com/lazymac2x/api-changelog-tracker-api
What problem does it solve?
Vendor APIs change silently and solo builders only notice breaking changelog entries after deploys fail.
Who is it for?
Indie SaaS founders maintaining multiple external API integrations who want agent-driven changelog awareness without bespoke scrapers.
Skip if: Teams that only consume internal APIs with no public changelog or teams needing full OpenAPI diff engines in CI only.
What do I get? / Deliverables
Your agent can query changelog-tracking tools so you plan upgrades and communicate risk before you merge dependency bumps.
- Registered remote MCP connection in your agent config
- Agent-invokable changelog lookup workflow for targeted APIs
- Actionable notes for upgrade or pin decisions before merge
Recommended MCP Servers
Journey fit
Ongoing API dependency hygiene sits in Operate monitoring, where solo builders maintain what they already shipped. Changelog tracking is observability for external contracts—not feature work—so monitoring is the canonical shelf.
How it compares
Hosted MCP integration for changelog awareness, not an agent skill or a local CLI changelog parser.
Common Questions / FAQ
Who is api-changelog-tracker for?
Solo builders and small teams shipping products that rely on third-party APIs and want their Claude Code, Cursor, or Codex agent to monitor vendor change logs.
When should I use api-changelog-tracker?
Use it during operate monitoring and pre-release checks when you need to know if a dependency’s changelog implies a breaking change before you ship.
How do I add api-changelog-tracker to my agent?
Add the remote MCP URL https://api.lazy-mac.com/api-changelog-tracker/mcp with type streamable-http in your agent’s MCP server configuration, then restart the session.