PrestaShop MCP: connecting your shop to Claude, ChatGPT or Le Chat
An MCP (Model Context Protocol) server lets an AI assistant call precise functions of your PrestaShop shop: read sales, find an order, fix a product page. PrestaShop has published a free official module since November 2025; I have also built my own MCP module, running in production on shops I maintain. I help you choose, install and, above all, secure either one.
An MCP project on PrestaShop?
What an MCP server is for PrestaShop
MCP is an open protocol that standardises how an AI assistant discovers and calls “tools” exposed by an external system. On PrestaShop, each tool is a bounded operation: get revenue for a period, list abandoned carts, read a product page, update a meta description. The assistant doesn’t guess and doesn’t browse the back office: it calls a described function with typed parameters and gets a structured answer.
In practice you can ask, in plain language, “which products lost sales this month compared with last month?” or “which product pages have no meta description?”, and the assistant chains the calls it needs. It is only useful if the exposed tools are well chosen, and only safe if permissions are set properly.
Official module or bespoke module: how to choose
The official PrestaShop MCP Server module, released on 19 November 2025, is free. It requires PrestaShop 8.2 or later and PHP 8.1, plus the PrestaShop Account and MBO modules. It covers catalogue, orders, customers and SEO, and other modules can add their own tools: a module declares itself compatible, then marks its public methods with the PHP attribute #[McpTool], which the official server discovers automatically.
A bespoke module makes sense in three cases: your shop still runs 1.7 or 8.0/8.1 and cannot install the official module; you want to give read-only access to a third party (partner, accountant, agency) without opening the back office; or you need tools the official module doesn’t offer, such as server log analysis, order attribution or quotes from a business module.
It isn’t one or the other: I can also write #[McpTool] tools for your existing modules that plug into the official server.
What the MCP module I built does
-
Native PHP module, no Node.js
The MCP server runs inside PrestaShop itself, through an HTTPS route of the module: nothing extra to install on the hosting. Its code declares compatibility from PrestaShop 1.7.
-
Forty read-only tools
Sales by period, products sold, abandoned carts, order statuses, quotes and their conversion, order attribution, internal search, catalogue and tracking health, period comparison, client report.
-
Private keys with limited scope
Each key is named, expires (ninety days suggested, one year at most), only opens the permissions ticked and can be restricted to IP addresses. Only its fingerprint is stored; revocation applies from the next request.
-
Server logs without personal data
Bounded reading of the access and error logs the administrator approves, with IPs, emails and identifiers in paths masked. An HTTP request is never presented as a visit.
-
Controlled, reversible writes
On the administrator side, creating or changing a product, category, customer or CMS page is logged and can be undone. Deletions are blocked while safe mode is on.
-
Rate limits
Sixty requests per minute per key and a capped request body: an assistant stuck in a loop won’t bring the shop down.
How a setup runs
-
List the questions and actions to delegate
We start from your real habits: the figures you check every week, the repetitive fixes, the reports you build by hand. Each need becomes a tool, or not.
-
Choose the technical route
Official module, bespoke tools plugged into it, or a standalone module, depending on your PrestaShop version, your hosting and the level of access wanted.
-
Test on a copy of the shop
Installation and trials on staging or a restored backup, never straight on production the first time.
-
Set permissions profile by profile
Read-only by default; write access only for the tools that need it and the people who use it; separate keys per person or per tool so a single one can be revoked.
-
Connect your assistant and check
Connector set up in Claude, ChatGPT, Le Chat or n8n, then a set of control questions whose answers we already know, to confirm the figures are right.
-
Document and hand over
You get the list of tools, keys and their scope, and the steps to revoke an access.
Unsure between the official module and a bespoke one?
When a PrestaShop MCP server makes sense
- You export the same figures to a spreadsheet every week to analyse them
- You want to fix incomplete meta descriptions or product pages in bulk
- Your shop runs 1.7 or 8.1 and the official module refuses to install
- A partner or contractor needs the figures, but not back-office access
- One of your business modules (quotes, configurator, B2B) should be queryable by AI
What an MCP server doesn’t do
It doesn’t make your shop visible in ChatGPT or in Google’s answers: it is private access for you and your team, not a public shop window. For visibility, see the guide on making your shop visible in AI search, and for purchases made by agents, what agentic commerce really covers.
Nor does it replace audience measurement: orders and server logs don’t tell you how many people visited. Finally, an assistant can misread a question; that’s why I favour tools that return verifiable data rather than ready-made conclusions.
Related pages
-
MCP server for a shop
The general approach, whatever the platform: tool scope, permissions, traceability.
-
Bespoke PrestaShop module
When the MCP tool you need first requires a specific module.
-
WordPress and WooCommerce MCP
The same approach on WooCommerce, with the Abilities API and the MCP Adapter.
-
Shopify MCP
Storefront MCP, Dev MCP and a private server on the Admin API.
Connect your PrestaShop shop to AI, properly
Describe your need in one minute
A few targeted questions so I can reply with an estimate rather than another questionnaire.