get_productsLABSCO SUMMARY
Shop operations, not just the catalogue.
It reaches the maintenance work as well as the catalogue — installing a module, clearing the cache after a change, fixing a menu link — which is what a shop owner's day actually consists of. Price and stock have their own operations, so a bulk repricing does not have to go through a full product update.
What it is
A management connection to a PrestaShop store covering both the catalogue and the platform around it. Products, categories, customers and orders are the core; modules, cache, themes and the main navigation menu are reachable in the same session.
What you get
- Product retrieval that handles one product by ID or a filtered list, optionally enriched with stock and category detail
- Products created, edited and removed, with price and stock as their own operations
- Categories retrieved with hierarchy filtering, created, edited and removed
- Customers listed, filtered, created and updated
- Orders listed and filtered, their status changed, and the available statuses read
- Modules listed and inspected, installed, activated or deactivated
- Cache cleared and its status read, theme settings updated, and the main menu's links read, added and edited
- A connection test, for confirming the store is reachable before anything else
Requirements
A PrestaShop store you administer, reachable over its web service API with credentials that permit the resources you intend to touch.
Setup effort
Build from source — clone the repository, then follow the project's own run instructions
USE CASES
01
Repricing or restocking without touching everything else
Change price and stock as their own operations, so a bulk update cannot accidentally overwrite descriptions or category assignments.
02
Answering a question about an order
Find the order, read the statuses available, and move it to the right one — support work done in the conversation where the question arrived.
03
Adding a product line
Create the products, place them in the right category, and create the category first if it does not exist yet.
04
Handling a customer record
Find the customer, correct their details, or create the account — without an admin login for a change of one field.
05
Installing and switching a module on
List what is installed, look up the module by name, install it and activate it — the maintenance loop that normally means a back-office session.
06
Fixing the shop after a change
Clear the cache and confirm its status, adjust a theme setting, and correct the main menu links that a change left pointing at nothing.
29 tools
Listed in project docs. Your client may show a different list.
create_productupdate_productdelete_productupdate_product_stockupdate_product_priceget_categoriescreate_categoryupdate_categorydelete_categoryget_customerscreate_customerupdate_customerget_ordersupdate_order_statusget_order_statesget_modulesget_module_by_nameinstall_moduleupdate_module_statusget_main_menu_linksupdate_main_menu_linkadd_main_menu_linkclear_cacheget_cache_statusget_themesupdate_theme_settingtest_connectionget_shop_infoBEFORE YOU INSTALL
What to know first
Tools you get
29 tools named in the project's documentation.
Requires
PRESTASHOP_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
<YOUR_PATH_TO_PYTHON> -m prestashop_mcp.prestashop_mcp_serverMCP Clients
Claude Desktop — Linux, macOS
CLAUDE DESKTOP — LINUX, MACOS · JSON
{
"mcpServers": {
"prestashop": {
"command": "<YOUR_PATH_TO_PRESTASHOP_MCP>/venv_prestashop/bin/python",
"args": [
"-m",
"prestashop_mcp.prestashop_mcp_server"
],
"cwd": "<YOUR_PATH_TO_PRESTASHOP_MCP>",
"env": {
"PRESTASHOP_SHOP_URL": "<YOUR_PRESTASHOP_SHOP_URL>",
"PRESTASHOP_API_KEY": "<YOUR_PRESTASHOP_API_KEY>"
}
}
}
}
