Customer Info includes a built-in MCP server (Model Context Protocol) that lets Claude — or any MCP client — answer questions about your customers directly from your store. Instead of copying data into a chat window, you connect once by URL and ask questions in plain English.
It is read-only. There are no write tools: saving a customer, switching users and the settings endpoints are deliberately not exposed.
⚠️ Test on Staging First
Connecting this grants an AI client access to personal customer data — names, addresses, phone numbers, order history and support conversations. Try it on a staging site before enabling it on a production store, and make sure the access fits your privacy policy.
✅ Requirements
- WooCommerce active — the tools return an error without it.
- HTTPS — required by the OAuth spec and by Claude’s connector.
- Pretty permalinks — the authorize page and discovery documents need them.
- A WordPress account with the manage_woocommerce capability (shop manager or administrator).
🔌 Connecting Claude
Add this URL as a custom connector in Claude, replacing the domain with your own store:
https://your-store.com/wp-json/customer-info-mcp/v1/mcp
Claude then walks you through the rest — it discovers the store’s authorization server, registers itself, sends you to a WordPress login and an Approve screen, and exchanges the result for an access token. Nothing needs to be installed locally, and teammates connect the same way with their own accounts.
🧰 What Claude Can Ask For
| Tool | What it returns |
|---|---|
| search_customers | Finds accounts by partial email, name or username — the starting point for a vague identifier. |
| get_customer_summary | The full 360-degree profile: identity, addresses, account age, lifetime value, order and subscription counts, support volume and wp-admin links. |
| get_customer_orders | Orders newest first, with line items, totals, refunds, status, coupons and payment method. |
| get_customer_subscriptions | Subscriptions with status, next renewal, recurring total, and licence activation limits when WooCommerce API Manager is active. |
| get_customer_clv | Revenue analysis: gross and net lifetime value, average order value, first and last order dates, and revenue per year. |
| get_support_history | Past Help Scout and Intercom conversations merged into one list, newest first. |
In practice you just ask — who is this customer, where is their licence being used, are they at risk of churning — and Claude picks the right tools.
🔐 How Access Is Secured
- Every token resolves to the real WordPress user who approved it, so every request is attributable to a person.
- Access requires the manage_woocommerce capability — the same permission the dashboard requires.
- Access tokens last 1 hour; refresh tokens last 30 days and are rotated on every use, so a replayed token is rejected.
- Access is per-user and individually revocable.
- A daily cron prunes expired codes, tokens and abandoned client registrations.
🧪 Other Ways to Connect
The endpoint also accepts standard WordPress authentication, so an application password over HTTP Basic works without going through OAuth — handy for a local client or a quick test. Create one at Users → Profile → Application Passwords; it is a revocable token, not your login password.