Magento MCP Servers Compared (2026): 17 Projects

Checked on 18 September 2026. Features are what each project or vendor documents about itself.

What is a Magento MCP server?

MCP (Model Context Protocol) is an open standard, first released by Anthropic. It lets an AI client call tools on another system. For Magento, a tool can be “search products”, “get order status” or “list DI preferences”. A Magento MCP server decides which tools exist, who may call them and what they may change.

“Magento 2 MCP” is the practical shorthand for connecting a Magento 2 or Adobe Commerce installation to MCP-capable AI clients.

Adobe documents two different MCPs for Adobe Commerce. Commerce MCP is for agentic commerce, from discovery to checkout, and is labelled “Coming Soon”. Commerce Developer MCP is development tooling for Adobe Commerce as a Cloud Service. They serve different use cases and are not two versions of the same server. We count separately documented products or projects, not vendors, so Adobe appears twice. Where two components are separate installs but form one product flow, such as angeo mcp-server and mcp-checkout, we describe them together.

How is MCP different from APIs, UCP, WebMCP and ACP?

Many MCP servers use Magento’s REST or GraphQL APIs underneath. MCP adds tool descriptions that AI clients understand.

Magento MCP server types: storefront, admin and developer

These are category-level risks, not findings against any project listed below. The grouping is ours, not an official MCP or Magento taxonomy.

Where does a Magento MCP server run? Deployment and architecture models

These four models mix architecture (module or sidecar), access context (local) and hosting (platform). They are a practical grouping, not a formal MCP taxonomy.

How to evaluate a Magento MCP server

For each project we look at: what it actually is, where it runs, how clients get access, what it can write, which safety controls it documents, its license and its status. Status means the latest release, repository activity or vendor availability label we found on 18 September 2026.

We use one vocabulary for writes: None documented, Read-only by design, Cart and checkout, Admin data, Code and files, CLI and database, Not documented.

What can go wrong?

Security checklist

1. Authentication. For remote servers, prefer standards-based authentication such as OAuth 2.1 where supported, or narrowly scoped credentials. Local developer servers rely on OS and process permissions and should avoid unnecessary network exposure. Never put an admin password in a config file.
2. Authorization. For remote deployments, validate the authentication protocol’s issuer, audience and scopes where applicable. Origin is not an authentication mechanism.
3. Token lifecycle. Prefer expiring credentials with rotation and revocation over long-lived static secrets.
4. Permissions per tool. Where an admin MCP server exposes Magento data, verify that each tool is subject to the intended Magento ACL.
5. A write switch. Check whether one setting can block all changes.
6. Approval for writes. Clearly mark state-changing tools, and use client-side confirmation and/or server-side approval controls before consequential actions.
7. Audit log. For sensitive admin deployments, consider an audit log that records calls and masks customer data.
8. Rate limits. Per client and per tool — and switched on in production.
9. Transport security. Enforce HTTPS, protect browser-based sign-in flows against CSRF, and follow the server’s documented protocol and origin requirements.
10. Separation. Storefront and admin servers use different endpoints and credentials, and the MCP endpoint does not reuse a Magento admin session.
11. Untrusted text. Product descriptions, reviews and code comments are data, not instructions.

Magento MCP servers compared

Absence of documentation is not evidence that a feature is absent. Both tables show what each project documents, not what we tested.

Main comparison

Documented security and permissions

We did not penetration-test the servers or audit their controls. Every cell below is based on the project’s own documentation.

Summary by group

This is a grouping, not a ranking.

• Shopping agents: Mirasvit Agentic Commerce, Meetanshi Agentic Commerce, Adobe Commerce MCP (coming soon), angeo.
• Admin work: Magebit, Scandiweb, Mirasvit AI Agent Connector, yuriyakishin, adwise, thomastx05, magendooro, iranimij.
• Development: Magento 2 and Adobe Commerce PhpStorm plugin, n98-magerun2 MCP, Adobe Commerce Developer MCP, Inchoo Bricklayer, elgentos (abandoned).
• Local-first: PhpStorm plugin, n98-magerun2 MCP, Inchoo Bricklayer, elgentos. Adobe Commerce Developer MCP also involves Adobe’s cloud service.
• Documented remote HTTP access: Magebit, Mirasvit AI Agent Connector, adwise (SSE), angeo. Scandiweb, Mirasvit Agentic Commerce and Meetanshi describe connecting hosted AI clients.
• No writes documented or read-only by design: Mirasvit Agentic Commerce; angeo mcp-server without mcp-checkout.

Storefront and agentic-commerce servers

Storefront servers serve shoppers’ agents, not your staff. They are part of agentic commerce and should only expose public data.

Admin servers: work with store data through AI clients

This is the busiest category. Projects differ most in how they control writes.

Developer servers: help coding agents work on Magento

How do I connect Magento to Claude, Claude Code, Cursor or ChatGPT?

Claude Code, Cursor and other coding agents

Use a local developer server: the Magento 2 and Adobe Commerce PhpStorm plugin through the IDE’s MCP server, or magerun2 mcp:server:start. In PhpStorm, the MCP server is off by default; turn it on in Settings → Tools → MCP Server. On Adobe Commerce as a Cloud Service, Adobe’s Commerce Developer MCP and skills are built for coding agents. Point any of them at a development install.

Claude (web or desktop)

Add an admin or storefront server that is reachable over HTTPS as a custom connector. Connector and MCP availability in Claude depends on the client and the plan, so check Anthropic’s current connector documentation before you deploy.

ChatGPT

As of 18 September 2026, OpenAI documents the following. ChatGPT calls these integrations “apps” (they were “connectors” until December 2025). Custom MCP apps are added in developer mode and connect to remote MCP servers. According to OpenAI’s Help Center, full MCP support including write actions is rolling out in beta for Business, Enterprise and Edu, and write actions can require user confirmation. For a private, on-premises or local server, OpenAI documents Secure MCP Tunnel: a client inside your network opens an outbound HTTPS connection, so the MCP server is not exposed to the public internet. Check your plan and workspace before you deploy.

Shoppers’ agents

Use a storefront server. If it implements UCP’s MCP binding, advertise that endpoint in your UCP business profile at /.well-known/ucp, as the UCP specification describes. See Magento UCP modules compared.

Which type of Magento MCP server fits your use case?

• Staff manage orders and content through AI. An admin server. Look for OAuth, per-tool ACL, a write switch, confirmation for writes and an audit log.
• AI shopping agents should see your catalog. A storefront server, alone or inside an agentic commerce module. Look for public-data-only access and rate limits.
• Developers use Claude Code, Cursor or PhpStorm. A local developer server. Look for active maintenance and no production credentials.
• You run Adobe Commerce as a Cloud Service. Commerce Developer MCP for development. Commerce MCP for agentic commerce, once Adobe makes it available.
• You self-host Magento. A module or a sidecar, depending on how you isolate services.
• Security is a separate evaluation dimension. Compare documented controls rather than treating feature count as a security signal.

What does MCP not do?

• Connecting an MCP server does not guarantee that an AI assistant will discover, index or recommend your products.
• It does not replace crawlability, Product schema or product feeds.
• It gives a compatible agent direct tool access only when that agent chooses to use it.

Our observation (not a documented fact): in August 2026 we connected one demo Magento store to Claude as a custom connector and tried a few prompts by hand. A cold shopping prompt in a new chat, such as “Find me a grey backpack”, went to Claude’s built-in product search instead of the store’s MCP tools. A prompt about the store itself, “What do you sell here?”, did reach the connector. This was a handful of manual tries, not a systematic study.

MCP discovery mechanisms are less established than web crawling and product-feed distribution. See AEO options for Magento.

Frequently asked questions

How we compared

We read each project’s README, Packagist listing, release notes, vendor page or official documentation on 18 September 2026. For thomastx05 and magendooro we relied on our own awesome-magento-aeo entries. We did not install the commercial extensions, and we did not audit any security control. Corrections are welcome — contact us.

• OpenAI: Developer mode and MCP apps
• OpenAI: Secure MCP Tunnel
• JetBrains: PhpStorm MCP server
• UCP specification
• Adobe: Summit 2026 announcements
• Project sources are linked in each entry and in the main table.