conduyt-mcp 4.77.0 → 4.79.0

package/README.md

@@ -55,7 +55,7 @@ MCP server for [Conduyt CRM](https://conduyt.app) — expose your CRM as AI-acce
 | `conduyt_delete_pipeline` | Delete a pipeline (move/remove its deals first) |
 | `conduyt_create_stage` | Append a stage to a pipeline (e.g. 'On Hold', 'Declined/Dead') |
 | `conduyt_update_stage` | Rename, recolor, reorder, or change won/lost flags on a stage |
-| `conduyt_delete_stage` | Delete a stage from a pipeline; `moveTo` moves its live deals to another stage first, `expectedSettingsRevision` refuses the delete when settings changed (409 `stale_settings_revision`; the answer then carries the new `settingsRevision`) |
+| `conduyt_delete_stage` | Soft-delete a stage: an EMPTY stage can always be deleted (history kept, hidden from every list, GET / PATCH then 404, no restore in v1, name reusable); `moveTo` re-homes its live deals first, `expectedSettingsRevision` refuses the delete when settings changed (409 `stale_settings_revision`; the answer then carries the new `settingsRevision`). Refusals are 409s whose message is surfaced verbatim: deals in the stage, `used by N active automation(s) (names)`, DPP status map, `pipeline_archived`, `intake_target`. A run parked before the delete fails at that step with a clear reason |
 
 ### Activities
 | Tool | Description |
@@ -197,9 +197,19 @@ The Mailchimp OAuth connect and callback are browser-only: connect Mailchimp in
 ### Notifications
 | Tool | Description |
 |------|-------------|
-| `conduyt_list_notifications` | List notifications for current user |
+| `conduyt_list_notifications` | List notifications for current user; `meta.latestByType` is `{type: {latest, count}}` over the last 24 h (newest createdAt + row count per type, read state ignored) next to `unreadCount` / `unreadByType` |
 | `conduyt_create_notification` | Send in-app + push notification to a team member |
 
+### Team Chat
+| Tool | Description |
+|------|-------------|
+| `conduyt_list_chat_channels` | `GET /chat/channels`: your channels; also CREATES your memberships in the auto channels the first time |
+| `conduyt_get_chat_unread` | `GET /chat/unread`: per channel `{ channelId, unread, soundUnread, newestSeq, latestSeq }`; may list an auto channel you have not opened yet (no membership row) |
+| `conduyt_list_chat_messages` | List a channel's messages, newest first; every message carries `seq` (commit-ordered position in the channel); does not move the read marker; on a 403 "Not a member of this channel" it calls `GET /chat/channels` once and retries once |
+| `conduyt_mark_chat_read` | Acknowledge read up to one message (`readUpTo` = message UUID; the marker only moves forward, an older or foreign message is a no-op; same one-retry membership bootstrap) |
+
+The rest of team chat (sending, reactions, pins, presence, uploads) is not wrapped yet; `GET /chat/messages/{messageId}/location` is a UI deep-link helper and deliberately not wrapped.
+
 ### Custom Fields
 | Tool | Description |
 |------|-------------|

package/dist/index.js

@@ -26,6 +26,7 @@ import { registerBoardSettingsTools } from "./tools/board-settings.js";
 import { registerMailchimpTools } from "./tools/mailchimp.js";
 import { registerStatusMetadataTools } from "./tools/status-metadata.js";
 import { registerNotificationTools } from "./tools/notifications.js";
+import { registerChatTools } from "./tools/chat.js";
 import { registerCustomFieldTools } from "./tools/custom-fields.js";
 import { registerSmartListTools } from "./tools/smart-lists.js";
 import { registerUserTools } from "./tools/users.js";
@@ -102,6 +103,7 @@ registerBoardSettingsTools(server, client);
 registerMailchimpTools(server, client);
 registerStatusMetadataTools(server, client);
 registerNotificationTools(server, client);
+registerChatTools(server, client);
 registerCustomFieldTools(server, client);
 registerSmartListTools(server, client);
 registerUserTools(server, client);

package/dist/tools/chat.d.ts

@@ -0,0 +1,6 @@
+import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
+import { ConduytClient } from "../client.js";
+/** The messages route's membership refusal (403 "Not a member of this channel"); any other 403 (a permission) is NOT this. */
+export declare function isMembershipRefusal(err: unknown): boolean;
+/** Team chat read side (app 10-09, live sha 3869c79ba): the unread vector, messages carrying `seq`, and the read acknowledgement. */
+export declare function registerChatTools(server: McpServer, client: ConduytClient): void;

package/dist/tools/chat.js

@@ -0,0 +1,55 @@
+import { z } from "zod";
+import { ConduytApiError, formatResult } from "../client.js";
+import { strictInput } from "./strict.js";
+/** The messages route's membership refusal (403 "Not a member of this channel"); any other 403 (a permission) is NOT this. */
+export function isMembershipRefusal(err) {
+    return err instanceof Error && /\b403\b/.test(err.message) && /Not a member of this channel/.test(err.message)
+        && (!(err instanceof ConduytApiError) || err.status === 403);
+}
+/**
+ * GET /chat/unread lists the AUTO channels even when the caller has no membership row yet, while the messages route answers
+ * 403 without one; GET /chat/channels is what lazily creates it. So on that one refusal: call GET /chat/channels ONCE, retry
+ * the read ONCE. Bounded: a second refusal, or a 403 for any other reason, reaches the caller untouched.
+ */
+async function withMembershipBootstrap(client, read) {
+    try {
+        return await read();
+    }
+    catch (err) {
+        if (!isMembershipRefusal(err))
+            throw err;
+        await client.get("/api/v1/chat/channels");
+        return read();
+    }
+}
+/** Team chat read side (app 10-09, live sha 3869c79ba): the unread vector, messages carrying `seq`, and the read acknowledgement. */
+export function registerChatTools(server, client) {
+    strictInput(server.tool("conduyt_list_chat_channels", "List the team chat channels the API key's user belongs to (GET /api/v1/chat/channels): id, name, kind, members, last message, counts. SIDE EFFECT: it also creates the caller's memberships in the account's AUTO channels (needs-a-hand, new-leads, wins) the first time, so a user who never opened Team Chat can read them. conduyt_list_chat_messages and conduyt_mark_chat_read already do this once for you when a channel listed by conduyt_get_chat_unread answers 403 'Not a member of this channel'; call this tool directly to discover channel ids.", {}, async () => {
+        const result = await client.get("/api/v1/chat/channels");
+        return formatResult(result);
+    }));
+    strictInput(server.tool("conduyt_get_chat_unread", "Team chat unread vector for the API key's user (GET /api/v1/chat/unread): one row per channel the user is a member of, { channelId, unread, soundUnread, newestSeq, latestSeq }. unread is the badge count (auto channels are 0 by design); soundUnread counts unread messages in every channel, auto ones included; newestSeq is the seq of the channel's newest message not written by the user (null = none, panic cards left out); latestSeq is the same including panic cards. Read-only: no writes, never creates a membership, so a row can be an AUTO channel the caller has not opened yet (no membership row: reading it first answers 403, which conduyt_list_chat_messages / conduyt_mark_chat_read recover from by calling conduyt_list_chat_channels once and retrying once). Use it to decide which channel to read next, then conduyt_list_chat_messages.", {}, async () => {
+        const result = await client.get("/api/v1/chat/unread");
+        return formatResult(result);
+    }));
+    strictInput(server.tool("conduyt_list_chat_messages", "List messages in a team chat channel (GET /api/v1/chat/channels/{id}/messages), newest first, paged by cursor. The caller must be a channel member (else 403). Every message carries seq, its commit-ordered position inside the channel (a total order: the list and the cursor follow it). Read-only: this tool does not move the read marker. On a 403 'Not a member of this channel' it calls GET /chat/channels once (which creates the caller's auto-channel memberships) and retries ONCE; a second refusal, or a 403 for any other reason, is returned as is; acknowledge with conduyt_mark_chat_read.", {
+        channelId: z.string().uuid().describe("Channel UUID"),
+        limit: z.number().int().min(1).max(100).optional().describe("Messages per page (1-100, default 50)"),
+        cursor: z.string().uuid().optional().describe("nextCursor from the previous page (a message UUID)"),
+    }, async ({ channelId, limit, cursor }) => {
+        const params = new URLSearchParams();
+        if (limit !== undefined)
+            params.set("limit", String(limit));
+        if (cursor !== undefined)
+            params.set("cursor", cursor);
+        const result = await withMembershipBootstrap(client, () => client.get(`/api/v1/chat/channels/${channelId}/messages?${params}`));
+        return formatResult(result);
+    }));
+    strictInput(server.tool("conduyt_mark_chat_read", "Acknowledge team chat as read up to one message (GET /api/v1/chat/channels/{id}/messages?readUpTo=<messageId>&limit=1; the API takes the acknowledgement as a query on the message list). readUpTo is the UUID of a message you were served (its seq becomes your read marker); take it from conduyt_list_chat_messages. The marker only moves FORWARD, never to 'now': an older (stale) message is a no-op, and a message that is not in this channel moves nothing (the call still succeeds, so re-check conduyt_get_chat_unread). A malformed id is a 400. On a 403 'Not a member of this channel' it calls GET /chat/channels once (creating the caller's auto-channel memberships) and retries ONCE; a second refusal, or a 403 for any other reason, is returned as is. The response is the newest message of the channel (limit 1), not a confirmation of the move.", {
+        channelId: z.string().uuid().describe("Channel UUID"),
+        readUpTo: z.string().uuid().describe("UUID of the newest message you have seen in this channel"),
+    }, async ({ channelId, readUpTo }) => {
+        const result = await withMembershipBootstrap(client, () => client.get(`/api/v1/chat/channels/${channelId}/messages?limit=1&readUpTo=${readUpTo}`));
+        return formatResult(result);
+    }));
+}

package/dist/tools/notifications.js

@@ -1,7 +1,7 @@
 import { z } from "zod";
 import { formatResult } from "../client.js";
 export function registerNotificationTools(server, client) {
-    server.tool("conduyt_list_notifications", "List notifications for the current user (determined by API key's associated user).", {
+    server.tool("conduyt_list_notifications", "List notifications for the current user (determined by API key's associated user). The response meta carries page, per_page, total, unreadCount, unreadByType ({type: count}) and latestByType ({type: {latest, count}}: per type over the last 24 hours, the newest createdAt as an ISO string and the row count, read state ignored; a poller sees a type advance when latest moves or count rises).", {
         page: z.number().optional().describe("Page number (default 1)"),
         per_page: z.number().optional().describe("Results per page"),
     }, async ({ page, per_page }) => {

package/dist/tools/pipelines.js

@@ -9,7 +9,7 @@ export const ARCHIVE_ERROR_CODES = "A refusal carries a machine-readable code in
 /** above the archive route's 60 s transaction (up to 500 deal moves) plus post-commit events; the client default is 30 s */
 export const ARCHIVE_PIPELINE_TIMEOUT_MS = 75_000;
 export function registerPipelineTools(server, client) {
-    server.tool("conduyt_list_pipelines", "List all active sales pipelines with their stages. Use this to discover pipeline and stage UUIDs before creating or moving deals. Each pipeline carries color (one of the 10 palette hex colours, or null until the settings page saves one), automationOnly and sortOrder (the board-menu order); an archived pipeline's pre-archive name is archivedFromName (see conduyt_list_archived_pipelines).", {}, async () => {
+    server.tool("conduyt_list_pipelines", "List all active sales pipelines with their stages (soft-deleted stages are never included). Use this to discover pipeline and stage UUIDs before creating or moving deals. Each pipeline carries color (one of the 10 palette hex colours, or null until the settings page saves one), automationOnly and sortOrder (the board-menu order); an archived pipeline's pre-archive name is archivedFromName (see conduyt_list_archived_pipelines).", {}, async () => {
         const result = await client.get("/api/v1/pipelines");
         return formatResult(result);
     });
@@ -90,7 +90,7 @@ export function registerPipelineTools(server, client) {
         const result = await client.post("/api/v1/pipelines/reorder", { order, expectedRevision });
         return formatResult(result);
     }));
-    server.tool("conduyt_create_stage", "Add a new stage to an existing pipeline. The stage is appended after the current last stage. Use this to extend a funnel (e.g. add 'On Hold' or 'Declined/Dead').", {
+    server.tool("conduyt_create_stage", "Add a new stage to an existing pipeline. The stage is appended after the current last stage. Use this to extend a funnel (e.g. add 'On Hold' or 'Declined/Dead'). A name may be reused after the old stage of that name was deleted (deleted stages are soft-deleted and hidden).", {
         pipelineId: z.string().describe("Pipeline UUID to add the stage to"),
         name: z.string().describe("Stage name"),
         color: z.string().optional().describe("Hex color, e.g. '#3B82F6'"),
@@ -107,7 +107,7 @@ export function registerPipelineTools(server, client) {
         });
         return formatResult(result);
     });
-    server.tool("conduyt_update_stage", "Update a stage within a pipeline — rename, recolor, reorder (sortOrder), or change its won/lost/system flags.", {
+    server.tool("conduyt_update_stage", "Update a stage within a pipeline — rename, recolor, reorder (sortOrder), or change its won/lost/system flags. A soft-deleted stage (conduyt_delete_stage) answers 404.", {
         pipelineId: z.string().describe("Pipeline UUID"),
         stageId: z.string().describe("Stage UUID to update"),
         name: z.string().optional().describe("Updated stage name"),
@@ -128,7 +128,7 @@ export function registerPipelineTools(server, client) {
         const result = await client.post(`/api/v1/pipelines/${pipelineId}/stages/reorder`, { order, expectedRevision });
         return formatResult(result);
     }));
-    strictInput(server.tool("conduyt_delete_stage", "Delete a stage from a pipeline. Strict input: the guards are spelled moveTo and expectedSettingsRevision, any other spelling (move_to, expected_settings_revision, a typo) is InvalidParams and nothing is deleted. The stage must be empty (no deals) unless moveTo names another stage of the same pipeline (same won / lost setting, not a system stage): its live deals then move there and the stage is deleted in one transaction. A stage a soft-deleted deal still points at is refused. Pass expectedSettingsRevision (the settingsRevision from conduyt_get_settings_revision, read right before) to refuse the delete when settings changed since you read them; the answer is then { id, deleted: true, settingsRevision } with the revision after the delete. A refusal carries a machine-readable code in the error text and the server's message, never swallowed: stale_settings_revision (409), pipeline_archived (409), intake_target (409, enabled intake routes deals into this stage); other 409s (DPP status map, unattended-lead automations, deals that used the stage) have no code but name the cause.", {
+    strictInput(server.tool("conduyt_delete_stage", "Delete a stage from a pipeline (soft delete). Strict input: the guards are spelled moveTo and expectedSettingsRevision, any other spelling (move_to, expected_settings_revision, a typo) is InvalidParams and nothing is deleted. An EMPTY stage can always be deleted, even if deals once used it: the row is kept so deal history, activities, audit rows and reports keep its name, but the stage is hidden from every pipeline and stage list, GET / PATCH on it answer 404, there is NO restore in v1, and its name may be reused by a new stage. Its stage rule, appointment-outcome mappings and status metadata are removed with it. With moveTo (another stage of the same pipeline, same won / lost setting, not a system stage) its live deals move there and the stage is deleted in one transaction. Pass expectedSettingsRevision (the settingsRevision from conduyt_get_settings_revision, read right before) to refuse the delete when settings changed since you read them; the answer is then { id, deleted: true, settingsRevision } with the revision after the delete. A refusal is a 409 whose server message is surfaced verbatim (never swallowed, never retried): deals currently in the stage and no moveTo (\"Cannot delete stage: N deal(s) are in this stage...\"), \"Cannot delete stage: it is used by N active automation(s) (names). Change their stage or pause them first.\" (a published automation references the stage in an action, trigger, condition or wait-until), the DPP status map selects it, plus the coded refusals stale_settings_revision, pipeline_archived and intake_target (enabled intake routes deals into this stage); a moveTo that is not a valid target is a 400. Accepted window: a run parked or in flight before the delete is not tracked; at the step that targets the deleted stage it fails or is skipped with a clear reason in the execution log.", {
         pipelineId: z.string().describe("Pipeline UUID"),
         stageId: z.string().describe("Stage UUID to delete"),
         moveTo: z.string().uuid().optional().describe("Another stage of the same pipeline the live deals move to (sent as move_to)"),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "conduyt-mcp",
-  "version": "4.77.0",
+  "version": "4.79.0",
   "mcpName": "com.conduyt/mcp",
   "description": "MCP server for Conduyt CRM — expose CRM operations as AI-accessible tools",
   "type": "module",

package/scripts/coverage-manifest.json

@@ -115,6 +115,11 @@
       "status": "planned",
       "reason": "file listing/metadata is agent-useful; upload stays browser-side"
     },
+    {
+      "match": "GET /api/v1/chat/messages/",
+      "status": "excluded",
+      "reason": "UI-only deep-link helper (resolves a message to its channel/position for the app's router); not an agent surface"
+    },
     {
       "match": "/api/v1/chat",
       "status": "planned",

package/scripts/coverage-matrix.json

@@ -1,11 +1,11 @@
 {
-  "generatedAt": "2026-10-09T02:56:11.306Z",
-  "toolCount": 330,
-  "totalEndpoints": 1064,
+  "generatedAt": "2026-10-09T04:00:29.593Z",
+  "toolCount": 334,
+  "totalEndpoints": 1066,
   "counts": {
-    "covered": 296,
-    "excluded": 318,
-    "planned": 450,
+    "covered": 299,
+    "excluded": 319,
+    "planned": 448,
     "uncategorized": 0
   },
   "matrix": {
@@ -1235,8 +1235,10 @@
       "reason": "team chat read/post for agents"
     },
     "GET /api/v1/chat/channels": {
-      "status": "planned",
-      "reason": "team chat read/post for agents"
+      "status": "covered",
+      "tools": [
+        "conduyt_list_chat_channels"
+      ]
     },
     "POST /api/v1/chat/channels": {
       "status": "planned",
@@ -1251,8 +1253,11 @@
       "reason": "team chat read/post for agents"
     },
     "GET /api/v1/chat/channels/:id/messages": {
-      "status": "planned",
-      "reason": "team chat read/post for agents"
+      "status": "covered",
+      "tools": [
+        "conduyt_list_chat_messages",
+        "conduyt_mark_chat_read"
+      ]
     },
     "POST /api/v1/chat/channels/:id/messages": {
       "status": "planned",
@@ -1318,6 +1323,10 @@
       "status": "planned",
       "reason": "team chat read/post for agents"
     },
+    "GET /api/v1/chat/messages/:messageId/location": {
+      "status": "excluded",
+      "reason": "UI-only deep-link helper (resolves a message to its channel/position for the app's router); not an agent surface"
+    },
     "GET /api/v1/chat/presence": {
       "status": "planned",
       "reason": "team chat read/post for agents"
@@ -1326,6 +1335,12 @@
       "status": "planned",
       "reason": "team chat read/post for agents"
     },
+    "GET /api/v1/chat/unread": {
+      "status": "covered",
+      "tools": [
+        "conduyt_get_chat_unread"
+      ]
+    },
     "GET /api/v1/companies": {
       "status": "covered",
       "tools": [