changelogs

Every vendor publishes release notes somewhere different.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • List Products: The products What's New tracks release notes for, with slugs, categories and platforms. Filter by category and/or a name query.
  • Search Releases: Full-catalog search across product names and release history. Returns matching products and releases with permalinks.
  • Whats New: A product's newest releases with notes. Pass since_version (the version you run) to get only what shipped after it, with per-category change counts.

What data it sees

Do you need an account

No: the server works without sign-in

Every vendor publishes release notes somewhere different. A GitHub release, a Steam patch note, a console firmware page, an IDE changelog nobody links to. What's New reads all of them and stores what it finds in one shape. Four read-only tools open that catalog to an agent: list_products and search_releases do what they sound like, whats_new takes the version you actually run and answers with only what shipped after it, and upgrade_notes takes the dependencies you are upgrading, from npm to Maven, and answers per package with the vendor's own breaking-change and migration sections — the ones a minor version number never announced. There is no key and no sign-in: point a client at https://whatsnew.fyi/mcp and start asking. Every entry keeps the provenance labels the site shows and links to the vendor's own notes, which are still the authoritative copy.

How to connect

How to connect changelogs to Claude

The server address to paste into Claude settings:

https://changelogs--whatsnew.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect changelogs to ChatGPT

The server address to paste into ChatGPT settings:

https://changelogs--whatsnew.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect changelogs to Cursor

The server address to paste into Cursor settings:

https://changelogs--whatsnew.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (5)

Raw names from tools/list. Only developers need these.

list_productsThe products What's New tracks release notes for, with slugs, categories and platforms. Filter by category and/or a name query.
search_releasesFull-catalog search across product names and release history. Returns matching products and releases with permalinks.
whats_newA product's newest releases with notes. Pass since_version (the version you run) to get only what shipped after it, with per-category change counts.
upgrade_notesBefore or after upgrading dependencies — package.json / lockfile / requirements changes, npm update, pip install -U, a Gradle version catalog, go.mod, a workflow's actions — pass each package with the version you run and the version you are moving to. Returns every tracked release in between with the vendor's own breaking-change, deprecation, migration and security sections verbatim, the categorized change list, CVE ids and deterministic signals (major bump, removed/deprecated items, breaking mentions) — including breaking changes shipped in minor or patch versions. Pass repository (from the package's own package.json) for scoped or renamed packages; it makes the match exact. A Maven/Gradle, Go, NuGet or GitHub Actions package goes by its purl (e.g. pkg:maven/com.squareup.okhttp3/okhttp), or by its own coordinate as the name (group:artifact, a module path, owner/repo@ref), and is matched exactly or not at all. A Maven, Go or NuGet package this server does not track is checked against deps.dev after the answer and counted, to decide what to track next; pass recordMisses: false for private packages.
missing_changesFor a whole project's outdated report — npm/pnpm outdated --json (current → from, wanted, latest), ncu --format installedVersion, pip or uv pip list --outdated --format json (version → from, latest_version → latest), go list -m -u -json all (Version → from, Update.Version → latest), cargo outdated, dotnet list package --outdated, a Gradle versions report — pass each package with the version installed and, where the tool gives them, wanted and latest. Answers what the project is missing, most exposed first: per package, the security releases, CVE ids and fixes it does not have, split into toWanted (from → wanted: reachable by an update within the declared range, no manifest edit) and toLatest (→ latest: needs the range changed), with the cost of moving beside them (major bump, breaking mentions, removed/deprecated) and a few of the fixes themselves. Counts are deterministic over every tracked release; no model judged anything. Up to 100 packages a call. Pass repository (from the package's own package.json) for scoped or renamed packages; a Maven, Go or NuGet package goes by its purl. For the vendor's own breaking-change and migration sections, call upgrade_notes on the packages worth moving. A Maven, Go or NuGet package this server does not track is checked against deps.dev after the answer and counted; pass recordMisses: false for private packages.