# PrestaShop MCP connector

The PrestaShop connector brings your store's addresses, carriers, cart rules and attachments into Claude, ChatGPT, Cursor and Microsoft Copilot, so each person works on them as themselves and every change is logged.

Source: https://elaichi.ai/connectors/prestashop/

## Facts

| | |
| --- | --- |
| Application | PrestaShop |
| Category | Ecommerce |
| AI tools | 368 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once PrestaShop is connected

- List the cart rules that expire this month
- Update the delivery address on Maria Lopez's account
- Which carriers are currently active in the store?

## Connect PrestaShop in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick PrestaShop.
2. Optionally set Share with, then press Connect.
3. Paste a PrestaShop API key. One person generates a token in PrestaShop and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which PrestaShop tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## PrestaShop MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## PrestaShop MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## PrestaShop MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## PrestaShop MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## PrestaShop MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect PrestaShop to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a PrestaShop tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with PrestaShop through Elaichi

### Set up a promotion before it goes live

Marketing. Ask for a new cart rule with the code, the discount and the start and end dates, then read it back to check it before customers see it.

### Fix a delivery address before dispatch

Support. A customer writes in with a typo in their street name. Pull up the address, correct it and confirm it without opening the PrestaShop back office.

### Keep carrier details current

Operations. When a shipping partner changes its name, delivery times or coverage, update the carrier record in PrestaShop in one ask rather than clicking through settings.

### Find which discount codes are still running

Sales. List the active cart rules, see which ones expire this month and decide which to extend or retire before the next campaign.

### Attach a spec sheet or manual

Catalog. Add a new attachment for a product's documentation, or replace an outdated one, so customers download the right file from the product page.

### Clean up the address book

Store management. List addresses, spot duplicates and incomplete entries, and remove or correct them so orders ship to the right place.

## Elaichi vs Zapier MCP vs Composio for PrestaShop

All three can connect PrestaShop to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over PrestaShop tools | Allow or restrict single PrestaShop tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per PrestaShop call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect PrestaShop to Claude?

Connect PrestaShop in Elaichi first: paste the webservice API key from your PrestaShop back office, and the connection is ready. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Short, concrete asks such as "list cart rules expiring this month" work better than long sentences.

### Does PrestaShop work with ChatGPT and Cursor as well as Claude?

Yes. Once PrestaShop is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect PrestaShop once and every client sees it.

### What can an AI agent actually do with my PrestaShop data?

With PrestaShop connected, an agent can look up, create, update and delete customer addresses, carriers, cart rules and product attachments. In practice that means fixing a delivery address, setting up a discount code with its dates, updating a shipping partner's details or attaching a manual to a product, all from a chat.

### Does connecting PrestaShop give the AI access to my whole store?

No. The connector can only reach what the PrestaShop webservice key you entered is allowed to reach, and every call runs under the person who signed in to Elaichi. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what PrestaShop itself permits.

### Can my team share one PrestaShop connection?

Yes. One person connects PrestaShop with the store's API key and shares the connection with a team in Elaichi, so nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who changed a cart rule or an address, not a shared account.

### Can I stop an agent from deleting or changing things in PrestaShop?

Yes. Restrictions in Elaichi work per action, so you can allow reading PrestaShop addresses and cart rules while restricting delete or update, and apply that to a role or to one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a PrestaShop connection when someone leaves?

Offboarding a person in Elaichi ends their access to PrestaShop at once, in every client they used. A shared PrestaShop connection keeps working for everyone else on the team. If you want the store gone entirely, disconnecting PrestaShop once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the PrestaShop MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. PrestaShop is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for PrestaShop?

Yes. Both let Claude, ChatGPT or Cursor use PrestaShop. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every PrestaShop call.

### How is Elaichi different from Composio for PrestaShop?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to PrestaShop: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 368 PrestaShop tools

Every tool below is callable through https://api.elaichi.ai/mcp once PrestaShop is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all PrestaShop addresses** (List). List addresses (The Customer, Manufacturer and Customer addresses). Returns full records by default; supports filter, sort, and display.
- **Get single PrestaShop address by ID** (Get). Get one record from addresses (The Customer, Manufacturer and Customer addresses) by id.
- **Create a PrestaShop address** (Create). Create a record in addresses (The Customer, Manufacturer and Customer addresses). Send the fields wrapped as {"prestashop": {"address": {...}}}; the connector sends it as XML. Required: id_country, alias, lastname, firstname, address1, city.
- **Update a PrestaShop address by ID** (Update). Replace a record in addresses (The Customer, Manufacturer and Customer addresses) by id (PUT). Send the full record, including id, wrapped as {"prestashop": {"address": {...}}}. PUT replaces the whole record: send every field (as returned by get); it is validated like a create.

- **PrestaShop addresses partial update** (Update). Partially update a record in addresses (The Customer, Manufacturer and Customer addresses) by id (PATCH). Pass the record id as the path id, and send id plus only the fields to change, wrapped as {"prestashop": {"address": {...}}}.

- **Delete a PrestaShop address by ID** (Delete). Delete a record from addresses (The Customer, Manufacturer and Customer addresses) by id.
- **List all PrestaShop attachments** (List). List attachments (The product Attachments). Returns full records by default; supports filter, sort, and display.
- **Get single PrestaShop attachment by ID** (Get). Get one record from attachments (The product Attachments) by id.
- **Create a PrestaShop attachment** (Create). Create a record in attachments (The product Attachments). Send the fields wrapped as {"prestashop": {"attachment": {...}}}; the connector sends it as XML. Required: file, mime, name.
- **Update a PrestaShop attachment by ID** (Update). Replace a record in attachments (The product Attachments) by id (PUT). Send the full record, including id, wrapped as {"prestashop": {"attachment": {...}}}. PUT replaces the whole record: send every field (as returned by get); it is validated like a create.

- **PrestaShop attachments partial update** (Update). Partially update a record in attachments (The product Attachments) by id (PATCH). Pass the record id as the path id, and send id plus only the fields to change, wrapped as {"prestashop": {"attachment": {...}}}.

- **Delete a PrestaShop attachment by ID** (Delete). Delete a record from attachments (The product Attachments) by id.
- **List all PrestaShop carriers** (List). List carriers (The Carriers that perform deliveries). Returns full records by default; supports filter, sort, and display.
- **Get single PrestaShop carrier by ID** (Get). Get one record from carriers (The Carriers that perform deliveries) by id.
- **Create a PrestaShop carrier** (Create). Create a record in carriers (The Carriers that perform deliveries). Send the fields wrapped as {"prestashop": {"carrier": {...}}}; the connector sends it as XML. Required: name, active, delay.
- **Update a PrestaShop carrier by ID** (Update). Replace a record in carriers (The Carriers that perform deliveries) by id (PUT). Send the full record, including id, wrapped as {"prestashop": {"carrier": {...}}}. PUT replaces the whole record: send every field (as returned by get); it is validated like a create.

- **PrestaShop carriers partial update** (Update). Partially update a record in carriers (The Carriers that perform deliveries) by id (PATCH). Pass the record id as the path id, and send id plus only the fields to change, wrapped as {"prestashop": {"carrier": {...}}}.

- **Delete a PrestaShop carrier by ID** (Delete). Delete a record from carriers (The Carriers that perform deliveries) by id.
- **List all PrestaShop cart rules** (List). List cart rules (Cart rules management (discount, promotions, …)). Returns full records by default; supports filter, sort, and display.
- **Get single PrestaShop cart rule by ID** (Get). Get one record from cart rules (Cart rules management (discount, promotions, …)) by id.
- **Create a PrestaShop cart rule** (Create). Create a record in cart rules (Cart rules management (discount, promotions, …)). Send the fields wrapped as {"prestashop": {"cart_rule": {...}}}; the connector sends it as XML. Required: date_from, date_to, name.
- **Update a PrestaShop cart rule by ID** (Update). Replace a record in cart rules (Cart rules management (discount, promotions, …)) by id (PUT). Send the full record, including id, wrapped as {"prestashop": {"cart_rule": {...}}}. PUT replaces the whole record: send every field (as returned by get); it is validated like a create.

- **PrestaShop cart rules partial update** (Update). Partially update a record in cart rules (Cart rules management (discount, promotions, …)) by id (PATCH). Pass the record id as the path id, and send id plus only the fields to change, wrapped as {"prestashop": {"cart_rule": {...}}}.

- **Delete a PrestaShop cart rule by ID** (Delete). Delete a record from cart rules (Cart rules management (discount, promotions, …)) by id.
- **List all PrestaShop carts** (List). List carts (Customer’s carts). Returns full records by default; supports filter, sort, and display.
- **Get single PrestaShop cart by ID** (Get). Get one record from carts (Customer’s carts) by id.
- **Create a PrestaShop cart** (Create). Create a record in carts (Customer’s carts). Send the fields wrapped as {"prestashop": {"cart": {...}}}; the connector sends it as XML. Required: id_currency, id_lang.
- **Update a PrestaShop cart by ID** (Update). Replace a record in carts (Customer’s carts) by id (PUT). Send the full record, including id, wrapped as {"prestashop": {"cart": {...}}}. PUT replaces the whole record: send every field (as returned by get); it is validated like a create.

- **PrestaShop carts partial update** (Update). Partially update a record in carts (Customer’s carts) by id (PATCH). Pass the record id as the path id, and send id plus only the fields to change, wrapped as {"prestashop": {"cart": {...}}}.

- **Delete a PrestaShop cart by ID** (Delete). Delete a record from carts (Customer’s carts) by id.
- **List all PrestaShop categories** (List). List categories (The product categories). Returns full records by default; supports filter, sort, and display.
- **Get single PrestaShop category by ID** (Get). Get one record from categories (The product categories) by id.
- **Create a PrestaShop category** (Create). Create a record in categories (The product categories). Send the fields wrapped as {"prestashop": {"category": {...}}}; the connector sends it as XML. Required: active, name, link_rewrite.
- **Update a PrestaShop category by ID** (Update). Replace a record in categories (The product categories) by id (PUT). Send the full record, including id, wrapped as {"prestashop": {"category": {...}}}. PUT replaces the whole record: send every field (as returned by get); it is validated like a create.

- **PrestaShop categories partial update** (Update). Partially update a record in categories (The product categories) by id (PATCH). Pass the record id as the path id, and send id plus only the fields to change, wrapped as {"prestashop": {"category": {...}}}.

- **Delete a PrestaShop category by ID** (Delete). Delete a record from categories (The product categories) by id.
- **List all PrestaShop combinations** (List). List combinations (The product combinations). Returns full records by default; supports filter, sort, and display.
- **Get single PrestaShop combination by ID** (Get). Get one record from combinations (The product combinations) by id.
- **Create a PrestaShop combination** (Create). Create a record in combinations (The product combinations). Send the fields wrapped as {"prestashop": {"combination": {...}}}; the connector sends it as XML. Required: id_product, minimal_quantity.
- **Update a PrestaShop combination by ID** (Update). Replace a record in combinations (The product combinations) by id (PUT). Send the full record, including id, wrapped as {"prestashop": {"combination": {...}}}. PUT replaces the whole record: send every field (as returned by get); it is validated like a create.

- **PrestaShop combinations partial update** (Update). Partially update a record in combinations (The product combinations) by id (PATCH). Pass the record id as the path id, and send id plus only the fields to change, wrapped as {"prestashop": {"combination": {...}}}.

- **Delete a PrestaShop combination by ID** (Delete). Delete a record from combinations (The product combinations) by id.
- **List all PrestaShop configurations** (List). List configurations (Shop configuration, used to store miscellaneous parameters from the shop (maintenance, multi shop, email settings, …)). Returns full records by default; supports filter, sort, and display.
- **Get single PrestaShop configuration by ID** (Get). Get one record from configurations (Shop configuration, used to store miscellaneous parameters from the shop (maintenance, multi shop, email settings, …)) by id.
- **Create a PrestaShop configuration** (Create). Create a record in configurations (Shop configuration, used to store miscellaneous parameters from the shop (maintenance, multi shop, email settings, …)). Send the fields wrapped as {"prestashop": {"configuration": {...}}}; the connector sends it as XML. Required: name.
- **Update a PrestaShop configuration by ID** (Update). Replace a record in configurations (Shop configuration, used to store miscellaneous parameters from the shop (maintenance, multi shop, email settings, …)) by id (PUT). Send the full record, including id, wrapped as {"prestashop": {"configuration": {...}}}. PUT replaces the whole record: send every field (as returned by get); it is validated like a create.

- **PrestaShop configurations partial update** (Update). Partially update a record in configurations (Shop configuration, used to store miscellaneous parameters from the shop (maintenance, multi shop, email settings, …)) by id (PATCH). Pass the record id as the path id, and send id plus only the fields to change, wrapped as {"prestashop": {"configuration": {...}}}.

- **Delete a PrestaShop configuration by ID** (Delete). Delete a record from configurations (Shop configuration, used to store miscellaneous parameters from the shop (maintenance, multi shop, email settings, …)) by id.
- **List all PrestaShop contacts** (List). List contacts (Shop contacts). Returns full records by default; supports filter, sort, and display.
- **Get single PrestaShop contact by ID** (Get). Get one record from contacts (Shop contacts) by id.
- ...and 318 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
