04 · Agent access · Open source
MCP Server for Magento 2
angeo/module-mcp-server
A Model Context Protocol server that gives AI agents live, structured, rate-limited access to your catalogue — product search, product cards, categories and store info. Read-only by default. No scraping, no headless browser, no theme to break.
Free and MIT-licensed. No licence key, no account, no telemetry.
What it does
Four things worth knowing before you install.
Structured access instead of scraping
An agent asking about your catalogue currently has two options: parse your rendered HTML, or guess. This gives it typed tools that return real data from Magento — product search, product cards, categories, store info.
Read-only until you decide otherwise
The default install exposes nothing that changes state. Writes arrive only if you add the checkout module deliberately, which means the risky surface is opt-in rather than something you have to remember to turn off.
Rate limited at the server
Limits are enforced server-side, not requested politely of the client. An agent in a loop cannot turn your catalogue into an outage.
Any MCP client
Claude, Gemini, ChatGPT and custom assistants speak the same protocol. You implement the server once instead of once per vendor.
Start here for anything agentic. This is the base the checkout tools attach to. Installing it alone is safe and reversible — it adds read-only tools and nothing that can spend money.
Requirements
| Magento | Open Source / Adobe Commerce 2.4.x |
| PHP | 8.2+ |
| Protocol | Model Context Protocol |
| Default mode | Read-only |
| Licence | MIT |
Questions
What can an agent actually do with this?
Search products, retrieve product cards, browse categories and read store information — the discovery half of a shopping conversation. Nothing that changes state, unless you also install the checkout module.
Is exposing my catalogue to AI agents safe?
The read-only default and server-side rate limiting are the two things that make it defensible. Everything exposed is already public on your storefront; the difference is that it arrives structured instead of scraped.
How is this different from llms.txt?
llms.txt is a static file a crawler fetches. MCP is a live connection an agent queries in the moment, with current prices and stock. Different mechanisms, and you want both.
Which clients can connect?
Any MCP client — Claude, Gemini, ChatGPT and custom assistants. That is the point of implementing a protocol rather than one vendor’s API.
Works with
Each module is independent, but these three are the ones most often installed alongside it.
Not sure whether you need this one?
Run the free scanner on your domain, or install the CLI audit. Both report which signals your store currently fails, so you install only what closes a real gap.