Connect PrestaShop to Claude: Automate Products and Customer Support

If you need to connect PrestaShop to Claude to automate inventory management, resolve customer support tickets, or generate promotional campaigns, you need a Model Context Protocol (MCP) server. This server acts as the translation layer between Claude's JSON-RPC tool calls and PrestaShop's Web Service API. You can either build and maintain this infrastructure yourself, or use a managed integration platform like Truto to dynamically generate a secure, authenticated MCP server URL. If your team uses ChatGPT, check out our guide on connecting PrestaShop to ChatGPT or explore our broader architectural overview on connecting PrestaShop to AI Agents.

Giving a Large Language Model (LLM) read and write access to a sprawling e-commerce ecosystem like PrestaShop is an engineering challenge. You have to handle Web Service Key authentication, map massive XML-based schemas to MCP tool definitions, and deal with PrestaShop's strict relational data constraints. Every time you need to expose a new resource to your AI assistant, you have to update your server code, redeploy, and test the integration.

This guide breaks down exactly how to use Truto to generate a secure, managed MCP server for PrestaShop, connect it natively to Claude Desktop, and execute complex e-commerce workflows using natural language.

The Engineering Reality of the PrestaShop API

A custom MCP server is a self-hosted integration layer. While the open MCP standard provides a predictable way for models to discover tools, the reality of implementing it against PrestaShop's Web Service API is painful. PrestaShop is built on a heavily relational, XML-first architecture that requires specific formatting and careful operational sequencing.

If you decide to build a custom MCP server for PrestaShop, here are the specific integration challenges you will face:

XML Payload Translation and Schema Wrapping PrestaShop's Web Service API relies heavily on XML for mutations (POST, PUT, PATCH). When an LLM generates a tool call, it outputs standard JSON. Your MCP server must translate this JSON into valid XML. Furthermore, PrestaShop requires payloads to be wrapped in a specific root element format (e.g., <prestashop><order>...</order></prestashop>). Truto's managed MCP server handles this translation behind the scenes, allowing the LLM to send JSON wrapped as {"prestashop": {"order": {...}}}, which is then safely converted to the required XML for the upstream API.

Orphaned Records and Missing Cascade Deletes PrestaShop does not always cascade deletes. For example, if you delete an order via the API, the associated order_details, order_histories, order_invoices, and order_payments records remain in the database as orphaned data. An LLM instructed to "delete an order" will naively call the order deletion tool, causing data integrity issues. A well-architected integration must expose tools for all these related entities so the LLM can orchestrate a multi-step cleanup, or handle the cascading logic explicitly in a proxy layer.

Strict Query Parameters for Display By default, PrestaShop list endpoints only return the id of the resources. To get meaningful data for an LLM to analyze, you must append specific query parameters like display=full or display=[id,name,price]. Your MCP tool schemas must explicitly instruct the model on how to use these query parameters, otherwise Claude will consistently return empty or useless lists.

Rate Limits and 429 Handling It is critical to understand that Truto does not retry, throttle, or apply backoff on rate limit errors. When PrestaShop's API returns an HTTP 429, Truto passes that error directly to the caller. Truto normalizes upstream rate limit info into standardized headers (ratelimit-limit, ratelimit-remaining, ratelimit-reset) per the IETF spec. Your MCP client or agent orchestrator is responsible for implementing retry and exponential backoff logic. Do not expect the MCP server to absorb these errors automatically.

Generating a PrestaShop MCP Server

Truto dynamically generates MCP tools from PrestaShop's API documentation and your connected account's configuration. The tools are served over a standard JSON-RPC 2.0 endpoint.

You can generate the MCP server URL using either the Truto UI or the API.

Method 1: Via the Truto UI

1. Navigate to the Integrated Accounts page in your Truto dashboard and select your connected PrestaShop account.
2. Click the MCP Servers tab.
3. Click Create MCP Server.
4. Select your desired configuration (e.g., name the server, filter to specific tags or read-only methods, set an expiration date).
5. Copy the generated MCP server URL (it will look like https://api.truto.one/mcp/a1b2c3d4e5f6...).

Method 2: Via the Truto API

You can programmatically generate MCP servers for your users by sending a POST request to Truto's API. This is ideal for provisioning agent access on the fly.

curl -X POST https://api.truto.one/integrated-account/{integrated_account_id}/mcp \
  -H "Authorization: Bearer YOUR_TRUTO_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "PrestaShop Claude Integration",
    "config": {
      "methods": ["read", "write"]
    }
  }'

The response will contain the secure, tokenized URL:

{
  "id": "mcp_123456789",
  "name": "PrestaShop Claude Integration",
  "config": { "methods": ["read", "write"] },
  "expires_at": null,
  "url": "https://api.truto.one/mcp/a1b2c3d4e5f6..."
}

Connecting the MCP Server to Claude

Once you have your Truto MCP URL, you can connect it to Claude in two ways, depending on how you use the model.

Option A: Via the Claude UI (Enterprise / Team)

If you are using Claude's web interface on a qualifying plan:

1. Navigate to Settings -> Integrations -> Add MCP Server.
2. Name your connection (e.g., "PrestaShop").
3. Paste the Truto MCP URL you copied earlier.
4. Click Add. Claude will instantly connect, perform a handshake, and list the available PrestaShop tools.

Option B: Via the Claude Desktop Config File

For local development or standard Claude Desktop usage, you can configure the MCP connection using the official SSE (Server-Sent Events) proxy.

Open your claude_desktop_config.json file (typically found at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS) and add the following configuration:

{
  "mcpServers": {
    "prestashop": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-sse",
        "https://api.truto.one/mcp/a1b2c3d4e5f6..."
      ]
    }
  }
}

Restart Claude Desktop. You will see a new hammer icon indicating that the PrestaShop tools are loaded and ready to use.

sequenceDiagram
    participant Claude as Claude Desktop
    participant MCP as Truto MCP Server
    participant TrutoProxy as Truto Proxy API
    participant PrestaShop as PrestaShop API
    
    Claude->>MCP: Call tools/call (update_a_presta_shop_order_state_by_id)
    MCP->>TrutoProxy: Map flat args to JSON schema (body & query)
    TrutoProxy->>PrestaShop: Translate JSON to XML & Execute PUT
    PrestaShop-->>TrutoProxy: Return 200 OK (XML)
    TrutoProxy-->>MCP: Translate XML to JSON
    MCP-->>Claude: Return MCP Result Content

PrestaShop Hero Tools for Claude

Truto exposes dozens of PrestaShop endpoints, but here are the highest-leverage tools for automating e-commerce operations.

list_all_presta_shop_orders

Retrieves a list of customer orders. Because Truto sets up default configurations, it returns full records by default.

"Claude, list all the recent PrestaShop orders. Show me the order ID, the customer ID, and the total paid for the last 5 orders."

update_a_presta_shop_order_state_by_id

Updates the state of an existing order (e.g., from 'Payment accepted' to 'Shipped'). You must send the full record wrapped in the PrestaShop JSON structure.

"Update the order state for order ID 1042 to 'Shipped'. Make sure to wrap the payload in {"prestashop": {"order_state": {...}}} format."

get_single_presta_shop_customer_by_id

Fetches detailed information about a specific customer, which is critical for support workflows where you only have an order ID and need the buyer's contact info.

"Fetch the customer details for customer ID 88 to verify their shipping email address."

create_a_presta_shop_cart_rule

Creates a new discount or promotion rule. The payload must be wrapped as {"prestashop": {"cart_rule": {...}}}. Required fields include date_from, date_to, and name.

"Create a new cart rule called 'Summer Sale 2026' valid for the next 30 days that applies a 15% discount."

delete_a_presta_shop_order_by_id

Deletes an order from the database. Note that PrestaShop does not cascade this operation automatically. The LLM must be instructed to delete associated details first if a clean purge is required.

"Delete order ID 901. Before you do, make sure to find and delete any associated order details and invoices so we don't leave orphaned records."

To view the complete inventory of available PrestaShop tools, schemas, and required fields, visit the Truto PrestaShop Integration Page.

Workflows in Action

With the MCP server connected, Claude can now execute multi-step workflows by reasoning about the required tools and executing them in sequence.

Scenario 1: Customer Order Inquiry and Fulfillment Update

Support teams waste hours cross-referencing helpdesk tickets with the e-commerce backend. Claude can act as an autonomous support agent.

"A customer emailed us asking why order ID 405 is delayed. Please check the order status, verify the customer's email address, and if the order is stuck in 'Payment accepted', update the state to 'Waiting for transfer' so the warehouse can proceed."

Tool Execution Sequence:

1. list_all_presta_shop_orders (Filtered by ID 405 to get the current order state and id_customer).
2. get_single_presta_shop_customer_by_id (Using the extracted id_customer to retrieve and verify the email address).
3. update_a_presta_shop_order_history_by_id (Writing the new state ID to the order history to trigger the 'Waiting for transfer' status).

Result: Claude responds to the user confirming the customer's email, explaining that the status was successfully bumped, and the warehouse has been unblocked.

Scenario 2: Launching a Flash Sale Campaign

Marketing teams often need to spin up promotions quickly without logging into the clunky backend admin panel.

"We need to run a flash sale immediately. Create a new cart rule called 'Flash 20' valid from today until tomorrow. Set the discount to 20%."

Tool Execution Sequence:

1. create_a_presta_shop_cart_rule (Claude constructs the JSON payload: {"prestashop": {"cart_rule": {"name": "Flash 20", "date_from": "...", "date_to": "...", "reduction_percent": "20"}}}). Truto's proxy layer automatically translates this into the XML format required by PrestaShop's Web Service.

Result: Claude creates the discount code and returns the new cart_rule_id to the user, ready to be shared on social media.

Scenario 3: Safely Purging Fraudulent Orders

Handling fraud in PrestaShop requires careful database management due to the lack of cascading deletes.

"We have identified order ID 992 as fraudulent. Delete the order completely. Make sure you don't leave any orphaned order details or invoices behind."

Tool Execution Sequence:

1. list_all_presta_shop_order_details (Filtered by id_order=992 to get all line items).
2. delete_a_presta_shop_order_detail_by_id (Called in a loop for each line item found).
3. list_all_presta_shop_order_invoices (Filtered by id_order=992).
4. delete_a_presta_shop_order_invoice_by_id (Deletes the associated invoice).
5. delete_a_presta_shop_order_by_id (Finally, deletes the parent order record).

Result: Claude methodically cleans out the relational data before destroying the parent record, ensuring your PrestaShop database remains clean and free of orphaned rows.

Security and Access Control

Giving an AI agent access to a live e-commerce database carries inherent risk. Truto provides strict, declarative controls at the MCP server level to ensure Claude only does what it is authorized to do.

• Method Filtering: Use config.methods during server creation to restrict access. Passing ["read"] will only expose GET and LIST tools, preventing Claude from accidentally modifying or deleting products.
• Tag Filtering: Use config.tags to limit the scope of the server. You can restrict the MCP server to only expose tools related to customers or orders, hiding sensitive configuration or employee endpoints.
• Token Expiration: The expires_at parameter allows you to create temporary MCP servers. If you are spinning up an agent for a specific migration task, you can set the token to expire in 24 hours. A Durable Object alarm will automatically purge the server configuration and KV entries when the time is up.
• Secondary Authentication: By setting require_api_token_auth: true, the MCP server will demand a valid Truto API token in the Authorization header. This ensures that even if the MCP URL is leaked in logs, unauthorized users cannot execute tools.

Moving Forward with AI-Driven E-Commerce

Building a custom MCP server for PrestaShop requires deep knowledge of XML parsing, relational data cleanup, and Web Service Key authentication. Every time PrestaShop updates an endpoint, your custom code breaks.

By leveraging Truto's dynamically generated MCP servers, you offload the maintenance burden of schema mapping and authentication. You get a secure, stateless URL that gives Claude immediate, structured access to your e-commerce data - allowing your engineering team to focus on building agentic workflows instead of maintaining API wrappers.