Pick a client.

02

Add the server to your config.

no config file

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.cursor/mcp.json

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

03

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.
get_supported_versions All versions currently in support.
get_eol_versions Versions that have reached end of life.
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. 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.