Connect your store to Claude

You add your shop to Claude once, as a connector. After that you open a chat and ask, or pick a ready-made job from the menu.

Before you start, have the connector address from the module settings ready. It looks like https://yourshop.com/module/tellmyshop/mcp?token=…. If you didn't save it, generate a new one in the Start card.

Do I need a paid Claude account?

No. Any Claude account works, including a free one. You buy TellMyShop once, with no subscription.

Add the connector in Claude.ai

  1. Sign in at claude.ai.
  2. Open Settings > Connectors.
  3. Click Add custom connector.
  4. Name: for example "My shop".
  5. Address (URL): paste your connector address.
  6. Click Add.
  7. Open a new chat and check that the connector is switched on in the tools menu under the message box.

Now type:

Connect to my shop and tell me what you can do.

Claude answers with your PrestaShop version, languages and what it is allowed to do. Right after installation that means: read only.

The connector also works in the Claude desktop and mobile apps on the same account.

Ready-made jobs in the Claude menu

TellMyShop adds 14 ready-made jobs to Claude, for example Check my store and plan the fixes, Product texts and SEO in batches or Get ready for Black Friday. You find them in the connector's menu in the chat ("+" > your shop). Pick one and Claude follows a tested plan: it reads first, shows you a plan, then previews each change. The full list: Ready-made jobs. The module's Ready-made jobs card lists them too.

If your Claude app doesn't show the menu, just ask in plain words, for example "Check my store and tell me what to fix first". Claude fetches the same plan with the read-only tool ps_get_ready_job.

Test the connection

In the Start card click Test the connection again. The shop sends itself the same request Claude sends. If it fails, see the FAQ.

The Start card also shows when Claude connected for the first time.

A second connector for technical work

Changes to the look of the shop, modules and shop files work only through the service connector, which you add as a second, separate connector in Claude. Use the service address from the module settings and name it clearly, for example "My shop (service)". Switch it on in the chat only while you do technical work, and keep the daily connector for everything else.

The service connector works only from approved IP addresses (Claude.ai's addresses are on the list by default), only while one of the technical areas is switched on, and it expires after 30 days. You get an email when it is created.

First things to ask

All of these only read:

Run an SEO audit of my products and tell me the five most urgent fixes.

Which pages returned "not found" most often this month?

Why can't customers see product ref:ABC-1 in its category?

When you ask for a change, Claude shows a preview with the old and new values. Reply "yes" to save, or tell Claude what to adjust. A preview is valid for 30 minutes.

Keep the address private

Your connector address contains a secret key. Anyone who has it can use the connector. Don't paste it in emails or chats. If it leaks, generate a new one in the module settings (the old one stops working at once) and update the connector in Claude.

Working in a team

There is one daily connector address per shop. In a Claude team account an admin can add it once for everyone; with individual accounts each person adds the same address. All changes show up in the shop under Claude's employee account, not under the name of the person who approved them. When someone leaves the team, generate a new address.

Technical details

Header instead of URL token. A token in the URL can end up in server and proxy logs. Where the client supports headers, use the address without ?token= and send Authorization: Bearer <token>.

Claude Code

claude mcp add --transport http my-shop https://yourshop.com/module/tellmyshop/mcp \
  --header "Authorization: Bearer <daily-token>"

Check with claude mcp list. --scope project shares the server through .mcp.json (don't commit the token), --scope user uses it in every project. If you set an IP allowlist, add the IP of the machine running Claude Code.

Claude Desktop with a local configuration (shop on your own machine or behind a VPN). Edit claude_desktop_config.json (Settings > Developer > Edit Config):

{
  "mcpServers": {
    "my-shop": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://yourshop.local/module/tellmyshop/mcp",
               "--header", "Authorization: Bearer <daily-token>"]
    }
  }
}

Needs Node.js. The endpoint still requires HTTPS; use a trusted local certificate (for example mkcert). Requests without an Origin header (Claude Code, local bridges, Anthropic's servers) are accepted; a request with an Origin header must come from claude.ai or claude.com.

Transport. Streamable HTTP, JSON-RPC; protocol versions 2026-07-28 and older 2025-11-25, 2025-06-18, 2025-03-26. Ready-made jobs are MCP prompts (prompts/list, prompts/get) plus the read-only core tool ps_get_ready_job, which returns the same plan for clients without a prompt menu.

Rules the endpoint applies: connector switch on; HTTPS only; IP lockout after 20 failed attempts in 10 minutes (with an email to the owner); optional IP allowlist for both connectors; the service token additionally needs its own allowlist (default 160.79.104.0/21) and an active block 3–5; Origin check as above; hourly limits on calls and writes (adjustable in the settings). No OAuth in 2.6.0 (Roadmap). One token per connector; separate tokens per person are not planned for 2.6.0.

More: Security, Technical troubleshooting.

PrestaShop is a registered trademark of PrestaShop SA. Claude is a trademark of Anthropic. TellMyShop is not affiliated with either.

Last updated: 2026-10-04