Skip to content
Custom Connectors

Connect Magento to Claude Code

Have Claude update products and process orders in Magento (Adobe Commerce). From the terminal, inside the sessions where you already work.

How do you connect Magento to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Magento, you add a Magento MCP server: a small hosted service that exposes Magento's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Magento account. No API keys pasted into config files.

claude mcp add --transport http magento https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Magento once connected?

Full read-write Magento access lets Claude update product details and inventory, change prices, process and fulfill orders, and manage customer records directly in the admin. The catalog edits and order work that used to mean clicking through the admin grid happen where your store data already lives, with you approving anything sensitive.

  • Update product titles, descriptions, attributes, and stock quantities
  • Adjust prices or apply a sale across a set of products
  • Move orders through fulfillment by updating their status
  • Create or update customer records and assign them to groups
  • Draft and apply catalog price rules or coupon codes
  • Bulk-edit products matching a search before you approve the change

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Magento access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Magento API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Magento changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Magento connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Magento connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Magento account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Magento's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Magento?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Magento account it signs in with. Revoking access is one click in Magento.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.