
One Shop Manager for PrestaShop
io.github.oneshopmanagerPublished by GitHub account oneshopmanagerv1.0.0Updated Oct 24, 2026
PrestaShop 1.6 to 9: catalog, stock, orders, accounting; changes wait for your approval.
Overview
Local MCP server that lets an assistant read a PrestaShop store's catalog, orders and accounting and file changes for merchant approval.
- What you can do
- Read catalog, customer and order data from a local copy of the store
- Run sales, stock, restock and SEO analyses and review saved tables
- Review accounting periods, VAT, invoices and credit slips, and the operation journal
- Propose edits to prices, texts, SEO fields, categories, combinations and stock
- Propose product creation or duplication, order status and tracking changes, and undo past operations
- When to use it
- Useful for PrestaShop 1.6 to 9 merchants who want an assistant to answer questions about products, sales, stock and accounting, and to draft bulk edits such as price changes or missing meta descriptions, with a human approving each change.
- Requirements
- A commercial One Shop Manager desktop app (14-day trial) on macOS 11+ or Windows 10+, with the store connected through its PrestaShop module. AI access must be enabled in the app, which generates a bearer access key. The app must stay open on the store; connection is local over Streamable HTTP on 127.0.0.1 or stdio.
Installation
In SourceWeft
- Open One Shop Manager for PrestaShop in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
One Shop Manager — MCP server for PrestaShop 1.6 to 9
One Shop Manager lets Claude, or any other MCP client, read a PrestaShop store and prepare changes that the merchant reviews and approves before anything is sent to the store.
Français · Website · Claude + PrestaShop
What it is
One Shop Manager is a desktop application for macOS 11+ and Windows 10+. It copies the store to the computer and exposes it to MCP clients through a local MCP server. A small PrestaShop module connects the application to the store webservice.
- Server name:
one-shop-manager - Transport: Streamable HTTP on
http://127.0.0.1:47715/mcp(port can be changed), or stdio through the application executable (--mcp <ACCESS_KEY>) - Authentication: a bearer access key generated by the application
- Scope: the store currently open in the application
This repository contains documentation only. The One Shop Manager software is commercial and is not open source.
What the AI can read
Answers come from the local copy of the store, without querying the live site for every question.
- Catalog: products, texts in every language, categories, attributes and combinations
- Customers and orders: customer search and details, order list and details with gross margin
- Analysis: sales report, product sales and unsold products, stock valuation, restock, SEO audit, saved tables
- Accounting: period summary with VAT by country and rate, invoices and credit slips to check, entries for one order
- Journal: past operations and the status of AI proposals
What the AI can propose
- Prices, field values and cell edits, texts and SEO fields, categories and category texts
- Product creation and duplication (created disabled)
- Attributes, attribute values and combinations, combination stock
- Order status, tracking numbers, new orders for an existing customer
- Undoing a past operation
The full list, with every tool and its type, is in docs/tools.md.
The approval rule
Nothing is written to the store until the user opens the before/after preview and clicks Apply. Every propose_* tool computes the change and files it as a proposal in AI assistant › AI log inside the application; the AI has no tool that writes to the store. Applied changes can be undone from the journal (except created orders).
A read-only mode hides all proposal tools from the AI.
Quick start
- Download the 14-day free trial from oneshopmanager.com and connect your store.
- In the application: Settings › AI settings, card AI access (MCP): check Enable AI access, then click Test access.
- Connect your client:
- Claude Desktop: one button, Connect Claude Desktop, or the extension
prestashop-mcp.mcpbfrom the Releases - Claude Code: one command to paste
- Cursor
- Other MCP clients, including Codex
- Claude Desktop: one button, Connect Claude Desktop, or the extension
- Ask: "How many active products does my store have?" The application must stay open on that store.
Example requests
- "Which products in stock have not sold in the last 90 days?"
- "Lower their price by 15%, rounded to .90."
- "Write a meta description for the products in the Shoes category that have none."
- "Which paid orders have not shipped yet?"
- "Why is order XKBKNABJK unbalanced in accounting?"
More in examples/prompts.md.
Security
- AI access is disabled by default.
- The MCP connection is local to the computer and protected by an access key.
- Store credentials stay in the system keychain, out of the AI's reach.
- Only the data needed for a question is sent to the AI provider; with your own Claude, it goes directly to Anthropic.
- Nothing is written without approval, and everything can be undone.
Details in docs/security.md.
Compatibility
- PrestaShop 1.6, 1.7, 8 and 9
- macOS 11+ and Windows 10+
- Claude Desktop, Claude Code, Cursor, Codex and any MCP client
Links
- Website: https://oneshopmanager.com/en/
- Claude + PrestaShop: https://oneshopmanager.com/claude-prestashop
- AI assistant and MCP: https://oneshopmanager.com/en/features/prestashop-ai-assistant-mcp
- Video: https://oneshopmanager.com/promo.mp4
- Pricing: https://oneshopmanager.com/en/pricing
- Contact: [email protected]
License
The documentation in this repository is licensed under CC BY 4.0. One Shop Manager itself is commercial software.
Source: README.md at commit ba71250
Tools
0Version history
1- v1.0.0LatestOct 14, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts