@agifyai/leadify-mcp 3.6.1 → 3.6.3

package/dist/server.js

@@ -16,7 +16,7 @@ import { registerPipelineTools } from "./tools/pipeline.js";
 export function createServer() {
     const server = new McpServer({
         name: "leadify",
-        version: "3.6.1",
+        version: "3.6.2",
     });
     registerAuthTools(server);
     registerOrganizationTools(server);

package/dist/tools/dataroom.js

@@ -242,6 +242,11 @@ async function mergeAndPut(organizationId, dry_run, patcher, validationHint) {
     return toolResult(data);
 }
 // ─── Tool registrations ────────────────────────────────────────────────────
+// ── get_outreach_context ─────────────────────────────────────────────────
+// Dedicated tool for the outreach pipeline Phase 0. Single call replaces the
+// old multi-step dance (get_data_room + org resolution + get_lead_group_persona)
+// and eliminates the cross-org footgun by accepting lead_group_id instead of
+// organization_id. The backend resolves the org server-side.
 export function registerDataRoomTools(server) {
     // ── get_data_room ──────────────────────────────────────────────────────
     server.tool("get_data_room", "Retrieve the organization's data room: company info (v2 schema) and all documents. " +
@@ -270,6 +275,27 @@ export function registerDataRoomTools(server) {
             return handleToolError(error);
         }
     });
+    // ── get_outreach_context ──────────────────────────────────────────────
+    server.tool("get_outreach_context", "Get a curated outreach context for a lead group: the outreach-relevant slice " +
+        "of companyInfo (identity, pitch, constraints, curated products, economics " +
+        "triggers/baseline, product ICP roles, proof wording) PLUS the full persona. " +
+        "Takes a lead_group_id (NOT organization_id) — the org is resolved server-side, " +
+        "eliminating the cross-org footgun of get_data_room. " +
+        "Returns a HARD error if no persona is linked to the group. " +
+        "Use this instead of get_data_room + get_lead_group_persona in the outreach " +
+        "pipeline Phase 0.", {
+        lead_group_id: z.string().describe("ID of the lead group to resolve context for."),
+    }, async ({ lead_group_id }) => {
+        try {
+            const params = new URLSearchParams();
+            params.set("lead_group_id", lead_group_id);
+            const data = await getClient().get("/api/outreach-context", params);
+            return toolResult(data);
+        }
+        catch (error) {
+            return handleToolError(error);
+        }
+    });
     // ── describe_company_info_schema ───────────────────────────────────────
     server.tool("describe_company_info_schema", "Return the companyInfo v2 schema mirrored at the MCP layer: all sections, enums, " +
         "max-length caps, required fields, and which patch tool owns each section. Call this " +

package/dist/tools/pipeline.js

@@ -21,7 +21,7 @@ export function registerPipelineTools(server) {
         "`get_lead` call); the caller only needs `lead_id`. " +
         "The response is decorated with a Trigger.dev `traceUrl` deep-link when missing " +
         "(https://cloud.trigger.dev/runs/{runId}), so you can always jump to the trace. " +
-        "Waits up to 120s for the remote agent to complete.", {
+        "Waits up to 300s for the remote agent to complete.", {
         lead_id: z.string().describe("ID of the lead to generate a message for."),
         dryrun: z
             .boolean()

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agifyai/leadify-mcp",
-  "version": "3.6.1",
+  "version": "3.6.3",
   "description": "MCP server for Leadify lead management API",
   "type": "module",
   "main": "dist/index.js",