Ask this site instead of scraping it

Claude Code — one command:

claude mcp add --transport http whatsnew https://whatsnew.fyi/mcp

Claude.ai and Claude Desktop — Settings → Connectors → Add custom connector, then paste the endpoint URL. There is no sign-in step; the connector works as soon as the URL is saved.

Cursor — add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "whatsnew": { "url": "https://whatsnew.fyi/mcp" }
  }
}

VS Code — add to .vscode/mcp.json:

{
  "servers": {
    "whatsnew": { "type": "http", "url": "https://whatsnew.fyi/mcp" }
  }
}

Clients that only speak stdio — bridge with mcp-remote:

{
  "mcpServers": {
    "whatsnew": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://whatsnew.fyi/mcp"]
    }
  }
}

whats_new(product, since_version?, limit?) — the newest releases for one product, with their notes. Pass since_version (the version you run) and the answer is only what shipped after it, with change counts per category: 2 fixed, 1 security since yours. The tool looks your version up in the release history by exact match (a leading v is fine) and never guesses version order. If it cannot find the version you named, it tells you and shows the latest releases instead.

search_releases(query, category?) — full-catalog search across product names and release history, the same search the search box on the site runs. Returns matching products and releases, each with a permalink.

list_products(category?, query?) — the tracked catalog with slugs, categories and platforms. Start here: the slugs it returns are what whats_new accepts, though plain product names usually resolve too.

Things worth asking once it is connected:

• “What’s new in Neovim since 0.10.0? Anything breaking?”
• “Did any of my dependencies ship a security fix this month?”
• “Which browsers released something this week?”

Every release in a result carries its provenance, the same labels the site shows: Sample data for hand-curated seed entries, Pre-release for betas and release candidates, and a low-confidence note where a publisher shipped boilerplate instead of real notes. Keep those labels if you quote an entry. The release notes the vendor publishes are the authoritative version, and every entry links to them.

Responses stay small on purpose: at most 100 products per listing, 25 releases per whats_new call, and release bodies cut at 1,500 characters with a bodyTruncated flag. Follow the permalink when you want the full text.

The endpoint is rate limited per IP. The terms allow machine reading in as many words, and they ask two things in return: keep to the rate limits, and if you republish what you find, credit the publisher and link back. If your agent would rather read documents than call tools, /llms.txt, the per-product markdown exports, and RSS cover the same ground.