@loopops/mcp-server 3.22.0 → 3.23.0

package/dist/tools/crm.js

@@ -1,7 +1,7 @@
 import { z } from "zod";
 import { trpcMutation } from "../api-client.js";
 import { safeTool } from "./_helpers.js";
-import { leadStatusSchema, salesforceLeadIdSchema, salesforceOpportunityIdSchema, targetAccountTierSchema, } from "./_schemas.js";
+import { targetAccountTierSchema } from "./_schemas.js";
 export function registerCrmTools(server, allowed) {
     // my_pipeline retired 2026-05-06 — replaced by ClickHouse parameterized
     // view analytics.my_pipeline. Row policies on salesforce.opportunity
@@ -12,58 +12,17 @@ export function registerCrmTools(server, allowed) {
     // analytics.my_leads. Row policies on salesforce.lead enforce per-user
     // scoping. Filter by created_date in the caller. See docs/CH-ANALYTICS-VIEWS.md.
     // pipeline_health retired 2026-05-06 — replaced by ClickHouse views
-    // analytics.pipeline_by_stage + analytics.win_rate(range_days). Query via
-    // the Cloud Remote MCP server (mcp.clickhouse.cloud/mcp). Row policies on
-    // salesforce.opportunity enforce per-user scoping. See docs/CH-ANALYTICS-VIEWS.md.
+    // analytics.pipeline_by_stage + analytics.win_rate(range_days).
+    // See docs/CH-ANALYTICS-VIEWS.md.
     // rep_performance retired 2026-05-06 — replaced by ClickHouse view
     // analytics.rep_performance(range_days). See docs/CH-ANALYTICS-VIEWS.md.
     // forecast retired 2026-05-06 — replaced by ClickHouse view
-    // analytics.forecast(quarter_start, quarter_end). Caller computes the
-    // quarter window. See docs/CH-ANALYTICS-VIEWS.md.
-    if (allowed.has("update_opportunity")) {
-        server.tool("update_opportunity", "Update an opportunity's close date, next step, or description. You can identify the deal by Salesforce Opportunity ID or exact opportunity name. Reps can only update their own deals. Requires a reason for the change.", {
-            opportunityId: salesforceOpportunityIdSchema
-                .optional()
-                .describe("Salesforce Opportunity ID (006…). Preferred if known."),
-            opportunityName: z
-                .string()
-                .optional()
-                .describe("Exact opportunity name, used when you don't have the Salesforce ID."),
-            close_date: z
-                .string()
-                .regex(/^\d{4}-\d{2}-\d{2}$/, { message: "Use YYYY-MM-DD." })
-                .optional()
-                .describe("New close date in YYYY-MM-DD format."),
-            next_step: z.string().optional().describe("Next step text."),
-            description: z.string().optional().describe("Opportunity description."),
-            reason: z
-                .string()
-                .min(1)
-                .describe("Why this change is being made (required, logged)."),
-        }, safeTool(async ({ opportunityId, opportunityName, close_date, next_step, description, reason }) => trpcMutation("mcp.updateOpportunity", {
-            opportunityId,
-            opportunityName,
-            fields: { close_date, next_step, description },
-            reason,
-        })));
-    }
-    if (allowed.has("update_lead")) {
-        server.tool("update_lead", "Update a lead's status or description. Reps can only update their own leads. Requires a reason for the change.", {
-            leadId: salesforceLeadIdSchema.describe("Salesforce Lead ID (00Q…)."),
-            status: leadStatusSchema
-                .optional()
-                .describe("New Salesforce Lead status."),
-            description: z.string().optional().describe("Lead description."),
-            reason: z
-                .string()
-                .min(1)
-                .describe("Why this change is being made (required, logged)."),
-        }, safeTool(async ({ leadId, status, description, reason }) => trpcMutation("mcp.updateLead", {
-            leadId,
-            fields: { status, description },
-            reason,
-        })));
-    }
+    // analytics.forecast(quarter_start, quarter_end). See docs/CH-ANALYTICS-VIEWS.md.
+    // update_opportunity / update_lead removed 2026-05-09 (Phase 2 of
+    // docs/SALESFORCE-MCP-PLAN.md). Opportunity + Lead writes go through
+    // the `salesforce-hosted` MCP for every Loop role: per-user OAuth+PKCE
+    // preserves LastModifiedById; sharing rules + FLS + validation rules
+    // enforce server-side. Use mcp__salesforce-hosted__updateSobjectRecord.
     if (allowed.has("push_target_account_to_sf")) {
         server.tool("push_target_account_to_sf", "Create Salesforce Account records from the target account list. Pushes accounts that don't yet have an SF Account ID. Ops+ only.", {
             domain: z

package/package.json

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