Connect your own AI client
You can connect your own Claude to StorePilot and ask it about your shops directly — "why did conversions drop last week", "what broke on the checkout page yesterday", "which products nobody is looking at". StorePilot is a remote MCP server (Model Context Protocol), so the connection is made in Claude's own settings and the data flows to your AI client, on your instruction.
This is not StorePilot calling an AI on your behalf. Nothing here is enabled by default, and nothing is sent anywhere until you connect a client and choose which sites it may read.
The address
https://api.store-pilot.net/mcp
Claude (web, desktop, mobile)
- Open Settings → Connectors → Add custom connector.
- Paste the address above.
- Claude opens StorePilot's sign-in, then a consent screen.
- Tick the sites this connection may read, and allow.
Claude Code
claude mcp add --transport http storepilot https://api.store-pilot.net/mcp
Then run /mcp inside a session and sign in through the browser.
:::note What changed on 11 September 2026
A connected client now also reads names, chat transcripts, survey free text, visitor and session identifiers, and a description of a recorded visit. Because consent had named the narrower list, every existing connection was ended — your client will ask you to sign in again, and the consent screen will show the new list before you approve it.
:::
What it can read
| Traffic | sessions, pageviews, bounce, top pages, devices, browsers, countries, traffic channels |
| Commerce | revenue, average order value, abandonment rate, orders, abandoned checkouts, per-product performance |
| Issues | errors grouped by fingerprint, with their stacks, releases and occurrence counts |
| Health | uptime, incidents, response times |
| Findings | the derived insight cards, and the daily fact sheet behind them |
| Visits | recorded visits — score, pages, duration, device, errors — and the narrative summary written about one |
| Visitors | who came back, on what device, from where, and what they did |
| Chats | transcripts from the storefront chat widget |
| Surveys | scores, distributions, and the free text people typed |
It sees the names and contact details on a checkout or an order, chat transcripts, survey answers including free text, and the pseudonymous identifiers that link a visit to a purchase. Raw form contents ride only where you hold the admin role — the same bar as the dashboard's own export — and any field whose name looks like an address is masked even then.
What it never receives
Postal addresses and postcodes. Not because a tool declines to send them — because they are never stored. The platform writes a marker in place of a street and a postcode before the record is saved, so there is nothing for any reader to be given.
IP addresses. Not even the truncated form the platform keeps for its own country lookups.
Session-recording footage. A recorded visit is described — its pages, duration, device, errors, and the narrative summary — and linked back to the player here. The recording itself is never returned: one visit runs to tens of megabytes of frames, and a partial one would be a replay claiming a visit it does not contain.
That is not a setting — it is how the data is built. Each tool returns a fixed set of fields named in the code, so a field that is not on the list cannot be returned by adding a parameter.
Access is read-only
There is no tool that writes, deletes or changes anything. A connected client cannot resolve an issue, delete an order or edit a setting.
The sites are the permission
A connection reads only the sites you ticked when you connected it, and only while you are still a member of the organization those sites belong to. Two consequences worth knowing:
- Remove somebody from an organization and their AI client loses access to it within a minute, without anybody touching the connection.
- A site you add later is not included. Connect the client again to name it.
Disconnecting
Your profile → Connected AI clients → Disconnect. It stops reading immediately.
Disconnecting is separate from signing out: "Sign out everywhere else" ends your browser sessions and leaves these connections running.
Who is the sub-processor
The provider of the AI client you connect — Anthropic, if you connect Claude — receives this data because you instructed it to. They are your sub-processor for that data, not ours, and they belong in your own record of processing. See the Data Processing Agreement §4.