conduyt-mcp 4.15.0 → 4.17.0

package/README.md

@@ -2,7 +2,7 @@
 
 MCP server for [Conduyt CRM](https://conduyt.app) — expose your CRM as AI-accessible tools. Covers the core CRM surface (contacts, deals, pipelines, custom fields, automations, messaging, and more); use `conduyt_api_catalog` to discover the full set of 500+ REST endpoints.
 
-## 169 Tools
+## 173 Tools
 
 ### Discovery
 | Tool | Description |
@@ -270,6 +270,14 @@ MCP server for [Conduyt CRM](https://conduyt.app) — expose your CRM as AI-acce
 | `conduyt_update_intake_deals` | Configure automatic deal creation on live intake (webhooks, forms, bookings) |
 | `conduyt_update_master_statuses` | Set the account's custom lead lifecycle statuses |
 
+### Reply Capture (inbound email)
+| Tool | Description |
+|------|-------------|
+| `conduyt_reply_capture_get` | Current state: configured/live, capture domain + reply address, pending DNS records, provider health |
+| `conduyt_reply_capture_setup` | Create the receiving subdomain (must be a subdomain of the verified sending domain) and return its DNS records |
+| `conduyt_reply_capture_verify` | Check DNS and promote to live once the provider confirms inbound receiving |
+| `conduyt_reply_capture_remove` | Remove capture (and finish an interrupted removal) — requires `confirm='REMOVE'`; replies to already-sent email are lost |
+
 ## Setup
 
 ```bash

package/dist/index.js

@@ -37,6 +37,7 @@ import { registerWorkflowSandboxTools } from "./tools/workflow-sandbox.js";
 import { registerPrivacyTools } from "./tools/privacy.js";
 import { registerAccountExportTools } from "./tools/account-exports.js";
 import { registerLifecycleTools } from "./tools/lifecycle.js";
+import { registerReplyCaptureTools } from "./tools/reply-capture.js";
 const apiUrl = process.env.CONDUYT_API_URL;
 const apiKey = process.env.CONDUYT_API_KEY;
 if (!apiUrl || !apiKey) {
@@ -96,5 +97,6 @@ registerWorkflowSandboxTools(server, client);
 registerPrivacyTools(server, client);
 registerAccountExportTools(server, client);
 registerLifecycleTools(server, client);
+registerReplyCaptureTools(server, client);
 const transport = new StdioServerTransport();
 await server.connect(transport);

package/dist/tools/automations.js

@@ -45,6 +45,10 @@ export function registerAutomationTools(server, client) {
         schedule: z.string().optional().describe("Updated cron schedule"),
         scheduleTimezone: z.string().optional().describe("Updated timezone"),
         stopOnResponse: z.boolean().optional().describe("Stop drip if contact responds"),
+        activeRunPolicy: z
+            .enum(["keep", "restart"])
+            .optional()
+            .describe("What a NEW trigger does when the contact is already mid-sequence: 'keep' (default — skip, existing run keeps its schedule) or 'restart' (cancel the parked run and re-enroll from step 1)"),
     }, async ({ id, ...updates }) => {
         const result = await client.patch(`/api/v1/automations/${id}`, updates);
         return formatResult(result);

package/dist/tools/reply-capture.d.ts

@@ -0,0 +1,29 @@
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
+import { ConduytClient } from "../client.js";
+/**
+ * Reply capture: the dedicated receiving subdomain that lets replies to CRM
+ * emails record and thread against the contact.
+ *
+ * Lifecycle mirrors the sending domain: create -> DNS records -> verify ->
+ * live. It is a strict subdomain of the account's own VERIFIED sending
+ * domain (the API refuses anything else — that rule is the cross-tenant
+ * fence, not a formatting preference), and only ONE capture domain can be
+ * set up at a time.
+ *
+ * Outcomes that are NORMAL here, not failures to retry blindly:
+ *  - 409 "already configured" — remove the current one first.
+ *  - 409 "contact support to reconcile" — the row is in an operator-repair
+ *    state (a provider create whose response was lost, or a stored provider
+ *    id that does not resolve to this domain). Support repairs it through a
+ *    super-admin, session-only endpoint that API keys deliberately cannot
+ *    reach; do not loop on it.
+ *  - 429 — the per-account budget (setup/teardown are limited per hour,
+ *    verification per minute). DNS takes minutes to propagate; wait.
+ *  - 503 — the shared email-provider allowance is busy with customer sends.
+ *    Retry in a moment; it says nothing about the domain's health.
+ *
+ * Removal is IRREVERSIBLE for in-flight threads: replies to emails already
+ * sent go to an address that no longer routes, so they are lost. Hence the
+ * confirm gate below.
+ */
+export declare function registerReplyCaptureTools(server: McpServer, client: ConduytClient): void;

package/dist/tools/reply-capture.js

@@ -0,0 +1,63 @@
+import { z } from "zod";
+import { formatResult } from "../client.js";
+/**
+ * Reply capture: the dedicated receiving subdomain that lets replies to CRM
+ * emails record and thread against the contact.
+ *
+ * Lifecycle mirrors the sending domain: create -> DNS records -> verify ->
+ * live. It is a strict subdomain of the account's own VERIFIED sending
+ * domain (the API refuses anything else — that rule is the cross-tenant
+ * fence, not a formatting preference), and only ONE capture domain can be
+ * set up at a time.
+ *
+ * Outcomes that are NORMAL here, not failures to retry blindly:
+ *  - 409 "already configured" — remove the current one first.
+ *  - 409 "contact support to reconcile" — the row is in an operator-repair
+ *    state (a provider create whose response was lost, or a stored provider
+ *    id that does not resolve to this domain). Support repairs it through a
+ *    super-admin, session-only endpoint that API keys deliberately cannot
+ *    reach; do not loop on it.
+ *  - 429 — the per-account budget (setup/teardown are limited per hour,
+ *    verification per minute). DNS takes minutes to propagate; wait.
+ *  - 503 — the shared email-provider allowance is busy with customer sends.
+ *    Retry in a moment; it says nothing about the domain's health.
+ *
+ * Removal is IRREVERSIBLE for in-flight threads: replies to emails already
+ * sent go to an address that no longer routes, so they are lost. Hence the
+ * confirm gate below.
+ */
+export function registerReplyCaptureTools(server, client) {
+    server.tool("conduyt_reply_capture_get", "Get the account's reply-capture state: whether it is configured and live, the capture domain and reply address, DNS records for a pending setup, and provider health. health='checking' with a healthWarning means the provider is re-checking DNS — capture stays active. degraded=true means the provider can no longer receive on that domain and it must be removed and set up again. needsSupport=true means an operator must reconcile it first. cleanupPending=true means a previous removal did not finish at the provider — call conduyt_reply_capture_remove again to complete it.", {}, async () => {
+        const result = await client.get("/api/v1/email-domains/reply-capture");
+        return formatResult(result);
+    });
+    server.tool("conduyt_reply_capture_setup", "Start reply-capture setup: creates the receiving domain at the email provider and returns the DNS records to add. The domain MUST be a strict subdomain of the account's own verified sending domain (omit it to use the suggested 'reply.<sending-domain>'); anything else is refused. Requires a verified sending domain first. After adding the DNS records, call conduyt_reply_capture_verify. A 409 means capture is already configured, a setup is already in progress, or the previous one still needs operator reconciliation.", {
+        domain: z
+            .string()
+            // TRIM BEFORE the emptiness check: the API trims and treats a blank
+            // as "omitted", silently creating reply.<sending-domain>. An empty
+            // agent variable would then burn mutation quota, take the account's
+            // ONE capture slot, and block sending-domain removal. Fail here.
+            .trim()
+            .min(1, "domain must not be blank — omit it entirely to use the suggested default")
+            .optional()
+            .describe("Capture subdomain, e.g. 'reply.acme.com'. Must be a subdomain of the account's verified sending domain. Omit to use the suggested default."),
+    }, async ({ domain }) => {
+        // An absent domain is serialized away, which is exactly how the API
+        // reads "use the suggested reply.<sending-domain>".
+        const result = await client.post("/api/v1/email-domains/reply-capture", { domain });
+        return formatResult(result);
+    });
+    server.tool("conduyt_reply_capture_verify", "Check the pending reply-capture domain's DNS and promote it to live once the provider reports it verified with inbound receiving in place. Returns verified=false plus the current DNS record states while records are still propagating — that is expected, not an error; poll sparingly (DNS takes minutes, and this endpoint is budgeted per account). Promotion is what turns on inbound matching and the Reply-To on outgoing email.", {}, async () => {
+        const result = await client.post("/api/v1/email-domains/reply-capture/verify", {});
+        return formatResult(result);
+    });
+    server.tool("conduyt_reply_capture_remove", "Remove reply capture: stops using the capture Reply-To on new email, stops matching inbound replies, and deletes the receiving domain at the provider. Replies to emails ALREADY SENT will be lost — there is no undo. Also completes a previously interrupted removal (cleanupPending) without creating anything new. Requires an explicit confirm='REMOVE'. Note: while any reply-capture row exists the sending domain cannot be removed, so this is also the step that unblocks that.", {
+        confirm: z
+            .literal("REMOVE")
+            .describe("Must be exactly 'REMOVE'. Hard safety gate: replies to already-sent emails are irrecoverably lost once the capture domain is gone."),
+    }, async () => {
+        const result = await client.del("/api/v1/email-domains/reply-capture");
+        return formatResult(result);
+    });
+}

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "conduyt-mcp",
-  "version": "4.15.0",
-  "description": "MCP server for Conduyt CRM \u2014 expose CRM operations as AI-accessible tools",
+  "version": "4.17.0",
+  "description": "MCP server for Conduyt CRM — expose CRM operations as AI-accessible tools",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -57,4 +57,4 @@
     "tsx": "^4.19.0",
     "@types/node": "^22.0.0"
   }
-}
+}

package/scripts/coverage-manifest.json

@@ -203,7 +203,7 @@
     {
       "match": "/api/v1/email-domains",
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered \u2014 see the reply_capture_* tools)"
     },
     {
       "match": "/api/v1/mailbox",
@@ -501,4 +501,4 @@
       "reason": "outbound webhook subscription management (distinct from the inbound /webhooks/ receivers)"
     }
   ]
-}
+}

package/scripts/coverage-matrix.json

@@ -1,11 +1,11 @@
 {
-  "generatedAt": "2026-07-29T16:12:55.014Z",
-  "toolCount": 169,
-  "totalEndpoints": 831,
+  "generatedAt": "2026-08-06T22:46:04.536Z",
+  "toolCount": 173,
+  "totalEndpoints": 842,
   "counts": {
-    "covered": 157,
-    "excluded": 243,
-    "planned": 431,
+    "covered": 161,
+    "excluded": 248,
+    "planned": 433,
     "uncategorized": 0
   },
   "matrix": {
@@ -297,6 +297,14 @@
       "status": "excluded",
       "reason": "super-admin platform operations (Conduyt staff only)"
     },
+    "GET /api/v1/admin/reply-capture/reconcile": {
+      "status": "excluded",
+      "reason": "super-admin platform operations (Conduyt staff only)"
+    },
+    "POST /api/v1/admin/reply-capture/reconcile": {
+      "status": "excluded",
+      "reason": "super-admin platform operations (Conduyt staff only)"
+    },
     "GET /api/v1/admin/scale-readiness": {
       "status": "excluded",
       "reason": "super-admin platform operations (Conduyt staff only)"
@@ -1289,6 +1297,10 @@
       "status": "planned",
       "reason": "conversation thread surfaces"
     },
+    "POST /api/v1/conversations/:contactId/compliance": {
+      "status": "planned",
+      "reason": "conversation thread surfaces"
+    },
     "GET /api/v1/conversations/:contactId/state": {
       "status": "planned",
       "reason": "conversation thread surfaces"
@@ -1321,6 +1333,10 @@
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
     },
+    "GET /api/v1/cron/capture-rfc-ids": {
+      "status": "excluded",
+      "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
+    },
     "GET /api/v1/cron/cleanup-audit-logs": {
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
@@ -1373,6 +1389,10 @@
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
     },
+    "GET /api/v1/cron/process-consent-outbox": {
+      "status": "excluded",
+      "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
+    },
     "GET /api/v1/cron/process-data-model-jobs": {
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
@@ -1477,6 +1497,10 @@
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
     },
+    "GET /api/v1/cron/reconcile-reply-capture": {
+      "status": "excluded",
+      "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
+    },
     "GET /api/v1/cron/recurring-tasks": {
       "status": "excluded",
       "reason": "CRON_SECRET-gated infrastructure jobs; never key-callable"
@@ -2033,27 +2057,51 @@
     },
     "GET /api/v1/email-domains": {
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered — see the reply_capture_* tools)"
     },
     "POST /api/v1/email-domains": {
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered — see the reply_capture_* tools)"
     },
     "PATCH /api/v1/email-domains": {
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered — see the reply_capture_* tools)"
     },
     "DELETE /api/v1/email-domains": {
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered — see the reply_capture_* tools)"
+    },
+    "GET /api/v1/email-domains/reply-capture": {
+      "status": "covered",
+      "tools": [
+        "conduyt_reply_capture_get"
+      ]
+    },
+    "POST /api/v1/email-domains/reply-capture": {
+      "status": "covered",
+      "tools": [
+        "conduyt_reply_capture_setup"
+      ]
+    },
+    "DELETE /api/v1/email-domains/reply-capture": {
+      "status": "covered",
+      "tools": [
+        "conduyt_reply_capture_remove"
+      ]
+    },
+    "POST /api/v1/email-domains/reply-capture/verify": {
+      "status": "covered",
+      "tools": [
+        "conduyt_reply_capture_verify"
+      ]
     },
     "GET /api/v1/email-domains/status": {
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered — see the reply_capture_* tools)"
     },
     "POST /api/v1/email-domains/verify": {
       "status": "planned",
-      "reason": "sending-domain management"
+      "reason": "sending-domain management (reply-capture subpaths ARE covered — see the reply_capture_* tools)"
     },
     "POST /api/v1/email/send": {
       "status": "covered",
@@ -2455,6 +2503,10 @@
       "status": "planned",
       "reason": "message surfaces beyond send tools"
     },
+    "GET /api/v1/messages/:id/media/:mediaIndex": {
+      "status": "planned",
+      "reason": "message surfaces beyond send tools"
+    },
     "GET /api/v1/messages/sms/:id": {
       "status": "planned",
       "reason": "message surfaces beyond send tools"