Magento 2 MCP Server

Magento 2 MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A MCP server for Magento 2.

What you get

This is a Model Context Protocol (MCP) server that connects to a Magento 2 REST API, allowing Claude and other MCP clients to query product information from a Magento store.

What the assistant can call

Once Magento 2 is connected, these are the calls the assistant has available:

• get_product_by_sku — Get detailed information about a product by its SKU
• search_products — Search for products using Magento search criteria
• get_product_categories — Get categories for a specific product by SKU
• get_related_products — Get products related to a specific product by SKU
• get_product_stock — Get stock information for a product by SKU
• get_product_attributes — Get all attributes for a product by SKU
• get_product_by_id — Get detailed information about a product by its ID
• advanced_product_search — Search for products with advanced filtering options
• update_product_attribute — Update a specific attribute of a product by SKU
• get_customer_ordered_products_by_email — Get all ordered products for a customer by email address
• get_order_count — Get the number of orders for a given date range
• get_revenue — Get the total revenue for a given date range

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need 2 environment variables: MAGENTO_BASE_URL, MAGENTO_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js (v14 or higher) - A Magento 2 instance with REST API access - API token for the Magento 2 instance

Choosing this one

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Magento 2's toolset — get_product_by_sku, search_products, get_product_categories and 11 more — is a fair guide to whether it matches your workflow. It is maintained by boldcommerce; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Magento 2.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the magento 2 mcp server does with a few real requests.