@agifyai/leadify-mcp 8.5.4 → 8.6.1

package/dist/tools/pipeline.js

@@ -1,7 +1,7 @@
 import { z } from "zod";
 import { getClient } from "../client.js";
 import { toolResult, toolError, handleToolError } from "../types.js";
-export function registerPipelineTools(server) {
+export function registerPipelineTools(server, client = getClient()) {
     // ── trigger_outreach ─────────────────────────────────────────────────────
     server.tool("trigger_outreach", "Generate the outreach message SEQUENCE for a lead via the Trigger.dev agent " +
         "(Leadify v3 writer). The agent is a PURE MESSAGE WRITER: it produces a multi-touch " +
@@ -28,13 +28,11 @@ export function registerPipelineTools(server) {
         "traceUrl. In dry-run (dryrun=true) the call is safe to retry, since nothing is " +
         "persisted; for production writes (dryrun=false) prefer following the trace over " +
         "blindly retrying to avoid duplicate generation. " +
-        "CARDS SUBSET (cards_to_generate): pass an explicit list of card names to restrict " +
-        "the generation to a specific subset. Use this for single-touch campaigns or " +
-        "when the full 10-card cycle is not needed. Omit to generate the full sequence " +
-        "(default). Subject fields (card_email_one_subject, etc.) should always accompany " +
-        "their body card. Valid card names: card_connexion, card_linkedin_one, " +
-        "card_linkedin_two, card_linkedin_three, card_email_one, card_email_one_subject, " +
-        "card_email_two, card_email_two_subject, card_email_three, card_email_three_subject.", {
+        "FREE WRITER: context_selection extends this same runtime with one explicit " +
+        "Vertical, Offer and Persona triplet. The backend requires all three objects to be " +
+        "ACTIVE, tenant-scoped and linked; no default is inferred. Omit context_selection " +
+        "to use the Lead Group-owned selection. The exact message-card set always comes " +
+        "from Fine Tuning and cannot be selected through technical card names.", {
         lead_id: z.string().describe("ID of the lead to generate a message for."),
         dryrun: z
             .boolean()
@@ -49,28 +47,17 @@ export function registerPipelineTools(server) {
             .default(false)
             .describe("true = bypass the 'already has a message?' check so you can re-generate. " +
             "false (default) = normal behaviour: skip leads that already have card_message."),
-        cards_to_generate: z
-            .array(z.enum([
-            "card_connexion",
-            "card_linkedin_one",
-            "card_linkedin_two",
-            "card_linkedin_three",
-            "card_email_one",
-            "card_email_one_subject",
-            "card_email_two",
-            "card_email_two_subject",
-            "card_email_three",
-            "card_email_three_subject",
-        ]))
-            .min(1)
+        context_selection: z
+            .object({
+            vertical_id: z.string().trim().min(1),
+            offer_id: z.string().trim().min(1),
+            persona_id: z.string().trim().min(1),
+        })
+            .strict()
             .optional()
-            .describe("Optional subset of outreach cards to generate. When omitted, all cards are " +
-            "generated (default behaviour — full 10-card sequence). When provided, ONLY " +
-            "these cards are generated. Example for single-touch: " +
-            "['card_connexion', 'card_linkedin_one', 'card_email_one', 'card_email_one_subject']. " +
-            "Subject fields must always accompany their body card. Cards for channels the " +
-            "lead doesn't have (e.g. email when no email address) are silently dropped."),
-    }, async ({ lead_id, dryrun, force, cards_to_generate }) => {
+            .describe("Optional explicit free-writer context. Supply vertical_id, offer_id and " +
+            "persona_id together. Omit to inherit the Lead Group context."),
+    }, async ({ lead_id, dryrun, force, context_selection }) => {
         try {
             // Resolve leadGroupId server-side. The Trigger.dev task payload requires
             // `leadGroupId`, but the lead_id alone is enough on the MCP side — we
@@ -79,7 +66,7 @@ export function registerPipelineTools(server) {
             // 10–60s Trigger.dev wait that follows.
             const leadParams = new URLSearchParams();
             leadParams.set("id", lead_id);
-            const leadRes = (await getClient().get("/get-lead", leadParams));
+            const leadRes = (await client.get("/get-lead", leadParams));
             const leadGroupId = leadRes?.lead?.groupId;
             if (!leadGroupId) {
                 return toolError(`Cannot resolve leadGroupId for lead "${lead_id}". ` +
@@ -96,10 +83,14 @@ export function registerPipelineTools(server) {
                 dryrun,
                 force,
             };
-            if (cards_to_generate && cards_to_generate.length > 0) {
-                body.cardsToGenerate = cards_to_generate;
+            if (context_selection) {
+                body.contextSelection = {
+                    verticalId: context_selection.vertical_id,
+                    offerId: context_selection.offer_id,
+                    personaId: context_selection.persona_id,
+                };
             }
-            const data = (await getClient().post("/api/trigger-outreach", body));
+            const data = (await client.post("/api/trigger-outreach", body));
             // Decorate the response with a Trigger.dev run deep-link when the
             // backend didn't ship one. Applies to BOTH success and failure paths
             // so the skill operator can always jump to the trace.
@@ -133,7 +124,7 @@ export function registerPipelineTools(server) {
             .describe("Separator between old and new content. Default: '\\n\\n---\\n\\n'."),
     }, async ({ lead_group_id, section, content, separator }) => {
         try {
-            const data = await getClient().post("/api/pipeline/append-fine-tuning", {
+            const data = await client.post("/api/pipeline/append-fine-tuning", {
                 leadGroupId: lead_group_id,
                 section,
                 content,
@@ -166,7 +157,7 @@ export function registerPipelineTools(server) {
             .describe("Maximum number of leads to return (1-5, default 1)."),
     }, async ({ lead_group_id, exclude_lead_ids, limit }) => {
         try {
-            const data = await getClient().post("/api/pipeline/next-lead", {
+            const data = await client.post("/api/pipeline/next-lead", {
                 leadGroupId: lead_group_id,
                 excludeLeadIds: exclude_lead_ids,
                 limit,

package/dist/version.d.ts

@@ -1,3 +1,3 @@
 export declare const MCP_PACKAGE_NAME = "@agifyai/leadify-mcp";
 export declare const MCP_SERVER_NAME = "leadify";
-export declare const MCP_VERSION = "8.5.4";
+export declare const MCP_VERSION = "8.6.1";

package/dist/version.js

@@ -1,3 +1,3 @@
 export const MCP_PACKAGE_NAME = "@agifyai/leadify-mcp";
 export const MCP_SERVER_NAME = "leadify";
-export const MCP_VERSION = "8.5.4";
+export const MCP_VERSION = "8.6.1";

package/package.json

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

package/dist/tools/dataroom.d.ts

@@ -1,2 +0,0 @@
-import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
-export declare function registerDataRoomTools(server: McpServer): void;