@loopops/mcp-server 3.50.0 → 3.52.0

package/dist/index.js

@@ -19,6 +19,7 @@ import { registerPeopleMasterTools } from "./tools/people-master.js";
 import { registerScoringTools } from "./tools/scoring.js";
 import { registerCpqTools } from "./tools/cpq.js";
 import { registerDealPrepTools } from "./tools/deal-prep.js";
+import { registerPlanTools } from "./tools/plan.js";
 import { registerSfdcSyncTools } from "./tools/sfdc-sync.js";
 import { registerTalTools } from "./tools/tal.js";
 import { parseSkillModesResponse } from "./skills/loader.js";
@@ -73,6 +74,7 @@ registerScoringTools(server, allowedSkills);
 registerSfdcSyncTools(server, allowedSkills);
 registerCpqTools(server, allowedSkills);
 registerDealPrepTools(server, allowedSkills);
+registerPlanTools(server, allowedSkills);
 // Skills framework — fetch role-visible skills from the Loop API and
 // register each as a server-provided MCP prompt. Surfaces in the
 // client's `/` menu and bundles (system prompt + tool emphasis +

package/dist/tools/deal-prep.js

@@ -1,3 +1,4 @@
+import { z } from "zod";
 import { trpcQuery } from "../api-client.js";
 import { safeTool } from "./_helpers.js";
 /**
@@ -20,4 +21,20 @@ export function registerDealPrepTools(server, allowed) {
     if (allowed.has("deal_prep_context")) {
         server.tool("deal_prep_context", "Loads Loop's deal-prep playbook: pre-call / during / post-call workflow, MEDDPICC field map (Salesforce API names), progression rules (Not Started → Identified → Validated → Confirmed; score 0-3 per dimension), health bands, conversation patterns, and follow-up actions. Call this ONCE per deal-prep conversation before doing anything else. The deal_prep skill auto-loads this on entry.", {}, safeTool(async () => trpcQuery("mcp.dealPrepContext")));
     }
+    if (allowed.has("opportunity_meddpicc")) {
+        server.tool("opportunity_meddpicc", "Read all 8 MEDDPICC dimensions + score + band + biggest-gap callout for an Opportunity. Loop-side read via the service account — guaranteed available even when salesforce-hosted MCP is reconnecting. Use this in the pre-call phase of /deal_prep. Look up by opportunityId / opportunityName / accountName (account name resolves to the most recently modified open opp). For WRITES, use salesforce-hosted updateSobjectRecord — per-user OAuth preserves LastModifiedById.", {
+            opportunityId: z
+                .string()
+                .regex(/^006/)
+                .optional()
+                .describe("SF Opportunity Id (006...). Provide one of: opportunityId / opportunityName / accountName."),
+            opportunityName: z.string().optional(),
+            accountName: z
+                .string()
+                .min(2)
+                .max(200)
+                .optional()
+                .describe("Customer account name (substring). Resolves to most recent open opp."),
+        }, safeTool(async (args) => trpcQuery("mcp.opportunityMeddpicc", args)));
+    }
 }

package/dist/tools/plan.d.ts

@@ -0,0 +1,15 @@
+import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
+/**
+ * Planning-chain context tools — surface for the `/plan_design` and
+ * `/plan_deploy` skills.
+ *
+ * Each skill bundles ONE loop-side context tool (loads the playbook)
+ * with existing planning-chain tools (capacity_report, list_scenarios,
+ * review_user_assignments, edit_quota, etc. — declared in the
+ * skill's tools_emphasized).
+ *
+ * `/plan_design`  — ops + leadership; strategic capacity + scenario design
+ * `/plan_deploy`  — manager + leadership + ops; review + edit + approve
+ *                   placement chain proposals scoped to caller's subtree
+ */
+export declare function registerPlanTools(server: McpServer, allowed: Set<string>): void;

package/dist/tools/plan.js

@@ -0,0 +1,23 @@
+import { trpcQuery } from "../api-client.js";
+import { safeTool } from "./_helpers.js";
+/**
+ * Planning-chain context tools — surface for the `/plan_design` and
+ * `/plan_deploy` skills.
+ *
+ * Each skill bundles ONE loop-side context tool (loads the playbook)
+ * with existing planning-chain tools (capacity_report, list_scenarios,
+ * review_user_assignments, edit_quota, etc. — declared in the
+ * skill's tools_emphasized).
+ *
+ * `/plan_design`  — ops + leadership; strategic capacity + scenario design
+ * `/plan_deploy`  — manager + leadership + ops; review + edit + approve
+ *                   placement chain proposals scoped to caller's subtree
+ */
+export function registerPlanTools(server, allowed) {
+    if (allowed.has("plan_design_context")) {
+        server.tool("plan_design_context", "Loads Loop's plan-design playbook: workflow (initial_read → scenario_iteration → promote_and_open), design heuristics (capacity_vs_target, productivity_assumptions, hire_timing, segment_mix), scenario_promotion_criteria, conversation_patterns. Call ONCE per plan-design conversation before doing anything else. The /plan_design skill auto-loads this on entry.", {}, safeTool(async () => trpcQuery("mcp.planDesignContext")));
+    }
+    if (allowed.has("plan_deploy_context")) {
+        server.tool("plan_deploy_context", "Loads Loop's plan-deploy playbook: three review tracks (user_assignments, quotas, account_assignments), anomaly_checks per track (patch sizing imbalance, manager hierarchy violations, low-confidence picks, etc.), edit_reasons guidance, conversation_patterns, audit_responsibility, and handoff to the commit chain. Call ONCE per plan-deploy conversation before doing anything else. The /plan_deploy skill auto-loads this on entry.", {}, safeTool(async () => trpcQuery("mcp.planDeployContext")));
+    }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@loopops/mcp-server",
-  "version": "3.50.0",
+  "version": "3.52.0",
   "description": "Loop Operations MCP Server — AI skills for RevOps",
   "license": "UNLICENSED",
   "type": "module",