Store platform

Magento MCP Server (community)

A community-built Magento 2 MCP server for store administration: 30+ tools over the REST admin API, OAuth 1.0 integration authentication, two-phase commit for bulk changes and audit logging.

What it is and why it matters

What it does

• Read and manage products, orders, customers and inventory
• Authenticate with a Magento Integration (OAuth 1.0)
• Bulk operations with a confirmation step and audit log
• Run locally next to your store with Node.js

Best for

Developers and agencies that need admin-level automation on Magento 2 and can review the code they run.

How to connect it

1. Check the prerequisites listed in the documentation: Node.js 18 or later, a Magento 2 or Adobe Commerce instance, and an Integration with the API permissions you want. Use a staging copy of the store first.
2. Get the code as described in the documentation (clone the repository, run npm install, then npm run build). Review the source before running it, since it will hold admin-level credentials.
3. In Magento Admin, go to System > Integrations and add a new integration with a clear name. Under API, select only the resources you need. For a first trial, choose read-only resources where Magento allows it. Save and activate it, then copy the Consumer Key, Consumer Secret, Access Token and Access Token Secret.
4. Add the server to your MCP client configuration (for example claude_desktop_config.json for Claude Desktop), as described in the documentation. Set the command to node, point the arguments to the built dist/index.js file, and set MAGENTO_BASE_URL plus the four OAuth values as environment variables.
5. Restart the client, then ask the assistant to run auth.login first to start a session. Confirm with auth.whoami and try a read request such as a product search.
6. Optionally, if you use Fastly for cache purging, add the Fastly service ID and API token variables described in the documentation. Leave this out until you need it.

Exact commands and addresses change. Use the official documentation for the current steps.

Installation guide for Magento MCP Server (community)

Client-by-client steps, what to prepare, the first prompts to run and fixes for common errors.

ClaudeChatGPTGeminiMicrosoft CopilotPerplexityCursorClaude Code

→

Questions you can ask it

• Search products with names containing 'eye drops' and list their SKU, status and visibility.
• Run the product display check for SKU PROD-001 and explain why it might not show on the storefront.
• Give me the indexer status report and tell me which indexers are behind.
• Show the inventory salable report for SKU PROD-001, including quantity, stock status and backorder setting.

What it cannot do

• It is not vendor-supported, and the documentation does not describe a support channel or compatibility guarantees across Magento versions.
• It runs only on your own machine or server with Node.js. There is no hosted version, so each person using it needs their own setup and credentials.
• It cannot do anything outside the API permissions of the Magento Integration, and the documentation lists no tools for areas beyond catalog, pricing, promotions, CMS, SEO, diagnostics, cache and scope.

Staying safe

• Write tools are included (bulk product, price, CMS and URL key updates, cart price rules, coupon generation, cache purge). Test on staging, and give the integration only the API resources it needs. Create a separate read-only integration for exploration.
• Credentials are passed as environment variables in your MCP client config and kept in memory, according to the documentation. That config file still contains secrets in plain text, so restrict access to it and do not share it. An alternative admin username and password mode exists, but the integration route is the safer option.
• Review the guardrails before any live use. The documented defaults include a 500 SKU cap per bulk commit, a 1000 coupon cap, a 50 percent price change warning and a 50 percent maximum discount, and they are changed in the source code. Read every prepared plan before committing, and check the audit log (JSONL) afterwards. The two-phase flow only helps if a person reviews each plan.

Watch out for: Includes write operations and is not vendor-supported. Test on staging, use a limited integration, and review guardrails before any live use.

Frequently asked questions