We built a free MCP server that tells your AI agent what changed

AI coding agents answer from training data, and training data goes stale. Platforms keep shipping breaking changes in the meantime: a new major SDK version, a removed API, a new store requirement. An agent that doesn’t know about them will confidently write code that calls something that no longer exists.

So we built the Platform Changes MCP server: a free, remote MCP server that gives an agent a live, sourced feed of what has changed, so it can check before it answers.

What it covers

It watches 14 official sources and serves what it finds, with a source link and date on every item. Eight are feeds:

• Apple Developer News
• Android Developers Blog
• GitHub Changelog
• Vercel Changelog
• Cloudflare Changelog
• Expo
• Supabase
• The Firebase JS SDK releases

The other six are policy pages that have no feed, so we compare each page with the last version we saw:

• Google Play policy announcements
• Google Play policy deadlines
• Google Play policy archive
• Google Play Developer Program Policy
• Apple App Review Guidelines
• Apple upcoming requirements

For a policy page you get an item summarising what was added or removed. It’s dated when we noticed the change, not when the vendor made it. If a vendor edits an old post, the item is flagged as revised.

Feeds are polled hourly and the policy pages every six hours. It’s remote, so there’s nothing to install, and it needs no API key.

The tools it gives your agent

• weekly_digest: a ranked overview per platform. This is the best first call.
• recent_changes: the newest changes, filterable by platform, tag, minimum importance and number of days, or sorted by last update to catch posts a vendor has edited.
• search_changes: text search across everything it has collected.
• get_change: the full record for a single change.
• list_sources: which platforms are monitored, when each was last polled and how many items it holds.

How to connect it

In Claude Code:

claude mcp add --transport http platform-changes https://changes.bromputers.co.uk/mcp

We’ve tested it in a real Claude Code session and with the official MCP Python SDK client. We haven’t tested it in Cursor, Windsurf, VS Code or Claude Desktop, so if you try it there, tell us how it goes. It’s also listed in the official MCP registry as io.github.Oprych22/platform-changes.

What it isn’t

We’d rather be upfront about the limits:

• Fourteen sources, and only those. The policy pages are watched by comparing their text, so a page that needs JavaScript to render can’t be watched this way, and a change is dated when we noticed it.
• Importance is rated by an AI model (Claude Haiku 4.5 on Amazon Bedrock), with a one-line reason for each item. It replaced my original keyword rules after disagreeing with them on about half of a 52-item sample, usually correctly. It can still be wrong, and anything it has not rated yet falls back to the keyword rules.
• Tags are heuristic too, not verified.
• It’s an experiment. It’s free, and we’ll only consider anything paid if people actually use it.

Why we built it

It started as a cheap way to find out whether developers and their agents would use a live feed of platform changes at all. Every tool call is logged, so we can see whether it’s being used. We’re alerted if the endpoint stops answering, the data goes stale, or a source fails to fetch for about six hours, though nothing here is a guarantee: it’s a free experiment. We’d like to hear which platforms or sources would make it useful to you, and whether the digest ranks things sensibly.

You can find the landing page, which refreshes hourly with recent changes, at changes.bromputers.co.uk. If you build tools like this for your own business, or want something built, get in touch.