O'So MCP Server for PrestaShop

O'So MCP Server for PrestaShop

https://github.com/user-attachments/assets/cf0b0e3f-1172-4ba9-aad1-11a6298aadf7

Ask your AI assistant to find an order, change a status, check your stock or audit a product page, and it does it in your back office - with the rights of the employee who connected it, and never more.

In the back office the module is called O'So MCP Server.

---

What you can ask

"Which orders are still waiting for shipment since Monday?"

"Mark order #1042 as shipped."

"Which products are almost out of stock?"

"Show me last month's sales."

"Audit the SEO of my best-selling product and fix its meta description."

"Who is the customer behind order #1042, and what else did they buy?"

More than 90 tools cover orders, catalogue, stock, customers, statistics, SEO, content pages, modules and appearance, and more than 10 ready-made prompts guide the assistant through the usual jobs. See them all.

---

Requirements

The Run the diagnostic button in the module checks all of this from the outside: certificate, SSL setting, friendly URLs, location, the addresses an assistant calls and the sign-in page where you approve it. No line should be red before you connect an assistant.

---

Install in 3 steps

1. Download OSo-MCP-Server-x.y.z.zip from the latest release. Do not unzip it.
2. In your back office, open Modules > Module Manager, click Upload a module and drop the zip, then Configure.
3. In the Access and security tab, turn on Consent page - it is off unless you are connecting an assistant.
4. Copy the address to give to your assistant - it looks like https://your-shop.example/module/somcp/mcp - and paste it into Claude, ChatGPT or another assistant (where to paste it).

The first time, the assistant opens a page of your shop: you sign in with your back office email and password, type the code e-mailed to you, check where the answer goes, and approve what it may do. Then turn Consent page off again: the assistant keeps working. Step by step with screenshots: Installation.

---

Or use the assistant built into your back office

No account to connect: a chat button at the top of every back office page opens an assistant that works with the same tools, with the rights of the employee signed in, and asks for your approval before any change.

• Bring your own key from Claude, ChatGPT, Gemini, Mistral, DeepSeek, Grok or Cohere - each link opens the page where that provider gives out keys.
• Or run an AI on your own computer, such as Ollama or LM Studio, with O'So AI Relay: no key, and nothing opened on your network.
• Deep thinking, web search and memory can be switched on or off for each conversation, from the + menu. Several assistants can share the work by role.

More in the wiki: Built-in assistant.

[The settings pages of O'So MCP Server, one after the other]

---

Compatible assistants

Any assistant that connects to a remote MCP server with OAuth can use your shop's address. These can:

• Chat: Claude (web, desktop, mobile), ChatGPT, Le Chat (Mistral), Dust
• Command line: Claude Code, Codex (OpenAI), Gemini CLI (Google), GitHub Copilot CLI
• Code editor: Cursor, VS Code (GitHub Copilot), Windsurf (Devin Desktop), Zed
• Automation: n8n (Cloud and self-hosted), Make

Where to paste the address in each of them: Connect an assistant.

---

Your shop stays protected

• Each employee decides. An assistant only gets the rights of the employee who connected it, page by page, exactly as set in Team > Permissions, and only on the shops that employee is attached to.
• No password and no all-powerful API key. Assistants sign in with OAuth 2.1, and every connection can be withdrawn in one click from the module.
• A connection takes your password and a code by e-mail, on a page that stays closed - the shop's "page not found" - until you open it in Access and security > Consent page.
• You choose what is offered. Each tool and prompt, or a whole group of them such as Orders - changes, can be switched off for connected assistants, for the built-in assistant, or both. A group switched off also holds back the tools a later update adds to it. Changes are flagged as such, which assistants use to ask you before making them.
• Every refusal is logged, in a security log that never contains a token or a secret.
• Tested before every release. Each version is installed and run on more than 30 PrestaShop versions (more than 70 PrestaShop and PHP combinations), attacked by more than 35 security tests on a live shop and driven through the back office by a real browser. The report is attached to every release.

Found a security issue? Please do not open an issue: report it privately, see SECURITY.md.

---

Tools

Grouped by back office page, each object's reads before its writes. ● reads only and is safe to repeat; ✎ changes data, one thing per call, and is flagged so assistants ask you before running it. The last column is the right the employee needs in Team › Permissions for the assistant to use the tool. Details of every tool are in docs/TOOLS.md.

🔌 Connection

🧾 Orders

📦 Catalog - Products

🗂️ Catalog - Categories

🏷️ Catalog - Brands

🚚 Catalog - Suppliers

🎨 Catalog - Attributes

📋 Catalog - Features

📎 Catalog - Files and taxes

📊 Stock

👥 Customers

📈 Statistics

📄 Content

🧩 Modules

🖌️ Appearance

⚙️ System

🔎 SEO

🤖 AEO

🛒 Sales

somcp_ping needs no right: it only tells the assistant which shop, account, language and currency it is connected to.

More than 10 prompts ship with the module, such as finding an order, changing an order status, checking stock, auditing SEO or getting recommended by AI assistants; each one is described in docs/TOOLS.md. The built-in assistant offers them too, each with its icon: those of the page you are on first, and all of them from the + of its field.

---

Need help?

• Documentation: the wiki covers requirements, installation, settings, each assistant and the built-in assistant. The same guide comes as a PDF, readme_en.pdf, with every release.
• A bug or an idea: open an issue.
• Installation, setup or a tool made for your shop: Novalo.
• What changed in each version: CHANGELOG.md.

---

For developers

How the module works (OAuth, MCP, multistore), how to install it from the sources, how to publish tools from your own module, how to contribute and where help is wanted: CONTRIBUTING.md.

Contributors

Everyone who helped build the module, the top contributor in the middle. The names and the counts are read from GitHub each time this page is shown, so they are always up to date. The settings page of the module shows the same list, read from GitHub, under Help and updates > Meet our contributors.

License

Academic Free License 3.0, like the rest of the Novalo modules.