claude-ecom MCP — Use Cases, Install & Live Demo

Why use it

Key features

CSV in, structured review out
KPI decomposition (revenue = traffic × CVR × AOV)
Python-backed calculations for accuracy
Prioritized findings, not a wall of charts
Next-actions list tied to findings

Live Demo

What it looks like in practice

claude-ecom-skill.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "claude-ecom-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/takechanman1228/claude-ecom",
        "~/.claude/skills/claude-ecom"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "claude-ecom-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/takechanman1228/claude-ecom",
        "~/.claude/skills/claude-ecom"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "claude-ecom-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/takechanman1228/claude-ecom",
        "~/.claude/skills/claude-ecom"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "claude-ecom-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/takechanman1228/claude-ecom",
        "~/.claude/skills/claude-ecom"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "claude-ecom-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/takechanman1228/claude-ecom",
        "~/.claude/skills/claude-ecom"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "claude-ecom-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/takechanman1228/claude-ecom",
          "~/.claude/skills/claude-ecom"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add claude-ecom-skill -- git clone https://github.com/takechanman1228/claude-ecom ~/.claude/skills/claude-ecom

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use claude-ecom

Weekly sales review in 10 minutes instead of 2 hours

👤 DTC founders, e-commerce managers ⏱ ~15 min beginner

When to use: Monday morning review of last week's numbers.

Prerequisites

Orders CSV export from Shopify/WooCommerce/etc. — Any platform's standard order export works; column mapping is flexible
Python available locally — python3 --version; skill uses a local Python env
Skill installed — git clone https://github.com/takechanman1228/claude-ecom ~/.claude/skills/claude-ecom

Flow

Hand over the CSV

Use claude-ecom. Here's last week's orders.csv — do a KPI decomposition and tell me what moved.✓ Copied

→ Revenue, CVR, AOV numbers with week-over-week deltas
Ask for findings

Rank the top 3 findings by impact. Be specific — named SKUs, traffic sources, time windows.✓ Copied

→ Findings with data points, not 'revenue went up'
Extract actions

For each finding, propose one concrete action I can take this week.✓ Copied

→ Action list I could paste in a Monday standup

Outcome: A weekly review I actually read.

Pitfalls

Garbage CSVs produce garbage reviews — Clean the export first — merge refunds, exclude test orders

Combine with: filesystem

Understand why a specific SKU is underperforming

👤 Product managers, merchandisers ⏱ ~20 min intermediate

When to use: A hero SKU suddenly slowed down and you need to know whether it's traffic, conversion, or pricing.

Flow

Filter to SKU

Use claude-ecom. Focus on SKU SHIRT-BLK-M for the last 60 days. Decompose revenue into traffic × CVR × AOV and compare to the prior 60.✓ Copied

→ Decomposition with clear delta per factor
Check channel split

Is the drop concentrated in one channel or across all?✓ Copied

→ Channel breakdown with concentration analysis

Outcome: A diagnosis, not a vibe.

Customer cohort retention report from order data

👤 Growth teams watching LTV ⏱ ~30 min intermediate

When to use: Quarterly review of cohort repeat rates.

Flow

Cohort the data

Use claude-ecom. Build a monthly acquisition-cohort retention table — orders/customer by month since first order.✓ Copied

→ Triangular retention table
Compare cohorts

Which cohort is best? Worst? What's different about them?✓ Copied

→ Hypotheses grounded in the data

Outcome: A retention view you could share with an investor.

Pitfalls

Short data windows distort recent cohorts — Flag cohorts with <3 months of history as provisional

Combinations

Pair with other MCPs for X10 leverage

claude-ecom-skill + filesystem

Point at a folder of weekly CSVs for automated trend analysis

Run the weekly review for each CSV in data/weekly/ and build a running dashboard.✓ Copied

claude-ecom-skill + bigquery-server

Instead of CSVs, pull from a warehouse

Query BigQuery for last week's orders and feed into claude-ecom for the review.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
load_csv	path, column mapping	Starting any analysis	local
kpi_decompose	date range	Weekly / monthly review	local Python
rank_findings	analysis output	After decomposition	0
cohort_table	cohort granularity	Retention analysis	local

Cost & Limits

What this costs to run

API quota: None
Tokens per call: Moderate — summary tables only, not raw rows
Monetary: Free (needs local Python)
Tip: Aggregate in Python; never paste raw orders rows into prompts.

Security

Permissions, secrets, blast radius

Credential storage: None

Data egress: Order summaries and findings are sent to Claude API; raw rows can stay local if you keep aggregation server-side

Order data often includes customer PII. Mask or exclude email/name/address columns before analysis.

Troubleshooting

Common errors and fixes

Python deps missing

The skill uses pandas; run pip install -r ~/.claude/skills/claude-ecom/requirements.txt

Verify: python -c 'import pandas'

Column mapping fails

Standard Shopify/Woo exports work out of the box. For custom exports, supply a column map in the prompt.

Wild numbers in the output

Check for duplicate order rows or non-currency values in the revenue column

Alternatives

claude-ecom vs others

Alternative	When to use it instead	Tradeoff
Looker Studio / Metabase dashboards	You want persistent dashboards, not one-shot reviews	Setup cost; no LLM-generated narrative
Shopify's own reports	Quick built-in views	Shallow; no cross-store or cohort analysis

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills