Magento Open Source 2.4.9 MCP server

Which servers in the official MCP registry are Magento Open Source 2.4.9's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to Magento Open Source 2.4.9

Whose server it is

Registry namewatch.magento/magento-watchverified in the MCP registry

The registry name sits under magento.watch. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19

Stateanswerschecked 2026-10-19
Tools13
Server calls itselfmagento-watch
Server version1.0.0
Protocol version2024-11-05

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 16 ms.

Measured dailydaily checks: 1, the first on 2026-10-19

Answeredmeasuring1 of the 7 daily checks it takes to print a share
Median first answer991 ms
Space in an agent's context≈ 2,610 tokensthe definitions of all its tools (13), which an agent carries on every turn
Tool definitionsC · 73 of 100

Parameters without a description: in 8 of 13
Not saying whether it only reads or can destroy: 13 of 13

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work.

Tools it offers13 tools · read 2026-10-19

get_version
Get detailed information about a specific Magento/Adobe Commerce version including release date, EOL date, system requirements, and a security summary: `security.fixedBy` (security fixes already included in this version) and…
get_all_versions
Get all versions for a distribution with their lifecycle information. Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSecureVersion` and `statusLabel` describe the support lifecycle only, so a…
get_supported_versions
Get only currently supported versions (not EOL, not future releases). Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSecureVersion` and `statusLabel` describe the support lifecycle only, so a…
get_eol_versions
Get versions that have reached end-of-life. Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSecureVersion` and `statusLabel` describe the support lifecycle only, so a supported version can still…
check_compatibility
Check if a specific PHP, MySQL, or other dependency version is compatible with a Magento version
get_latest_version
Get the latest stable version for a distribution. Each version carries `securitySummary` { status, requiredPatches, upgradeRequired }: `isSecureVersion` and `statusLabel` describe the support lifecycle only, so a supported version can…
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…
find_patch
Find Adobe Quality Patches Tool (QPT) patches for a Magento Open Source or Adobe Commerce version. With only distribution and version it lists every applicable patch. Add query (symptoms, error text, feature words or a patch id like…
get_patch
Get one Quality Patches Tool patch by id (e.g. "ACSD-56760") with every file variant, its Composer constraint, resolved applicable versions per distribution, modified files, prerequisites, documentation fields and the raw patch URL.
find_upstream_fix
Community fixes merged into magento/magento2 after a release line was cut, with per-version applicability from git apply checks; not Adobe Quality Patches, for those use find_patch. With only distribution and version it lists, newest…
get_upstream_fix
Community fixes merged into magento/magento2 after a release line was cut, with per-version applicability from git apply checks; not Adobe Quality Patches, for those use find_patch. Get one upstream fix by id (e.g. "magento2-40867") with…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

OpenAPI spec

21 paths, read 2026-10-19. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.