@agifyai/leadify-mcp 1.5.1 → 1.5.2

package/README.md

@@ -223,3 +223,6 @@ Conséquences pratiques :
 | `update_outreach_case_study` | Ajouter / remplacer / supprimer un case study par index, sans re-envoyer la liste. |
 | `update_outreach_urls` | Patch booking_url et/ou website_url uniquement. |
 | `set_outreach_connection_request` | Toggle du flag connectionRequestEnabled (LinkedIn invite vs cold DM). |
+| `trigger_outreach` | Générer un message d'outreach via l'agent Trigger.dev (dry-run par défaut). `force=true` pour re-générer sur un lead déjà traité. |
+| `append_fine_tuning` | Appendre du contenu à une section du Fine Tuning (nonNegotiableRules, pitfalls, structure, examples). Toujours en mode append — garantie contractuelle. |
+| `pipeline_next_lead` | Sélectionner le prochain lead à traiter (score descendant, sans message). Exclusion des IDs déjà vus, limit 1-5. |

package/dist/server.js

@@ -12,6 +12,7 @@ import { registerPersonaTools } from "./tools/personas.js";
 import { registerLeadGroupTools } from "./tools/lead_groups.js";
 import { registerOrganizationTools } from "./tools/organizations.js";
 import { registerOutreachSettingsTools } from "./tools/outreach_settings.js";
+import { registerPipelineTools } from "./tools/pipeline.js";
 export function createServer() {
     const server = new McpServer({
         name: "leadify",
@@ -30,5 +31,6 @@ export function createServer() {
     registerDataSourceTools(server);
     registerPersonaTools(server);
     registerOutreachSettingsTools(server);
+    registerPipelineTools(server);
     return server;
 }

package/dist/tools/pipeline.d.ts

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

package/dist/tools/pipeline.js

@@ -0,0 +1,104 @@
+import { z } from "zod";
+import { getClient } from "../client.js";
+import { toolResult, handleToolError } from "../types.js";
+export function registerPipelineTools(server) {
+    // ── trigger_outreach ─────────────────────────────────────────────────────
+    server.tool("trigger_outreach", "Generate an outreach message for a lead via the Trigger.dev agent. " +
+        "DRY-RUN BY DEFAULT (dryrun=true) — the agent runs all logic (analysis, messaging, research) " +
+        "but NEVER persists anything to the database. Essential for iterating on messages via the " +
+        "MCP pipeline without polluting the DB. Use dryrun=false for production writes. " +
+        "The 'force' flag (default false) bypasses the 'already has a message?' guard — " +
+        "useful for re-generating on an already-processed lead. " +
+        "Waits up to 120s for the remote agent to complete.", {
+        lead_id: z.string().describe("ID of the lead to generate a message for."),
+        dryrun: z
+            .boolean()
+            .optional()
+            .default(true)
+            .describe("true (default) = dry-run mode: agent runs but writes nothing to DB. " +
+            "false = production mode: agent writes card_message, card_analysis, etc. to lead.data."),
+        force: z
+            .boolean()
+            .optional()
+            .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."),
+    }, async ({ lead_id, dryrun, force }) => {
+        try {
+            const data = await getClient().post("/api/trigger-outreach", {
+                leadId: lead_id,
+                dryrun,
+                force,
+            });
+            return toolResult(data);
+        }
+        catch (error) {
+            return handleToolError(error);
+        }
+    });
+    // ── append_fine_tuning ───────────────────────────────────────────────────
+    server.tool("append_fine_tuning", "Append content to a Fine Tuning section for a lead group. " +
+        "ALWAYS in append mode — NEVER replaces existing content (contractual guarantee). " +
+        "Use this to incrementally build up rules and examples as you iterate with the user. " +
+        "Sections: nonNegotiableRules (imperative rules), pitfalls (traps to avoid), " +
+        "structure (imposed message structure), examples (validated message samples). " +
+        "For full rewrites, use the Leadify UI or the classic update endpoint.", {
+        lead_group_id: z.string().describe("ID of the lead group."),
+        section: z
+            .enum(["nonNegotiableRules", "pitfalls", "structure", "examples"])
+            .describe("Fine Tuning section to enrich."),
+        content: z
+            .string()
+            .describe("Content to APPEND (not replace). Concatenated after existing content."),
+        separator: z
+            .string()
+            .optional()
+            .default("\n\n---\n\n")
+            .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", {
+                leadGroupId: lead_group_id,
+                section,
+                content,
+                separator,
+            });
+            return toolResult(data);
+        }
+        catch (error) {
+            return handleToolError(error);
+        }
+    });
+    // ── pipeline_next_lead ───────────────────────────────────────────────────
+    server.tool("pipeline_next_lead", "Select the next lead to process in the campaign pipeline. " +
+        "Returns the hottest leads (highest score) that don't yet have a message " +
+        "(card_message empty or missing). Exclude already-processed leads via exclude_lead_ids. " +
+        "Call this at the start of each pipeline iteration to get a fresh lead.", {
+        lead_group_id: z.string().describe("ID of the lead group to query."),
+        exclude_lead_ids: z
+            .array(z.string())
+            .optional()
+            .default([])
+            .describe("IDs of leads already processed in this session (to avoid duplicates)."),
+        limit: z
+            .number()
+            .int()
+            .min(1)
+            .max(5)
+            .optional()
+            .default(1)
+            .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", {
+                leadGroupId: lead_group_id,
+                excludeLeadIds: exclude_lead_ids,
+                limit,
+            });
+            return toolResult(data);
+        }
+        catch (error) {
+            return handleToolError(error);
+        }
+    });
+}

package/package.json

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