Download the PHP package yu-dev/module-mcp-server without Composer

Magento MCP Server

An MCP (Model Context Protocol) server implemented as a Magento 2 module. It exposes store operations as typed, access-controlled MCP tools over the Streamable HTTP transport, so MCP clients (claude.ai Connectors, Claude Desktop, etc.) can read and manage the store from a chat session.

What the AI can do with it

Example phrases that resolve to tool calls:

Catalog & content (anonymous)

• "Find sports bras under $40" → product_search
• "Show the full card for SKU WS02" → product_get
• "Is MT01 in stock?" → product_check_stock
• "What promotions are running right now?" → promotion_list
• "What payment and delivery options does the store offer?" → store_info
• "What currency will I be charged in? Convert this price to euros." → store_info
• "How can I contact the store?" → store_info
• "What do customers say about the Antonia Racer Tank?" → review_list_for_product

Business insights (admin login required)

• "How were sales last week? Compare to the week before." → sales_compare_periods
• "Which orders are stuck in processing?" → order_list
• "Show negative reviews from the last 7 days — judge by the text, not the stars." → review_list
• "List abandoned carts over $100 from this week." → cart_list_abandoned
• "Which products are almost out of stock?" → product_low_stock
• "Who are my top customers by lifetime spend?" → customer_search
• "Find the customer Emma — how much has she spent with us?" → customer_search
• "Find Maria and show her recent orders." → customer_search + order_list_by_customer
• "How fast is WS02 selling — when will it run out?" → product_sales_velocity
• "Check the sales pace of everything that's low on stock — what should I reorder first?" → product_low_stock + product_sales_velocity
• "Top 10 products by revenue this quarter." → sales_bestsellers
• "Compare June to May — orders, revenue, average check." → sales_compare_periods
• "Which categories actually drive revenue?" → sales_by_category
• "How do customers pay, and which delivery options do they pick?" → sales_payment_stats + sales_shipping_stats
• "What do visitors search for — and which searches return nothing?" → search_terms_report
• "What needs fixing in the catalog: missing images, descriptions, meta?" → catalog_health_report
• "Is the store healthy — indexers, cron, cache?" → system_health
• "List every CMS page — any forgotten drafts?" → cms_page_list

Store management (admin login + write switch)

• "Raise the price of WS02 by 10% and clean up its description." → product_update
• "Create a draft product for the new hoodie, keep it disabled." → product_create
• "Approve the positive pending reviews, reject the spam one." → review_moderate
• "Add a CMS block with the holiday shipping notice." → cms_block_create
• "Duplicate WS02 as WS02-RED for the red variant." → product_duplicate
• "Hide the Sale category from the menu and refresh its meta description." → category_update

Prompts (one-click workflows)

• morning_report — the owner's daily digest: sales summary, orders needing action, review moderation queue with text-based sentiment, abandoned carts, low stock.
• store_checkup — the weekly health inspection: indexers/cron/cache, catalog content gaps, searches that find nothing, pending reviews and restock risks, prioritized into a "fix now / this week / backlog" plan.
• recover_carts — abandoned-cart triage plus a personalised recovery email draft per cart. Drafts only — nothing is sent.
• restock_advisor — a purchase table ranked by days-to-stockout: what runs out first and how much to reorder.
• review_moderate_queue — verdict per pending review, applied only after your explicit confirmation.
• product_content_writer — drafts missing product descriptions, one product per confirmation.
• zero_result_rescue — turns "searches that found nothing" into a naming-gap / assortment-gap worklist.
• sales_dashboard — an interactive dashboard with charts: revenue trend, categories, bestsellers, payment & shipping mix.
• sales_trends — this period vs the previous one (or last year), with percentage deltas and bestseller movers, as charts.
• product_performance — top products by revenue and by quantity with sales velocity; flags bestsellers about to run out of stock.

Requirements

• Magento 2.4.4+ (developed on 2.4.7; uses no APIs newer than 2.4.4)
• PHP 8.1+ (8.1 / 8.2 / 8.3)
• No third-party dependencies

Installation

Composer (recommended)

Manual (app/code)

Copy the module to app/code/Yu/McpServer (e.g. git clone into that path), then run the same bin/magento commands as above.

Smoke test:

Configuration

Stores → Configuration → Advanced → MCP Server:

Connecting a client

Add https://your-store.com/mcp as a custom connector (claude.ai: Settings → Connectors; Claude Desktop: Settings → Connectors → Add custom connector). The flow is automatic:

1. The client reads the discovery documents (/.well-known/oauth-protected-resource, /.well-known/oauth-authorization-server) and registers itself via Dynamic Client Registration (RFC 7591).
2. Public tools answer immediately. The first call to a restricted tool returns HTTP 401 + WWW-Authenticate with a resource_metadata pointer, which triggers the client's OAuth flow.
3. The user's browser lands on a login form backed by Magento's own admin authentication (\Magento\Backend\Model\Auth — lockout and 2FA apply). The issued token carries that admin's ACL permissions.

Protocol

Single endpoint POST /mcp, JSON-RPC 2.0, MCP Streamable HTTP transport. Batch requests supported. GET /mcp opens an empty SSE stream (some clients probe with GET before registering).

Error semantics: anonymous call to a restricted tool → HTTP 401 (+ WWW-Authenticate); authenticated but missing the ACL resource → JSON-RPC error -32002 (Forbidden) in a 200 response; over the anonymous rate limit → HTTP 429 + Retry-After.

Tools

40 tools, one class each in a domain subfolder of Model/Tools/ (Product/, Order/, Review/, ...), registered via DI in etc/di.xml. Tool names are domain-first ({domain}_{action}), so a sorted tools/list groups by domain and the name prefix matches the class's subfolder. Access is declared per tool through getRequiredAclResource(): null = public, otherwise the Magento ACL resource the caller's admin role must hold.

Public (anonymous, rate-limited)

Public tools return the customer view: disabled products are indistinguishable from nonexistent ones. An authenticated admin holding Magento_Catalog::products gets the admin view through the same tools — disabled products included and marked with status (ContextAwareToolInterface).

Read, ACL-gated

The sales tools aggregate over collection rows in PHP with documented scan limits (a truncated: true flag appears when a period exceeds them). system_health is read-only by design: it reports invalid indexers, failed/stuck cron jobs and disabled/invalidated caches, but fixing them stays admin work.

Write, ACL-gated + write switch

There are no delete tools of any kind, by design. Every successful write call is audit-logged (var/log/mcp.log, info level, no customer personal data).

Prompts

Security

• OAuth 2.1 Authorization Code + PKCE (S256 only), access + refresh tokens, refresh rotation on every use, single-use 60s auth codes, per-IP throttling of failed logins (5 / 15 min). Public clients only — no client secrets.
• Identity = Magento admin, permissions = Magento ACL. No parallel user store. A full Administrator role (Magento_Backend::all) is treated as a wildcard.
• Anonymous surface: rate-limited 60 requests/IP/min (proxy-aware client IP — works behind Cloudflare Tunnel / reverse proxies via X-Forwarded-For), optionally disableable entirely via the public-tools switch.
• Dedicated OAuth storage: mcp_oauth_client / mcp_oauth_auth_code / mcp_oauth_token tables (separate from Magento's OAuth 1.0a Integration tokens, which can't serve this flow).
• Presented-but-invalid tokens are a hard 401 — never silently downgraded to anonymous.

Logging

Dedicated channel var/log/mcp.log (method, tool name, duration, success/failure; write audit records). Payload bodies are logged only at debug level behind the config flag.

Development

Adding a tool: implement ToolInterface (or WriteToolInterface / ContextAwareToolInterface) as one class in Model/Tools/, register it in etc/di.xml under ToolRegistry's tools argument, add a unit test. Rules: DI only (no ObjectManager), data access through repositories/collections (no raw SQL), tools never see JSON-RPC — they return arrays or throw exceptions.