Let your coding agent read the release calendar.

Pick a client.

Add the server to your config.

claude mcp add magento-watch --transport http https://magento.watch/mcp/api

{
  "mcpServers": {
    "magento-watch": {
      "url": "https://magento.watch/mcp/api",
      "transport": "http"
    }
  }
}

{
  "mcpServers": {
    "magento-watch": {
      "url": "https://magento.watch/mcp/api",
      "transport": "http"
    }
  }
}

Restart the client.

Your agent now has the following tools available:

• get_version Return a single version with its full lifecycle and system requirements.
• get_all_versions Every tracked version for a distribution with full lifecycle data and the security patches each release still needs.
• get_supported_versions All versions currently in support, each with the security patches it still needs.
• get_eol_versions Versions that have reached end of support.
• check_compatibility Ask whether a PHP, MySQL, or other dependency version is compatible with a given release.
• get_latest_version Latest stable release for a distribution.
• get_security_bulletins List Adobe/Magento security bulletins (CVEs), optionally filtered by severity or publish date. Use this to list critical bulletins since a given date, or to survey what has been disclosed.
• get_security_bulletin Get one security bulletin by id, including a plain-text summary, its CVEs, severity, and which versions per distribution contain the fix. Use this when the user names a specific bulletin or asks which patch fixes a given CVE.
• check_version_security Check whether a specific Magento/Adobe Commerce version is vulnerable to known security bulletins, and which version fixes it. A version is also vulnerable when the only remedy from Adobe is an isolated patch applied on top of that base release; fixedIn is then null. This is the tool to call when a user asks "is my Magento vulnerable" or "which patch fixes CVE-...".
• find_patch List every QPT quality patch that applies to a Magento version, or rank them against a described bug.
• get_patch One quality patch with its file variants, constraints, modified files and documentation.
• find_upstream_fix List community fixes merged upstream that still apply to a Magento version, or rank them against a described bug.
• get_upstream_fix One upstream fix with its pull request, issues, first release and per-version code match.