Connect a module
Microsoft Clarity
ShopMCP connects multiple Microsoft Clarity projects to Claude, ChatGPT, Cursor, and other MCP clients through encrypted project-level Data Export API tokens, then layers ecommerce-focused analysis over Clarity recordings and dashboards.
One token per Clarity project
Microsoft Clarity project admins generate Data Export API tokens inside each project. ShopMCP stores each token as a separate encrypted connection so one workspace can analyze several Clarity projects at once.
1. Generate a Clarity token
In Microsoft Clarity, open the project you want to connect, then go to Settings - Data Export and generate a new API token for ShopMCP.
- Only Clarity project admins can manage Data Export API tokens.
- Give the token a recognizable name such as
shopmcp-production. - Repeat this for every Clarity project you want ShopMCP to access.
2. Connect projects in ShopMCP
Open Settings - Integrations, choose Microsoft Clarity, then paste the project name and API token. Use bulk paste when an agency or portfolio workspace needs to add several projects.
Verification uses the project quota
Clarity's documented Data Export API allows 10 requests per project per day. ShopMCP verifies a token with a small one-day OS insight request, so connect tokens deliberately.
3. What you can ask
| Goal | Example prompt | What ShopMCP reads |
|---|---|---|
| Build a growth scorecard | Create a Clarity growth opportunity scorecard across checkout, PDP, mobile, paid landing pages, and technical errors. | Dashboard answers, recording cohorts, and a prioritization model for revenue proximity, segment concentration, repeatability, and confidence. |
| Prioritize recordings | Find the 20 Clarity recordings I should watch first for checkout friction across all projects. | Recording cohorts for rage clicks, dead clicks, quick backs, JavaScript errors, and checkout abandonment. |
| Audit checkout | Audit checkout UX for the AU and US stores over the last 7 days. | Dashboard answers plus representative recordings scoped to checkout URLs and conversion-friction signals. |
| Audit product pages | Find mobile PDP friction for products in the roof-rack category. | Product-page recordings and dashboard answers filtered by URL, device, product name, brand, or price range. |
| Find UX friction | Show recent mobile sessions with rage clicks on checkout across all Clarity projects. | Recording samples filtered by device, URL, and rage-click signals. |
| Compare projects | Compare traffic, device mix, and dead-click counts for the AU and US projects over the last 24 hours. | Live insights broken down by project and dimensions such as Device or URL. |
| Investigate errors | List sessions with JavaScript errors on product pages since yesterday. | Recording samples filtered by visited URLs and JavaScript error signals. |
| Ask dashboard questions | Which sources had the highest engagement time in the last 3 days? | Microsoft Clarity's dashboard query MCP endpoint for the selected project. |
4. Limits to know
- The documented Data Export API returns data for the previous 1 to 3 days.
- Each live-insights request can include up to three dimensions.
- The documented response is capped at 1,000 rows and does not paginate.
- The recordings and dashboard-query tools use Microsoft's official Clarity MCP endpoints.
- Growth scorecards use a bounded upstream plan so broad multi-project audits stay practical in MCP clients.
- ShopMCP's ecommerce audit tools can run against a selected project or, in clients that expose tool arguments, across connected projects with
store: "all".
5. Ecommerce growth prompts
Run a Clarity growth opportunity scorecard for all projects and tell me where UX work is most likely to grow revenue.Audit checkout friction on mobile for the last 7 days and give me the recordings to watch first.Find PDP friction for products over $150 with strong ratings but weak add-to-cart behavior.Show paid landing pages with quick backs, rage clicks, dead clicks, or JavaScript errors.Compare checkout health across connected Clarity projects using store: "all".
6. How ShopMCP differs from the official MCP
| Capability | Microsoft official MCP | ShopMCP Clarity |
|---|---|---|
| Project setup | One configured project token per MCP server instance. | Connect multiple encrypted Clarity project tokens in one workspace. |
| Raw dashboard questions | Available. | Available, with the same Microsoft MCP endpoint. |
| Recording samples | Available. | Available, plus ecommerce cohort builders for the recordings worth watching first. |
| Live Data Export rows | Not exposed as an official MCP tool. | Available as an explicit quota-aware read tool. |
| Checkout and PDP audits | No dedicated ecommerce tools. | Dedicated checkout and product-page audit tools. |
| Growth prioritization | No dedicated scorecard. | Bounded growth scorecard for checkout, PDP, mobile, paid landing-page, and technical-error opportunities. |
| Multi-project comparison | Manual switching or multiple MCP setups. | Use store: "all" when multiple Clarity projects are connected. |