@agifyai/leadify-mcp 8.6.4 → 8.6.6

package/README.md

@@ -291,11 +291,10 @@ Leadify et ne doit jamais être envoyée par un agent MCP.
 | `rollback_canonical_relationship_migration` | Tombstoner les liens créés par un plan de migration précis. |
 | `update_company_brain_sections` | Modifier uniquement les sections globales encore actives (`identity`, `positioning`, `allowedVocabulary`, `prohibitedVocabulary`, `legalConstraints`). Les anciennes sections Offre/Verticale sont filtrées et refusées. |
 | `publish_context_workspace` | Publier une révision prête du Company Brain après confirmation explicite (`confirm_publish: true`). Admin de l'organisation requis ; les raisons de non-readiness sont renvoyées par le serveur. |
-| `upsert_persona` | Créer ou mettre à jour un Persona strictement lié à une organisation et à une Verticale ; `schema_packs` est obligatoire à la création et `expected_updated_at` à chaque mise à jour. Les Personas globales ou orphelines ne sont jamais créées. |
+| `list_persona_contracts` / `get_persona_contract` | Lister ou lire les contrats Persona canoniques d’une organisation explicitement sélectionnée. |
+| `create_persona_contract` | Créer un Persona tenant-scoped et lié à une Verticale depuis un contrat canonique complet. |
+| `replace_persona_contract` / `patch_persona_contract` | Remplacer ou modifier un contrat canonique avec verrou optimiste ; aucune colonne Persona historique n’est exposée. |
 | `change_persona_status` | Passer un Persona entre `DRAFT`, `ACTIVE` et `ARCHIVED` avec le même verrou `updated_at`, readiness et protection des références. |
-| `update_persona_schema_packs` | Remplacer uniquement les CRM Schema Packs d’un Persona tenant-scoped avec `expected_updated_at`, puis relire la readiness des groupes liés. |
-| `get_persona` | Récupérer un Persona par son ID et son organisation explicite. Les anciennes Personas globales/orphelines sont exclues. |
-| `get_lead_group_persona` | Récupérer le persona assigné à un groupe de leads. |
 | `list_data_sources` | Lister toutes les sources de données configurées (par pays puis nom). |
 | `create_data_source` | Créer une nouvelle source de données (admin uniquement). |
 | `update_data_source` | Modifier une source de données existante (admin uniquement). |

package/dist/client.d.ts

@@ -8,5 +8,11 @@ export declare class LeadifyClient {
     put(path: string, body: unknown): Promise<unknown>;
     patch(path: string, body: unknown): Promise<unknown>;
     delete(path: string, body?: unknown): Promise<unknown>;
+    /**
+     * Invoke an authenticated oRPC procedure. The API-key facade exposes most
+     * everyday operations as REST, while hash-pinned schema migrations remain
+     * intentionally available only through the admin oRPC boundary.
+     */
+    rpc(path: string, input: unknown): Promise<unknown>;
 }
 export declare function getClient(): LeadifyClient;

package/dist/client.js

@@ -57,6 +57,19 @@ export class LeadifyClient {
         const url = new URL(path, this.baseUrl);
         return this.request("DELETE", url, body);
     }
+    /**
+     * Invoke an authenticated oRPC procedure. The API-key facade exposes most
+     * everyday operations as REST, while hash-pinned schema migrations remain
+     * intentionally available only through the admin oRPC boundary.
+     */
+    async rpc(path, input) {
+        const url = new URL(`/rpc/${path.replace(/^\/+/, "")}`, this.baseUrl);
+        const data = await this.request("POST", url, { json: input });
+        if (data && typeof data === "object" && "json" in data) {
+            return data.json;
+        }
+        return data;
+    }
 }
 let _client = null;
 export function getClient() {

package/dist/tools/lead_groups.js

@@ -170,46 +170,4 @@ export function registerLeadGroupTools(server, writeClient) {
             return handleToolError(error);
         }
     });
-    // ── get_lead_group_persona ─────────────────────────────────────────────
-    server.tool("get_lead_group_persona", "Retrieve the persona assigned to a specific lead group, with group context. " +
-        "Returns null persona if none is assigned. Use this to check what targeting " +
-        "rules apply to a group before generating messages. " +
-        "By default, `persona` uses the OUTREACH projection (messaging + targeting), " +
-        "the lean supported view. Pass `view=full` only when you need the complete " +
-        "persona payload — prefer the dedicated get_outreach_templates tool for the outreach trio. " +
-        "SILO: outreach data is its own concern. It does not leak into the default persona payload.", {
-        lead_group_id: z.string().describe("Lead group ID."),
-        view: z
-            .enum(["full", "outreach"])
-            .optional()
-            .default("outreach")
-            .describe("Persona projection. " +
-            "'outreach' (default) = projection used by the outreach agent (messaging + targeting). " +
-            "'full' = the complete persona payload. " +
-            "Prefer get_persona + get_outreach_templates for a complete picture, scoped per concern."),
-    }, async ({ lead_group_id, view }) => {
-        try {
-            const params = new URLSearchParams();
-            if (view)
-                params.set("view", view);
-            const data = await getClient().get(`/api/lead-group/${encodeURIComponent(lead_group_id)}/persona`, params);
-            // SILO defense in depth: even if the API returns the full payload for
-            // `view=slim` (the view param is best-effort on the backend), strip the
-            // outreach trio locally so it can never leak through this tool.
-            // Outreach data belongs to the dedicated outreach tools.
-            if (view !== "outreach" && data && typeof data === "object") {
-                const wrapper = data;
-                const persona = wrapper.persona ?? null;
-                if (persona && typeof persona === "object") {
-                    delete persona.outreachTemplates;
-                    delete persona.outreachSignalRouting;
-                    delete persona.outreachFields;
-                }
-            }
-            return toolResult(data);
-        }
-        catch (error) {
-            return handleToolError(error);
-        }
-    });
 }

package/dist/tools/organizations.js

@@ -48,7 +48,7 @@ export function registerOrganizationTools(server) {
     // ── list_organizations ─────────────────────────────────────────────────
     server.tool("list_organizations", "List every organization accessible to the caller, returning each with id, name, and " +
         "optional slug. Use this as the starting point when you need an organization_id — " +
-        "e.g. before create_lead_group, clone_lead_group, upsert_persona (org-scoped), " +
+        "e.g. before create_lead_group, clone_lead_group, create_persona_contract (org-scoped), " +
         "or move_persona.", {}, async () => {
         try {
             const data = await getClient().get("/api/organizations");
@@ -129,7 +129,7 @@ export function registerOrganizationTools(server) {
                 leadGroups: groups.slice(0, limit).map((group) => ({ id: group.id, name: group.name, organizationId: group.organizationId, leadCount: group._count?.leads ?? 0, published: group.published ?? false })),
                 total: groups.length,
                 truncated: groups.length > limit,
-                next: "Choose a lead_group_id, then use get_leads, get_context_workspace, or get_lead_group_persona.",
+                next: "Choose a lead_group_id, then use get_leads, get_context_workspace, or list_persona_contracts.",
             });
         }
         catch (error) {

package/dist/tools/schema.d.ts

@@ -1,5 +1,5 @@
 import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { type LeadifyClient } from "../client.js";
-type SchemaClient = Pick<LeadifyClient, "get" | "post">;
+type SchemaClient = Pick<LeadifyClient, "get" | "post" | "rpc">;
 export declare function registerSchemaTools(server: McpServer, client?: SchemaClient): void;
 export {};

package/dist/tools/schema.js

@@ -78,6 +78,42 @@ export function registerSchemaTools(server, client) {
             return handleToolError(error);
         }
     });
+    // ── schema_migration_preview / apply_schema_migration ─────────────────
+    server.tool("schema_migration_preview", "Preview the exact hash-pinned schema migration required to make a lead group READY. " +
+        "This is read-only. Review the returned expectedSchemaHash, planHash, impacted leads and " +
+        "conversion actions before calling apply_schema_migration.", {
+        lead_group_id: z.string().describe("ID of the lead group to inspect."),
+    }, async ({ lead_group_id }) => {
+        try {
+            const data = await (client ?? getClient()).rpc("leadGroups/schemaMigrationPreview", { leadGroupId: lead_group_id });
+            return toolResult(data);
+        }
+        catch (error) {
+            return handleToolError(error);
+        }
+    });
+    server.tool("apply_schema_migration", "Apply a destructive schema migration only after schema_migration_preview has been read and " +
+        "the exact expected_schema_hash and expected_plan_hash have been supplied. This API performs " +
+        "its own optimistic hash checks. Use only for the reviewed lead group; reread its leads and " +
+        "schema readiness afterwards.", {
+        lead_group_id: z.string().describe("ID of the reviewed lead group."),
+        expected_schema_hash: z.string().regex(/^[a-f0-9]{64}$/).describe("expectedSchemaHash from the fresh preview."),
+        expected_plan_hash: z.string().regex(/^[a-f0-9]{64}$/).describe("planHash from the same fresh preview."),
+        confirmation: z.literal("apply_destructive_schema_migration").describe("Exact acknowledgement required by the server."),
+    }, async ({ lead_group_id, expected_schema_hash, expected_plan_hash, confirmation }) => {
+        try {
+            const data = await (client ?? getClient()).rpc("leadGroups/applySchemaMigration", {
+                leadGroupId: lead_group_id,
+                expectedSchemaHash: expected_schema_hash,
+                expectedPlanHash: expected_plan_hash,
+                confirmation,
+            });
+            return toolResult(data);
+        }
+        catch (error) {
+            return handleToolError(error);
+        }
+    });
     // ── delete_columns ─────────────────────────────────────────────────────
     server.tool("delete_columns", "Remove one or more columns (fields) from a lead group's schema and all lead data " +
         "stored in those fields. This action is irreversible — field definitions and values " +

package/package.json

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