\n\n# Tenpo\n\n**The operator that runs alongside your store.**\n\nMost \"AI for e-commerce\" tools answer questions about your dashboard.\nTenpo runs your dashboards *for* you — across every platform, every minute, in plain English.\n\n[](https://www.npmjs.com/package/@tenpo/mcp)\n[](LICENSE)\n\n[**Get started in 2 lines →**](#install-in-2-lines) · [**See it think →**](#how-tenpo-thinks) · [**What it covers →**](#what-tenpo-covers)\n\n
\n\n---\n\n## The problem every store owner has\n\nYour orders are in Shopify. Your marketing is split across Meta, Google, and TikTok. Customer support lives in Gorgias. Email is in Klaviyo. Inventory is somewhere else. Accounting is in Xero.\n\nYou can see that revenue dropped. You can't easily see **why**. Is it a stock issue? An ad problem? A supplier delay? A churn wave? You'd need hours of cross-referencing — and most store owners don't have those hours.\n\nDecisions get made on gut feel. Problems get spotted late. Opportunities get missed entirely.\n\n---\n\n## What Tenpo is\n\nNot a dashboard. Not a chatbot. **An operator that runs your store next to you.**\n\nWhen you ask Tenpo something, it doesn't look up a pre-calculated answer. It queries your live data across every connected platform, traces the cause back through every related signal, attaches a financial impact, and tells you exactly what to do — in one message.\n\nIt's like having a business partner who:\n\n- Has memorised every order, product, customer, campaign, and supplier — once you connect them\n- Spots problems before they become expensive\n- Connects dots no human analyst would realistically cross-reference\n- Knows *when to act* and *when to ask*\n- Gets smarter about your specific business the longer you work together\n\nYou bring an AI host (Claude Desktop, Cursor, Claude Code, Codex, Hermes, OpenClaw — anything that speaks MCP). Tenpo brings the synapses. **Your AI does the thinking, Tenpo provides the truth.**\n\n---\n\n## How Tenpo thinks\n\nThe thing that makes Tenpo different isn't a feature. It's how it reasons.\n\nMost tools answer the question you asked. Tenpo answers the question that **matters** — which is usually a different one.\n\nYou ask: *\"Why is revenue down this week?\"*\n\nA normal tool says \"revenue dropped 31% vs last week.\" Accurate but useless.\n\nTenpo runs this instead:\n\n```\n\"Revenue is down 31% this week\"\n │\n ┌─────────┴──────────┐\n ▼ ▼\nWhen did it drop? What drove last\n → Tuesday week's revenue?\n │ │\n ▼ ▼\nWhat happened Are those products\non Tuesday? still in stock?\n │ │\n ▼ ▼\n3 top SKUs went NO — all 3 went OOS\nout of stock on Tuesday\n │ │\n └─────────┬──────────┘\n ▼\n Are ads still running on those OOS products?\n │\n ▼\n YES — $840/week wasted\n │\n ┌─────────┴──────────┐\n ▼ ▼\nWhen's the next Are customers\nPO arriving? churning because of this?\n │ │\n ▼ ▼\n14 days away Repeat purchase rate\n$22K/day at risk dropped 68% → 51%\n= $3.1K total risk = frustrated buyers\n going to competitors\n```\n\nOne question. Seven angles investigated. A full causal chain — from symptom to root, with dollars attached at every step.\n\nThis is **multi-directional thinking**. Tenpo keeps pulling threads until it finds the *full* answer, not just *an* answer. Every response follows the same four-part shape:\n\n> **What I'm seeing** → **Why this is happening** → **What this means** → **What I'd do about it**\n\n---\n\n## The cascade effect\n\nIn real businesses, nothing happens in isolation. Tenpo knows this.\n\nYou say four words: *\"I received PO #42.\"*\n\nHere's what happens automatically:\n\n| Step | Action |\n|---|---|\n| 1 | Marks PO #42 received, updates stock levels |\n| 2 | Finds 3 waiting orders for those SKUs — fulfils them |\n| 3 | Notices Meta + Google ads were paused on those SKUs (because they were OOS) — resumes them |\n| 4 | Records the $48,000 expense in Xero |\n| 5 | Updates the supplier's reliability score for next time |\n| 6 | Notes: \"Klaviyo not connected — back-in-stock email would have triggered for 47 customers\" |\n\nNine things across five platforms. **Every action triggers a chain reaction.** You did nothing but say four words.\n\n---\n\n## What Tenpo covers\n\nEight sectors. One operator. **You don't need to know which tool to call — just describe the outcome you want.**\n\n\n\n| Sector | \nWhat you can ask | \n
\n\n| Sales & Revenue | \n\nHow is my store doing this week · what's driving / killing revenue · best and worst products by margin · daily business overview · forecast next month's revenue · why did Tuesday spike\n\n |
\n\n| Inventory & Suppliers | \n\nWhat's about to run out · what to reorder (and how much) · which products are dead stock tying up cash · supplier reliability scorecards (A/B/C/D/F) · generate a PO and email it to my supplier · read incoming supplier emails and extract quotes · compare quotes from 3 suppliers · mark PO #42 received → cascade everything\n\n |
\n\n| Marketing & Email | \n\nDraft a winback campaign for lapsed champions · send a Klaviyo campaign · design a 30-day content calendar · A/B test subject lines · build a flash-sale flow · find cross-sell opportunities · which customers haven't bought in 60 days\n\n |
\n\n| Paid Ads | \n\nWhat's my true ROAS after COGS + shipping + fees · which campaigns to pause right now · reallocate budget from underperformers to winners · pause ads on out-of-stock products · auto-pause if ROAS drops below 2× · generate ad copy and creative concepts · campaign performance with revenue attribution\n\n |
\n\n| Customers | \n\nWho's about to churn · predicted next order date per customer · top 1% / 10% / 25% concentration risk · cross-sell next-best-product · win-back the right customers at the right time · respond to support tickets in Gorgias / Zendesk · reply to reviews on Trustpilot / Okendo / Judge.me\n\n |
\n\n| Finance & Operations | \n\nP&L waterfall (gross → COGS → fees → ad spend → operating profit) · what's leaking at each step · process Stripe refunds · push invoices to Xero / QuickBooks · create shipping labels · track shipments · sales-tax nexus monitoring · payout holds and disputes\n\n |
\n\n| Competitors | \n\nWhat's [competitor] priced at right now · who dropped prices this week · what emails are top brands sending this month · new SKUs they launched · their promo cadence · benchmark my AOV / LTV / repurchase rate against peers in my category (anonymous, k≥3 merchants)\n\n |
\n\n| Automation | \n\nEvery Monday morning, send me a store overview · when revenue drops 30%, ping me on WhatsApp · auto-pause ads on OOS products · trigger the win-back flow when a customer hits 60 days quiet · let me approve once and never ask again for the same pattern\n\n |
\n\n
\n\nEight headline sectors. Behind them: **47 platform integrations, 229 tools your AI can call, and 100+ specialist skills loaded automatically based on what you ask.**\n\n---\n\n## Beyond data — built-in expertise\n\nTenpo isn't just retrieving data. It applies deep, structured expertise to interpret it.\n\nWhen you ask Tenpo to write a campaign, it doesn't just write copy — it picks the right **psychological framework** for the moment:\n\n| You're trying to… | Tenpo reaches for… |\n|---|---|\n| Convert hesitant first-time visitors | Loss Aversion + Social Proof |\n| Move slow-selling inventory | Decoy Effect + Scarcity |\n| Bring back lapsed customers | Zeigarnik Effect + Reciprocity |\n| Increase average order value | Anchoring + Bundling Psychology |\n| Reduce cart abandonment | Endowment Effect + Commitment Consistency |\n| Launch a new product | Authority Bias + Social Proof |\n| Run a flash sale | Scarcity + Urgency + Peak-End Rule |\n| Re-engage a cold email list | Curiosity Gap + Reciprocity |\n\nWhen you ask about pricing, it thinks in a **Velocity × Margin matrix**. When you ask about churn, it knows the recovery probability decays from 25% at 30 days to <1% at 180+ days, and routes each customer to the right message at the right time. When you ask about conversion, it audits the full funnel — traffic quality → landing experience → product page → checkout → post-purchase → retention — not just the headline number.\n\n**No human campaign manager coordinates all of this in a single pass. Tenpo does it every time, in seconds.**\n\n---\n\n## Background watchers — for connected stores\n\nOnce you've connected at least one integration, Tenpo runs background checks on your data automatically — no tier upgrade required, no manual setup:\n\n| Watcher | What it catches |\n|---|---|\n| **Stock risk** | Products getting dangerously close to selling out before the next supplier delivery |\n| **Revenue cliff** | Unexplained week-over-week revenue drops |\n| **Refund spike** | Today's refund count exceeding 3× the recent baseline |\n| **ROAS death** | Ad campaigns running below breakeven |\n| **Dead stock with active ads** | Ad spend on SKUs that haven't sold in 14+ days while inventory sits |\n| **Payment failure spike** | Stripe / processor anomalies signalling card-data drift or outages |\n| **Inventory desync** | DB stock says \"available\", Shopify says \"out\" — pipeline drift |\n\nWhen a watcher fires, you get a notification on the channel you set up — Telegram, WhatsApp, Slack, or email. When the situation resolves itself, the alert closes automatically.\n\n> **What this needs:** at least one connected store + a notification channel set up. Watchers don't run for accounts that registered but never connected anything (we don't burn cycles on empty data).\n\n---\n\n## Install in 2 lines\n\n```bash\nnpx -y @tenpo/mcp\n```\n\nThat's the first line. **First run auto-issues a free API key** (500 calls/month, no expiry, no card, no signup form). The key prints once in the host's stderr — copy it into your config so it's reused next time.\n\nThe second line goes into your AI host's config:\n\n> ⚠️ **After editing the config, fully restart your AI host.**\n> MCP servers are loaded at host startup — `claude mcp add`, saving Claude Desktop's config, or editing Cursor's MCP settings will register Tenpo, but the new tools won't appear in your running session until you **quit and relaunch the app** (Cmd+Q on Mac, fully close on Windows). This is a host-side limitation, not a Tenpo one.\n\n