@tenpo/mcp 0.2.12 → 0.3.0

package/dist/index.js

@@ -101,6 +101,62 @@ async function ensureApiKey() {
     }
 }
 // ── MCP server ──────────────────────────────────────────────────────────────
+/**
+ * Operator brief injected into every host AI's context at MCP connection time.
+ *
+ * Per MCP spec, `serverInfo.instructions` is THE field for telling the host AI
+ * how to behave when this server is loaded. Without this, the host falls back
+ * to its generic system prompt — and Tenpo MCP responses end up generic.
+ *
+ * Distilled from `/skills/tenpo-soul/SKILL.md` (472 lines → ~1.6KB). Covers:
+ * identity, zero-fabrication, response standard, tool chaining, sparse-data
+ * fallback, playbook library, and internal-name scrubbing.
+ */
+const TENPO_OPERATOR_BRIEF = `You have Tenpo — the operator system for this merchant. 200+ tools across 8 commerce domains, 215 expert playbooks, per-merchant DuckDB with live store data, network telemetry.
+
+# How to use Tenpo
+
+For ANY non-trivial commerce question, your FIRST action is:
+
+  tenpo_think({ query: "<the user's question verbatim>" })
+
+This returns a "thinking pack" — Tenpo's full pre-LLM orchestration output, designed for YOUR model (Sonnet/Opus/GPT-4/Gemini) to consume. The pack tells you:
+
+  • Domain + mode classification (fast / deep / investigate)
+  • Pre-fetched store evidence (snapshot, integration health)
+  • Data-quality flags — catches demo stores, sync issues, no-orders-30d gaps, structural anomalies that should change your strategy entirely
+  • Top 8 scored tools (of 200+) ranked by relevance to THIS query, with "why_relevant" reasoning
+  • Top 3 expert playbooks (of 215) with content previews
+  • Abstract reasoning directives (not scripted phrasings — principles you apply)
+  • Follow-up loop hints — what to call next based on what you find
+
+The pack tells you WHAT TO THINK ABOUT. You decide WHAT TO SAY. Tenpo orchestrates; you reason.
+
+# Discipline rules (always apply)
+
+1. Zero fabrication. Every number/name/date/ID must come from a tool call THIS turn. If you didn't call a tool for it, you don't know it. Empty results = report empty. Errors = report verbatim.
+
+2. Surface data-quality flags FIRST. If the pack flags a demo store, a sync gap, or zero historic orders — that finding leads your response. Don't strategize past a structural anomaly.
+
+3. Use tools the pack scored. The scored_tools list is curated for this query — call those first. Other tools exist (200+ total) but the pack ranking reflects relevance.
+
+4. Use the playbooks. The scored_skills list comes with content previews. Pull deeper via tenpo_get_prompt(id) when you need the full playbook.
+
+5. Investigate before strategizing in "investigate" mode. Don't stop at the symptom — chain tools until you find the causal chain, then explain it.
+
+6. Writes require tenpo_approve. Never claim "Done ✅" without a tool result confirming success.
+
+7. Translate internal names. Never expose "tenpo-klaviyo skill" or "tenpo_X tool" to the merchant. Natural language only.
+
+8. Custom integrations are universal. Any service the merchant names — Loop Returns, Sentry, n8n, custom webhooks — connect via tenpo_add_custom_connector + tenpo_call_integration. Never refuse.
+
+# Format
+
+Tool responses with a _DISPLAY_RULE field carry rendering directives — follow them. Charts use tenpo_chart and return real PNG URLs (QuickChart-rendered) that work in every host. For 3+ rows of data, use markdown tables.
+
+# Identity
+
+You ARE the operator running alongside this store, not a generic assistant. Direct. Lead with the answer. Every sentence carries information.`;
 const server = new Server({
     name: "tenpo",
     version: "0.2.0",
@@ -114,6 +170,11 @@ const server = new Server({
         // Desktop / Claude Code) handle it, others return method-not-found and
         // we fall back to BM25 gracefully.
     },
+    // serverInfo.instructions: read by every MCP host at connection time and
+    // injected into the host AI's context. This is how we ship Tenpo's
+    // operator psychology to coding agents (Claude Desktop, Cursor, Claude
+    // Code, Codex, etc.) without an LLM running server-side.
+    instructions: TENPO_OPERATOR_BRIEF,
 });
 // ── Sampling capability detection ───────────────────────────────────────────
 // Some hosts (Claude Desktop, Claude Code) support sampling. Others don't yet.
@@ -164,6 +225,20 @@ async function tryClassifyIntentViaSampling(query, taxonomy) {
 }
 // ── Tools ───────────────────────────────────────────────────────────────────
 const TOOLS = [
+    {
+        name: "tenpo_think",
+        description: "GOD-MODE ENTRY POINT — Call this FIRST for ANY non-trivial commerce question. Returns a 'thinking pack' with: domain classification, pre-fetched store evidence + data-quality flags (catches dev/demo stores, sync issues, structural anomalies), top 8 scored tools (of 200+) with relevance reasoning, top 3 expert playbooks (of 215) with content previews, abstract reasoning directives, and follow-up loop hints. The pack tells you WHAT to think about — you decide WHAT TO SAY. Tenpo never runs an LLM; your host model does the reasoning with curated context. This is what makes coding agents perform at or beyond the in-app Tenpo agent.",
+        inputSchema: {
+            type: "object",
+            required: ["query"],
+            properties: {
+                query: {
+                    type: "string",
+                    description: "The merchant's question or request, verbatim",
+                },
+            },
+        },
+    },
     {
         name: "tenpo_route",
         description: "PREFLIGHT INTELLIGENCE — Returns a curated tool/skill bundle for a query. Tenpo NEVER runs an LLM; you (the host) do the synthesis with your own tokens. Returns: relevant_tools (top 5 of 175+), relevant_skills (top 3 of 199 with content), suggested_path, pre_executed_data (revenue/alerts), suggested_next_actions, soul. Call this once per user query, then tenpo_run_tool for each tool you need.",
@@ -417,6 +492,16 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
     const { name, arguments: args = {} } = request.params;
     try {
         switch (name) {
+            case "tenpo_think": {
+                const a = args;
+                if (!a.query)
+                    throw new Error("query required");
+                const result = await tenpoFetch("/api/v1/think", {
+                    method: "POST",
+                    body: { query: a.query },
+                });
+                return formatToolResult(result);
+            }
             case "tenpo_route": {
                 const result = await tenpoFetch("/api/v1/route", {
                     method: "POST",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tenpo/mcp",
-  "version": "0.2.12",
+  "version": "0.3.0",
   "description": "Tenpo — the operator that runs alongside your store. Connects to 45+ commerce platforms (Shopify, Klaviyo, Meta Ads, GA4, Stripe…) and gives any AI host (Claude Desktop, Cursor, Claude Code, ChatGPT) deterministic answers about your sales, ads, email, inventory, suppliers, customers, finance, and competitors. Free tier, no card required.",
   "license": "MIT",
   "homepage": "https://tenpo.ai",