@aioproductoscom/mcp 0.11.0 → 0.14.0

package/dist/client.js

@@ -67,6 +67,19 @@ export class PlatformClient {
     customer360(query) {
         return this.req(`/api/me/customer?q=${encodeURIComponent(query)}`);
     }
+    nps(opts) {
+        const p = new URLSearchParams();
+        if (opts.productId)
+            p.set("product_id", opts.productId);
+        if (opts.windowDays)
+            p.set("window_days", String(opts.windowDays));
+        const qs = p.toString();
+        return this.req(`/api/me/nps${qs ? `?${qs}` : ""}`);
+    }
+    nrr(windowDays) {
+        const qs = windowDays ? `?window_days=${windowDays}` : "";
+        return this.req(`/api/me/nrr${qs}`);
+    }
     funnel(opts) {
         const p = new URLSearchParams();
         if (opts.productId)

package/dist/index.js

@@ -18,7 +18,12 @@ function text(data) {
         ],
     };
 }
-const server = new McpServer({ name: "productos", version: "0.11.0" }, {
+/** A prompt result — one user-role message the host injects when the slash
+ *  command runs. Surfaces as a named slash command in the AI host. */
+function promptMsg(body) {
+    return { messages: [{ role: "user", content: { type: "text", text: body } }] };
+}
+const server = new McpServer({ name: "AIOProductOS", version: "0.14.0" }, {
     instructions: "You manage product work on ProductOS for the connected member — board, insights, features, and " +
         "analytics all hang off one spine. Call get_pm_playbook first for how to operate: ground in " +
         "get_product_brain, keep work tied to the spine (insight→feature→task→outcome), and prioritize on " +
@@ -54,6 +59,8 @@ server.tool("update_task", "Update a task's fields (status, priority, title, des
 server.tool("comment_on_task", "Add a comment to a task.", { id: z.string(), body: z.string() }, async (a) => text(await client.comment(a.id, a.body)));
 server.tool("get_product_brain", "Read a grounded, read-only snapshot of the org's product so YOU can reason about it on your own model: revenue + top paying accounts, web + product analytics, features, recent verbatim customer signals, and open work. Optional product_id; omit for the primary product. Returns the brain text plus the list of products you can ask about.", { product_id: z.string().optional() }, async (a) => text(await client.brain(a.product_id)));
 server.tool("get_customer_360", "Everything about ONE customer, resolved by id, email, domain, or company name: profile, subscription + MRR, how many users sit under the account, and their verbatim feedback. The money + people + voice join on one record — use it before answering anything about a specific account.", { query: z.string() }, async (a) => text(await client.customer360(a.query)));
+server.tool("analyze_nps", "NPS for the product — standard score AND revenue-weighted NPS (each respondent weighted by their account MRR), plus the detractor accounts ranked by what they're worth, with verbatims. The revenue weighting is the spine join no standalone survey tool can compute: it surfaces when your biggest customers are the unhappy ones even if the headline score looks fine. Optional product_id (primary by default) and window_days (default 90).", { product_id: z.string().optional(), window_days: z.number().optional() }, async (a) => text(await client.nps({ productId: a.product_id, windowDays: a.window_days })));
+server.tool("analyze_nrr", "Net Revenue Retention — NRR (revenue-weighted) next to logo retention (count-weighted), the expansion/contraction/churn split, and the accounts that lost the most MRR. The divergence is the point: \"you keep 92% of logos but 78% of revenue\" means a big account churned while the headline looks fine. NRR is the number investors ask for and no standalone analytics tool can compute — it needs revenue on the same record. Optional window_days (default 90). Returns status 'building' until enough daily MRR snapshots exist to compare.", { window_days: z.number().optional() }, async (a) => text(await client.nrr(a.window_days)));
 server.tool("capture_insight", "Write a piece of customer feedback to the spine (the agent's own hand, not just reading). It fires the same insight.created webhook a manual capture does. Tie it to the account it's about (account_id) and the feature it concerns (feature_id) when you know them; kind='opportunity' for a prioritizable ask. Defaults to the primary product.", {
     body: z.string(),
     title: z.string().optional(),
@@ -85,6 +92,30 @@ server.tool("list_channels", "List the team Comms channels you (this token's mem
 server.tool("read_channel", "Read recent messages in a Comms channel you belong to (oldest→newest), so you can catch up before replying. Pass the channel_id from list_channels.", { channel_id: z.string(), limit: z.number().optional() }, async (a) => text(await client.readChannel(a.channel_id, a.limit)));
 server.tool("post_to_channel", "Post a message into a team Comms channel you belong to. It goes out as you (this token's member) and appears live for your teammates — use it to tell the team what you did, share a link, or ask a question. Only works for channels you're a member of (see list_channels).", { channel_id: z.string(), body: z.string() }, async (a) => text(await client.postToChannel(a.channel_id, a.body)));
 server.tool("reply_in_channel", "Reply in a thread under a specific message in a Comms channel you belong to. Pass the parent message's id (from read_channel) as parent_id.", { channel_id: z.string(), parent_id: z.string(), body: z.string() }, async (a) => text(await client.replyInChannel(a.channel_id, a.parent_id, a.body)));
+// ── Routines (slash-command prompts) ────────────────────────────────────────
+// Surface in the AI host as named slash commands (e.g. Claude Code:
+// /productos:standup), so the human — or a scheduled headless run — can run a
+// product routine on demand. Each orchestrates the tools above; they stay
+// read-first and only write what the playbook sanctions.
+server.prompt("standup", "Board standup — what moved, what's blocked, what needs you today (read-only).", async () => promptMsg(`Run the product standup for the connected org. Read-only — don't change anything.\n` +
+    `1) pm_meta to resolve lists / statuses / members.\n` +
+    `2) list_tasks to read the active board.\n` +
+    `Report briefly: what's in progress, what's blocked (and why), what's gone stale with no movement, and the 1–3 ` +
+    `decisions that need a human today. Pull get_product_brain if revenue/account context sharpens the call. ` +
+    `End with the single most important thing to do next.`));
+server.prompt("triage", "Triage — turn fresh customer signal into prioritized, spine-linked work.", async () => promptMsg(`Run intake triage for the connected org. Follow get_pm_playbook.\n` +
+    `1) get_product_brain — ground in revenue, top accounts, recent verbatim signal, and open work.\n` +
+    `2) Review the board (list_tasks, pm_meta) and any fresh insights.\n` +
+    `3) Prioritize on EVIDENCE — affected accounts + MRR + reach — never an invented score.\n` +
+    `4) Make the writes you're confident in: create_task / update_task, linking insight→feature→task; ` +
+    `assign owners; place the clear ones in the current sprint. SURFACE the judgment calls for a human instead of guessing.\n` +
+    `Confirm only the writes you actually made.`));
+server.prompt("daily", "Daily PM briefing — your plate, blockers, and the one thing to do next.", async () => promptMsg(`Give the connected member their daily briefing.\n` +
+    `1) get_product_brain for context.\n` +
+    `2) list_tasks + pm_meta — what's assigned to them, what's blocked, what's overdue or stale.\n` +
+    `3) Scan the support inbox (list_conversations) and upcoming calls (list_bookings) for anything urgent.\n` +
+    `Output a tight briefing: top priorities today, blockers needing a decision, and ONE recommended next action. ` +
+    `Read-only unless they ask you to act.`));
 async function main() {
     await server.connect(new StdioServerTransport());
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aioproductoscom/mcp",
-  "version": "0.11.0",
+  "version": "0.14.0",
   "description": "ProductOS MCP — manage tickets, read your product brain + analytics, and run the support inbox from Claude Code, Cursor, Codex, and any MCP host.",
   "type": "module",
   "license": "MIT",
@@ -11,7 +11,9 @@
     "url": "git+https://github.com/businesstalksnetwork/productos.git",
     "directory": "packages/mcps/productos-pm"
   },
-  "bugs": { "url": "https://github.com/businesstalksnetwork/productos/issues" },
+  "bugs": {
+    "url": "https://github.com/businesstalksnetwork/productos/issues"
+  },
   "keywords": [
     "mcp",
     "model-context-protocol",
@@ -22,10 +24,19 @@
     "project-management",
     "product-management"
   ],
-  "bin": { "productos": "dist/index.js" },
-  "files": ["dist", "README.md"],
-  "engines": { "node": ">=18" },
-  "publishConfig": { "access": "public" },
+  "bin": {
+    "productos": "dist/index.js"
+  },
+  "files": [
+    "dist",
+    "README.md"
+  ],
+  "engines": {
+    "node": ">=18"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
   "scripts": {
     "build": "tsc",
     "prepublishOnly": "npm run build",