magento.watch MCP Server

by magento Your server? Claim it

answering

magento.watch is answering right now. Last checked 8 min ago. It exposes 13 tools.

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

Uptime history 24 days of history

24 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

196 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check magento.watch every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://magento.watch/mcp/api

~/.codex/config.toml

[mcp_servers.magento-watch]
url = "https://magento.watch/mcp/api"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 13

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

patch

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

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.

security

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.

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.

upstream

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

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.

version

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

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)

all

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.

compatibility

check_compatibility

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

eol

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.

latest

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.

supported

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.

Endpoints

URL	Transport	State	Latency	Checked
https://magento.watch/mcp/api	streamable-http	answering	84 ms	8 min ago

Alternatives to magento.watch

same job, measured the same way

Magento Cloud MCP Server

by juan-cinto-infracommerce

MCP server for Adobe Commerce Cloud — REST API + SSH, no PHP CLI required

73 installs/wk local only

Agentic Commerce Readiness

by expandingweb

Score a Magento or Adobe Commerce store on eight AI agent-readiness checks.

7 tools answering

Adobe Commerce Docs MCP

by jigarkkarangiya

MCP server for Adobe Commerce / Magento 2 documentation — search, browse, and read official docs.

80 installs/wk local only

Anteproof

by anteproof

Commit-pace and release probabilities for open-source repositories. Docs: anteproof.com/docs

6 tools answering

Visaroute

by cloudcorprecords

Passport visa, entry and transit requirements for any country pair, with official sources.

228 installs/wk local only

Dibs (Hive Commons)

by hivecommons

Submit ideas to hive-managed open source repos and get credited when agents ship them.

4 tools answering

SearchForge

by divyanshu-iitian

Free open-source web search and page reading for LLMs, AI agents, and RAG.

local only

Macbeth

by wende

Open-source computer use for macOS agents.

48 installs/wk local only

magento.watch — questions

Answers built from our own checks of this server.

What can magento.watch do?

It exposes 13 tools, read directly from the server on our last check. Among them: check_compatibility, check_version_security, find_patch, find_upstream_fix, get_all_versions, get_eol_versions and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is magento.watch mostly used for?

Its tools cluster around security, version and patch. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is magento.watch working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 196 ms. The bar chart above shows every period we have measured.

How do I connect magento.watch?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does magento.watch need an API key?

No. magento.watch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is magento.watch?

It answers our handshake in 196 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.