magento.watch

watch.magentoPublished by magento.watchOfficial publisherv1.0.0Updated Oct 24, 2026

Magento Open Source, Adobe Commerce and Mage-OS releases, EOL, requirements, CVEs and patches

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that gives an assistant Magento Open Source, Adobe Commerce and Mage-OS release, lifecycle, compatibility, CVE and patch information.

What you can do
Look up releases and lifecycle: latest, supported, end-of-life and all versions with release, EOL and system requirements, plus version details and security summaries for each distribution. Check compatibility of PHP, MySQL and other dependency versions against a Magento version. Survey security bulletins and CVEs, filtered by severity or publish date, and read a single bulletin with its fixes per distribution. Check whether a specific version is vulnerable to known bulletins and which version or isolated patch fixes it. Find and read Quality Patches Tool patches by symptoms, error text, modules, categories or patch id, and find community upstream fixes with per-version applicability.
When to use it
Useful when planning or auditing a Magento or Adobe Commerce upgrade, judging whether a version is still supported or secure, checking PHP or database compatibility, or locating the patch or upstream fix for a known issue or CVE.
Requirements
A remote streamable HTTP endpoint at magento.watch; no package, environment variable or header is declared, and no authentication is declared. Network access to the endpoint is needed.
Before you install
The server is read-only reference lookup, but its answers drive upgrade and patching decisions, so verify security and compatibility results against Adobe's own bulletins before acting. No authentication is declared, so avoid sending confidential project details in queries.

Installation

In SourceWeft

  1. Open magento.watch in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/watch.magento%2Fmagento-watch/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

13

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 `security.vulnerableTo` (open bulletins that still need an upgrade or an isolated patch)

Parametersversionrequireddistributionrequired

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 supported version can still have open bulletins. Call check_version_security for the remedies.

Parametersdistributionrequired

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 supported version can still have open bulletins. Call check_version_security for the remedies.

Parametersdistributionrequired

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 have open bulletins. Call check_version_security for the remedies.

Parametersdistributionrequired

check_compatibility

Check if a specific PHP, MySQL, or other dependency version is compatible with a Magento version

ParametersdependencyrequireddistributionrequiredmagentoVersionrequireddependencyVersionrequired

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 still have open bulletins. Call check_version_security for the remedies.

Parametersdistributionrequired

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.

Parameterssinceseverity

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.

Parametersidrequired

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-...".

Parametersversionrequireddistributionrequired

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 ACSD-56760), modules (e.g. "catalog", "module-sales") or categories (QPT names like "Admin", "Catalog/Product") to get a ranked list with a 0-100 relevance score and the signals that matched. Covers quality patches only; for security fixes use check_version_security. List mode can return several hundred hits; pass query, modules or categories to rank and limit. Mage-OS is not a QPT target and always returns status "unknown".

ParameterslimitquerymodulesversionrequiredcategoriesdistributionrequiredincludeInapplicable

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.

Parametersidrequiredversiondistribution

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 first, every upstream fix whose code applies cleanly to that version and that the version does not contain yet. Add query (symptoms, error text, feature words or an id like magento2-40867), modules or categories (QPT category names like "GraphQL", "Catalog/Product") to get a ranked list with a 0-100 relevance score and the signals that matched. fixedIn filters by the first release that contains the fix (null for fixes not in any release yet). Mage-OS always returns status "unknown"; a version outside the checked release tags returns status "unknown-version".

ParameterslimitqueryfixedInmodulesversionrequiredcategoriesdistributionrequiredincludeExcluded

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 its pull request, linked issues, first release containing it, per-tag code match, affected versions, touched packages and files, labels and triage scores. Pass version, and optionally distribution, to get the code match for that version and the Composer bundle URL when the fix applies to it.

Parametersidrequiredversiondistribution

Version history

1
  1. v1.0.0LatestOct 15, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Magento integrations