Adobe Commerce MCP
NPM · @COMMENTEME/ADOBE-COMMERCE-MCP
Offline Adobe Commerce PHP docs, config files, bin/magento CLI, Web API and module scaffolding
Available components
Last scanned (3 hours ago)
Scores higher than 48% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2119 tokens (~163/item across 13 items; 10 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +2
- Stability: unverified → 0.17 ▲ functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 56
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@commenteme/adobe-commerce-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add-controller Add a controller and route ~279
Generate routes.xml, an action controller (GET page or POST JSON) and, for pages, the layout handle and template, for the frontend or adminhtml area (with ADMIN_RESOURCE and acl.xml for the Admin), adapted from the official routing docs. Returns the files for the caller to write.
| Name | Type | Req | Description |
|---|---|---|---|
| aclResource | string | – | adminhtml only: ACL resource for ADMIN_RESOURCE (default "<Vendor_Module>::<controller>") |
| action | string | – | Action class (default "Index") |
| area | string | yes | frontend (storefront) or adminhtml (Admin) |
| basePath | string | – | Module directory relative to the Commerce root (default "app/code/<Vendor>/<Module>") |
| controller | string | – | Controller folder (default "Index") |
| frontName | string | yes | URL front name: the first URL segment, <frontName>/<controller>/<action> (e.g. "reviews") |
| method | string | – | HTTP method: GET renders a page with a layout handle, POST returns JSON (default GET) |
| module | string | yes | Module name as Vendor_Module (e.g. "Acme_Reviews"), as registered in registration.php |
| routeId | string | – | Route id in routes.xml and first part of the layout handle (default: frontName) |
| title | string | – | Page title for GET actions |
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Files to write. The server never writes to disk. |
| notes | array | yes | Next steps and caveats |
No examples provided.
add-db-schema Add a table to db_schema.xml ~236
Generate a declarative schema etc/db_schema.xml table with columns, primary key, unique constraints, foreign keys and indexes, adapted from the official declarative schema docs, plus the whitelist and setup:upgrade steps. Returns the file for the caller to write.
| Name | Type | Req | Description |
|---|---|---|---|
| basePath | string | – | Module directory relative to the Commerce root (default "app/code/<Vendor>/<Module>") |
| columns | array | – | Columns. Without columns the table gets an entity_id int unsigned identity primary key. |
| comment | string | – | Table comment |
| engine | string | – | SQL engine, default "innodb" |
| foreignKeys | array | – | – |
| indexes | array | – | – |
| module | string | yes | Module name as Vendor_Module (e.g. "Acme_Reviews"), as registered in registration.php |
| primaryKey | array | – | Primary key columns (default: the identity column) |
| resource | string | – | Database resource (shard), default "default" |
| table | string | yes | Table name (e.g. "acme_review") |
| unique | array | – | Unique constraints, each a list of columns |
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Files to write. The server never writes to disk. |
| notes | array | yes | Next steps and caveats |
No examples provided.
add-observer Add an event observer ~192
Generate an observer class and its events.xml subscription (global or per area), adapted from the official events and observers docs. Returns the files for the caller to write. Use it to react to a dispatched event.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | global (etc/events.xml, all areas) or one area folder (default global) |
| basePath | string | – | Module directory relative to the Commerce root (default "app/code/<Vendor>/<Module>") |
| event | string | yes | Event name to observe (e.g. "catalog_product_save_after", "checkout_cart_add_product_complete") |
| module | string | yes | Module name as Vendor_Module (e.g. "Acme_Reviews"), as registered in registration.php |
| observerClass | string | – | Observer class name inside <Module>\Observer (default derived from the event name) |
| observerName | string | – | Observer name in events.xml (unique per event) |
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Files to write. The server never writes to disk. |
| notes | array | yes | Next steps and caveats |
No examples provided.
add-plugin Add a plugin (interceptor) ~275
Generate a before, after or around plugin class and its di.xml declaration for a public method of a class or interface, adapted from the official plugins docs. Returns the files for the caller to write. Use it to change the behavior of a core or third-party method without rewriting the class.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | di.xml area: global (etc/di.xml) or an area folder (default global) |
| basePath | string | – | Module directory relative to the Commerce root (default "app/code/<Vendor>/<Module>") |
| method | string | yes | Public method to intercept (e.g. "getName", "save") |
| module | string | yes | Module name as Vendor_Module (e.g. "Acme_Reviews"), as registered in registration.php |
| pluginClass | string | – | Plugin class name inside <Module>\Plugin (default "<TargetShortName>Plugin") |
| pluginName | string | – | Plugin name in di.xml (default "<vendor>_<module>_<target>_<method>") |
| sortOrder | integer | – | sortOrder attribute in di.xml |
| targetClass | string | yes | Class or interface whose public method is intercepted (e.g. "Magento\Catalog\Model\Product") |
| type | string | yes | Plugin type. The docs advise after over around unless the chain must be stopped. |
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Files to write. The server never writes to disk. |
| notes | array | yes | Next steps and caveats |
No examples provided.
explain-config-file Explain a module config file ~163
Explain an Adobe Commerce module configuration file (di.xml, events.xml, webapi.xml, db_schema.xml, crontab.xml, routes.xml, system.xml, acl.xml, config.xml, layout, ui_component, schema.graphqls, requirejs-config.js and more): what it is for, where it goes (folder and area), the XSD URN from the docs, and the documentation pages. Use it before creating or editing one of these files.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Config file name or path inside a module (e.g. "di.xml", "etc/adminhtml/system.xml", "db_schema.xml", "crontab.xml", "webapi.xml", "view/frontend/layout/catalog_product_view.xml", "requirejs-config.j… |
No output schema declared.
No examples provided.
lookup-cli-command Look up a bin/magento command ~126
Look up a bin/magento command of Adobe Commerce on-premises: description, usage, arguments and options, from the official CLI reference. Accepts full names, Symfony shortcuts (s:up) or keywords. Use it before suggesting or running a bin/magento command.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | A bin/magento command, full or with Symfony shortcuts (e.g. "setup:upgrade", "bin/magento s:up", "indexer:reindex"), or keywords to find one (e.g. "static content deploy", "maintenance") |
No output schema declared.
No examples provided.
lookup-webapi Look up REST endpoints and GraphQL operations ~176
Look up Adobe Commerce Web API: REST endpoints (path, method, parameters, body, which tokens can call it) from the official OpenAPI schema, and GraphQL queries and mutations (arguments, return type, example, guide). Accepts a GraphQL name, a REST path or keywords. Use it when writing integrations or storefront calls.
| Name | Type | Req | Description |
|---|---|---|---|
| api | string | – | Limit to REST or GraphQL |
| limit | integer | – | Max results for keyword search (default 10) |
| method | string | – | REST only: HTTP method |
| query | string | yes | GraphQL query or mutation name (e.g. "products", "addProductsToCart"), REST path (e.g. "/V1/products/{sku}", "V1/orders"), or keywords (e.g. "cart coupon", "customer address") |
No output schema declared.
No examples provided.
read-doc Read an Adobe Commerce doc page ~145
Read a full page, or one section, of the bundled Adobe Commerce documentation by id (from search-docs), source path or public developer.adobe.com / experienceleague.adobe.com URL. Use it after search-docs, or when the user pastes a docs link.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | yes | Document id as returned by search-docs (e.g. "php/development/components/plugins.md"), source path (e.g. "commerce-php/src/pages/development/components/plugins.md") or public URL. Append "#anchor" to… |
| section | string | – | Section anchor or heading to read only that section (e.g. "around-methods") |
No output schema declared.
No examples provided.
scaffold-module Scaffold an Adobe Commerce module ~246
Generate registration.php, etc/module.xml and composer.json for a new Adobe Commerce module (Vendor_Module), adapted from the official docs. Returns the files (path and content) for the caller to write; the server never writes to disk. Use it when starting a module.
| Name | Type | Req | Description |
|---|---|---|---|
| basePath | string | – | Module directory relative to the Commerce root (default "app/code/<Vendor>/<Module>") |
| description | string | – | composer.json description |
| license | array | – | composer.json license list (default ["proprietary"]) |
| module | string | yes | Module name as Vendor_Module (e.g. "Acme_Reviews"), as registered in registration.php |
| packageName | string | – | Composer package name (default "<vendor>/module-<module>", lowercase) |
| php | string | – | PHP constraint for composer.json require (e.g. "~8.3.0||~8.4.0"). Omitted when not given. |
| sequence | array | – | Modules that must load before this one, for <sequence> in module.xml (e.g. ["Magento_Catalog"]) |
| version | string | – | composer.json version (default "1.0.0") |
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Files to write. The server never writes to disk. |
| notes | array | yes | Next steps and caveats |
No examples provided.
search-docs Search Adobe Commerce docs ~197
Search the official Adobe Commerce (Magento Open Source) developer documentation bundled offline: PHP extensions, frontend core, Web APIs and operations. Use it first for any "how do I" question about modules, plugins, DI, events, declarative schema, layouts, caching, indexers, queues or configuration. Returns excerpts with title, public URL and source path; follow up with read-doc.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Restrict to one doc set: php (PHP extensions), frontend (themes, layouts, UI components, JS), webapi (REST and GraphQL guides), operations (configuration, CLI, installation, performance) |
| limit | integer | – | Max results (default 5, max 20) |
| query | string | yes | Keywords to look for in the official Adobe Commerce docs (e.g. "plugin around method", "declarative schema foreign key", "message queue consumer", "full page cache private content") |
No output schema declared.
No examples provided.
How do I install the Adobe Commerce MCP server?
Adobe Commerce MCP runs locally as an npm package, launched with npx -y @commenteme/adobe-commerce-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @commenteme/adobe-commerce-mcp
claude mcp add commentemeapp-adobe-commerce-mcp -- npx -y @commenteme/adobe-commerce-mcp
What is the Adobe Commerce MCP server?
Adobe Commerce MCP is listed in the public MCP registry as io.github.commentemeapp/adobe-commerce-mcp. Offline Adobe Commerce PHP docs, config files, bin/magento CLI, Web API and module scaffolding. This page covers its npm package (@commenteme/adobe-commerce-mcp).
Is the Adobe Commerce MCP server safe to use?
Adobe Commerce MCP scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Adobe Commerce MCP server expose?
Adobe Commerce MCP exposes 10 tools: search-docs, read-doc, explain-config-file, lookup-cli-command, lookup-webapi, and 5 more. Their descriptions and schemas cost roughly 2,035 tokens of context every time the server is loaded.
Is the Adobe Commerce MCP server still maintained?
Adobe Commerce MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Adobe Commerce MCP server under?
Adobe Commerce MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.