capsulemcp 1.8.1 → 2.0.1

package/dist/index.js

@@ -138,6 +138,26 @@ function invalidateByPrefix(pathPrefix, trigger) {
   }
 }
 
+// src/capsule/normalize.ts
+var KEY_RENAMES = {
+  kase: "project",
+  kases: "projects",
+  restrictedKases: "restrictedProjects"
+};
+function normalizeProjectKeys(value) {
+  if (Array.isArray(value)) {
+    return value.map(normalizeProjectKeys);
+  }
+  if (value !== null && typeof value === "object") {
+    const out = {};
+    for (const [key, v] of Object.entries(value)) {
+      out[KEY_RENAMES[key] ?? key] = normalizeProjectKeys(v);
+    }
+    return out;
+  }
+  return value;
+}
+
 // src/capsule/client.ts
 var DEFAULT_BASE_URL = "https://api.capsulecrm.com/api/v2";
 function baseUrl() {
@@ -409,7 +429,8 @@ async function throwForStatus(res) {
 }
 async function handleResponse(res) {
   await throwForStatus(res);
-  return mapAbort(res.json());
+  const body = await mapAbort(res.json());
+  return normalizeProjectKeys(body);
 }
 function buildUrl(path, params) {
   const url = new URL(`${baseUrl()}${path}`);
@@ -651,6 +672,7 @@ var CORE_TOOLS = /* @__PURE__ */ new Set([
   "create_opportunity",
   "update_opportunity",
   // Projects
+  "search_projects",
   "filter_projects",
   "list_projects",
   "get_project",
@@ -1148,10 +1170,6 @@ function defineBatch(args) {
   return { schema, handler };
 }
 
-// src/tools/descriptions.ts
-var EMBED_TAGS_FIELDS_DESCRIPTION = "Comma-separated embeds, e.g. 'tags,fields'";
-var EMBED_ATTACHMENTS_PARTICIPANTS_DESCRIPTION = "Comma-separated embeds, e.g. 'attachments,participants'";
-
 // src/tools/define-delete.ts
 import { z as z5 } from "zod";
 
@@ -1177,6 +1195,26 @@ var paginationFieldsNoDefaults = {
   page: z4.number().int().positive().optional(),
   perPage: z4.number().int().min(1).max(100).optional()
 };
+var ENTITY_PATH = {
+  parties: "parties",
+  opportunities: "opportunities",
+  projects: "kases"
+};
+function embedParam(allowed) {
+  return z4.string().superRefine((value, ctx) => {
+    const tokens = value.split(",").map((t) => t.trim());
+    for (const token of tokens) {
+      if (token === "" || !allowed.includes(token)) {
+        ctx.addIssue({
+          code: "custom",
+          message: `Unknown embed token '${token}'. Valid tokens: ${allowed.join(", ")} (comma-separated). Capsule silently ignores unknown tokens, so this is rejected client-side to prevent silently-missing data.`
+        });
+      }
+    }
+  }).describe(`Comma-separated embeds. Valid tokens: ${allowed.join(", ")}.`).optional();
+}
+var RECORD_EMBEDS = ["tags", "fields", "missingImportantFields"];
+var ENTRY_EMBEDS = ["attachments", "participants"];
 
 // src/capsule/idempotent.ts
 var isCapsule404 = (err) => err instanceof CapsuleApiError && err.status === 404;
@@ -1341,7 +1379,7 @@ var WebsiteSchema = z7.object({
 }).superRefine(validateWebsiteAddress);
 var searchPartiesSchema = z7.object({
   q: z7.string().optional().describe("Free-text search query"),
-  embed: z7.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION),
+  embed: embedParam(RECORD_EMBEDS),
   ...paginationFields
 });
 async function searchParties(input) {
@@ -1355,7 +1393,7 @@ async function searchParties(input) {
 }
 var getPartySchema = z7.object({
   id: positiveId.describe("Party ID"),
-  embed: z7.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION)
+  embed: embedParam(RECORD_EMBEDS)
 });
 async function getParty(input) {
   const { data } = await capsuleGet(`/parties/${input.id}`, {
@@ -1367,7 +1405,7 @@ var getPartiesSchema = z7.object({
   ids: z7.array(positiveId).min(1).max(50).describe(
     "Array of party IDs (1\u201350). Capsule's native batch-fetch endpoint caps at 10 per request; the connector transparently splits larger sets into 10-id chunks and fans out the Capsule calls in parallel. Result shape is identical regardless of input size."
   ),
-  embed: z7.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION)
+  embed: embedParam(RECORD_EMBEDS)
 });
 async function getParties(input) {
   return chunkedMultiGet("/parties", "parties", input.ids, { embed: input.embed });
@@ -1407,7 +1445,7 @@ var PartyWriteBaseSchema = {
     "APPEND-ONLY: items are merged into the existing list, never replaced. For atomic add/remove/replace use add_party_website and remove_party_website_by_id."
   ),
   ownerId: positiveId.nullable().optional().describe(
-    "Pass a user ID to set, or `null` to unassign (verified empirically in v1.6.4 wire-trace \u2014 Capsule accepts `owner: null` on PUT /parties/:id for both persons and organisations). Discover IDs via list_users. WARNING: Capsule's PUT on /parties has the same asymmetric owner/team semantic documented in NOTES-ON-CAPSULE-API.md \xA727 for /kases \u2014 setting `owner` while omitting `team` is plausibly clearing-prone. When you supply `ownerId` and omit `teamId`, this connector reads the party's current team and includes it in the PUT body to preserve it across the owner change. Supply `teamId` explicitly to change it."
+    "Pass a user ID to set, or `null` to unassign (verified empirically in v1.6.4 wire-trace \u2014 Capsule accepts `owner: null` on PUT /parties/:id for both persons and organisations). Discover IDs via list_users. WARNING: Capsule's PUT on parties has the same asymmetric owner/team semantic documented in NOTES-ON-CAPSULE-API.md \xA727 for project updates \u2014 setting `owner` while omitting `team` is plausibly clearing-prone. When you supply `ownerId` and omit `teamId`, this connector reads the party's current team and includes it in the PUT body to preserve it across the owner change. Supply `teamId` explicitly to change it."
   ),
   teamId: positiveId.nullable().optional().describe(
     "Assign to team ID (discover via list_teams). Pass a team ID to set, or `null` to unassign. Capsule enforces the owner\u2208team membership constraint \u2014 passing a team the current owner doesn't belong to returns 422 'owner is not a member of the team'. Combine `ownerId: null` + `teamId: <T>` in one call to transfer a party to team-ownership with no specific user (verified empirically in v1.6.4 wire-trace; the membership rule doesn't fire when owner is null)."
@@ -1433,6 +1471,21 @@ var createPartySchema = z7.object({
   fields: z7.array(CustomFieldWriteSchema).optional().describe(
     fieldsArrayDescriptor("get_party") + " Verified empirically in v1.6.5 wire-trace: Capsule's POST /parties accepts the same `fields[]` shape as PUT, so callers can set custom field values on creation without a follow-up update."
   )
+}).superRefine((data, ctx) => {
+  if (data.type === "person" && !data.firstName && !data.lastName) {
+    ctx.addIssue({
+      code: "custom",
+      path: ["firstName"],
+      message: "create_party: a person requires firstName and/or lastName"
+    });
+  }
+  if (data.type === "organisation" && !data.name) {
+    ctx.addIssue({
+      code: "custom",
+      path: ["name"],
+      message: "create_party: an organisation requires name"
+    });
+  }
 });
 async function createParty(input) {
   const { ownerId, teamId, organisationId, fields, ...rest } = input;
@@ -1483,7 +1536,7 @@ var { schema: batchUpdatePartySchema, handler: batchUpdateParty } = defineBatch(
 var { schema: deletePartySchema, handler: deleteParty } = defineDelete({
   toolName: "delete_party",
   pathPrefix: "/parties",
-  confirmHint: "Must be set to true. Deletes the party AND all linked notes, tasks, opportunities, and projects (kases). Deleting an ORGANISATION does NOT delete people linked to it via organisationId \u2014 their `organisation` field is silently cleared to null and they survive as standalone records. Irreversible."
+  confirmHint: "Must be set to true. Deletes the party AND all linked notes, tasks, opportunities, and projects. Deleting an ORGANISATION does NOT delete people linked to it via organisationId \u2014 their `organisation` field is silently cleared to null and they survive as standalone records. Irreversible."
 });
 function definePartySubResourceRemove(opts) {
   const shape = {
@@ -1618,7 +1671,7 @@ var OpportunityValueSchema = z8.object({
 });
 var searchOpportunitiesSchema = z8.object({
   q: z8.string().optional().describe("Free-text search query"),
-  embed: z8.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION),
+  embed: embedParam(RECORD_EMBEDS),
   ...paginationFields
 });
 async function searchOpportunities(input) {
@@ -1632,7 +1685,7 @@ async function searchOpportunities(input) {
 }
 var getOpportunitySchema = z8.object({
   id: positiveId,
-  embed: z8.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION)
+  embed: embedParam(RECORD_EMBEDS)
 });
 async function getOpportunity(input) {
   const { data } = await capsuleGet(`/opportunities/${input.id}`, {
@@ -1644,7 +1697,7 @@ var getOpportunitiesSchema = z8.object({
   ids: z8.array(positiveId).min(1).max(50).describe(
     "Array of opportunity IDs (1\u201350). Capsule's native batch-fetch endpoint caps at 10 per request; the connector transparently splits larger sets into 10-id chunks and fans out the Capsule calls in parallel."
   ),
-  embed: z8.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION)
+  embed: embedParam(RECORD_EMBEDS)
 });
 async function getOpportunities(input) {
   return chunkedMultiGet("/opportunities", "opportunities", input.ids, { embed: input.embed });
@@ -1666,7 +1719,7 @@ var createOpportunitySchema = z8.object({
     "Assign to team ID (discover via list_teams). Independent from `ownerId` \u2014 setting one does NOT clear the other on create. Three ownership shapes are valid: owner alone, team alone, or owner+team (the owner must be a member of the team; users can belong to multiple teams \u2014 422 'owner is not a member of the team' otherwise)."
   ),
   fields: z8.array(CustomFieldWriteSchema).optional().describe(
-    fieldsArrayDescriptor("get_opportunity") + " Capsule's POST /opportunities accepts the same `fields[]` shape as PUT (inferred by symmetry with the v1.6.5 wire-trace findings on POST /parties and POST /kases \u2014 the tenant probed had no opportunity custom fields configured, so this is unverified empirically). Setting custom fields on creation removes the create-then-update ritual."
+    fieldsArrayDescriptor("get_opportunity") + " Capsule's POST /opportunities accepts the same `fields[]` shape as PUT (inferred by symmetry with the v1.6.5 wire-trace findings on party and project creation \u2014 the tenant probed had no opportunity custom fields configured, so this is unverified empirically). Setting custom fields on creation removes the create-then-update ritual."
   )
 });
 async function createOpportunity(input) {
@@ -1698,10 +1751,10 @@ var updateOpportunitySchema = z8.object({
     "Win probability 0\u2013100. On an open milestone this overrides the milestone's default probability. CANNOT be set in the same call as a closing milestone (Won/Lost) \u2014 Capsule processes the milestone change first, the opportunity becomes closed, then the probability update is rejected as edit-on-closed-opp with 422 'probability can be updated only for open opportunity'. To close an opportunity, leave probability out of the call: it auto-snaps to 100% (Won) or 0% (Lost)."
   ),
   lostReasonId: positiveId.optional().describe(
-    "Reason the opportunity was lost. Only meaningful when transitioning to a Lost milestone \u2014 Capsule silently drops it for other milestones. Without this set, a connector-driven Lost-close leaves `lostReason: null`. Discover IDs via list_lostreasons."
+    "Reason the opportunity was lost. Only meaningful when transitioning to a Lost milestone \u2014 Capsule silently drops it for other milestones. Without this set, a connector-driven Lost-close leaves `lostReason: null`. Discover IDs via list_lost_reasons."
   ),
   ownerId: positiveId.nullable().optional().describe(
-    "Reassign owner: pass a user ID to set, or `null` to unassign (verified empirically in v1.6.5 wire-trace \u2014 Capsule accepts `owner: null` on PUT /opportunities/:id, mirroring the v1.6.4 finding on /parties; brings update_opportunity into parity with update_party and update_project). When you supply `ownerId` and omit `teamId`, the connector fetches the opportunity's current team and includes it in the PUT body to preserve it across the owner change. Without this defensive read, Capsule's PUT would clear the existing team (see NOTES-ON-CAPSULE-API.md \xA727 \u2014 same asymmetric semantic as /kases). Supply `teamId` explicitly on the same call to change the team instead. Combine `ownerId: null` + `teamId: <T>` in one call to transfer an opportunity to team-ownership with no specific user (verified empirically in v1.6.5; the owner-clears-team semantic doesn't fire when owner is being cleared to null)."
+    "Reassign owner: pass a user ID to set, or `null` to unassign (verified empirically in v1.6.5 wire-trace \u2014 Capsule accepts `owner: null` on PUT /opportunities/:id, mirroring the v1.6.4 finding on /parties; brings update_opportunity into parity with update_party and update_project). When you supply `ownerId` and omit `teamId`, the connector fetches the opportunity's current team and includes it in the PUT body to preserve it across the owner change. Without this defensive read, Capsule's PUT would clear the existing team (see NOTES-ON-CAPSULE-API.md \xA727 \u2014 same asymmetric semantic as project updates). Supply `teamId` explicitly on the same call to change the team instead. Combine `ownerId: null` + `teamId: <T>` in one call to transfer an opportunity to team-ownership with no specific user (verified empirically in v1.6.5; the owner-clears-team semantic doesn't fire when owner is being cleared to null)."
   ),
   teamId: positiveId.nullable().optional().describe(
     "Reassign team: pass a team ID (discover via list_teams) to set, or `null` to unassign. Capsule preserves the existing owner across a team change (server-side), so `update_opportunity { teamId }` alone is safe \u2014 the owner is carried through. Owner must be a member of the new team or Capsule returns 422 'owner is not a member of the team'. Independent from `ownerId` \u2014 setting `teamId` does NOT clear the owner."
@@ -1743,9 +1796,23 @@ var { schema: deleteOpportunitySchema, handler: deleteOpportunity } = defineDele
 
 // src/tools/projects.ts
 import { z as z9 } from "zod";
+var searchProjectsSchema = z9.object({
+  q: z9.string().optional().describe("Free-text search query"),
+  embed: embedParam(RECORD_EMBEDS),
+  ...paginationFields
+});
+async function searchProjects(input) {
+  const path = input.q ? "/kases/search" : "/kases";
+  return capsuleGetList(path, {
+    q: input.q,
+    embed: input.embed,
+    page: input.page,
+    perPage: input.perPage
+  });
+}
 var listProjectsSchema = z9.object({
   status: z9.enum(["OPEN", "CLOSED"]).optional(),
-  embed: z9.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION),
+  embed: embedParam(RECORD_EMBEDS),
   ...paginationFields
 });
 async function listProjects(input) {
@@ -1758,7 +1825,7 @@ async function listProjects(input) {
 }
 var getProjectSchema = z9.object({
   id: positiveId,
-  embed: z9.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION)
+  embed: embedParam(RECORD_EMBEDS)
 });
 async function getProject(input) {
   const { data } = await capsuleGet(`/kases/${input.id}`, {
@@ -1770,10 +1837,10 @@ var getProjectsSchema = z9.object({
   ids: z9.array(positiveId).min(1).max(50).describe(
     "Array of project IDs (1\u201350). Capsule's native batch-fetch endpoint caps at 10 per request; the connector transparently splits larger sets into 10-id chunks and fans out the Capsule calls in parallel."
   ),
-  embed: z9.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION)
+  embed: embedParam(RECORD_EMBEDS)
 });
 async function getProjects(input) {
-  return chunkedMultiGet("/kases", "kases", input.ids, { embed: input.embed });
+  return chunkedMultiGet("/kases", "projects", input.ids, { embed: input.embed });
 }
 var createProjectSchema = z9.object({
   name: z9.string().min(1),
@@ -1791,7 +1858,7 @@ var createProjectSchema = z9.object({
   ),
   expectedCloseOn: z9.string().regex(/^\d{4}-\d{2}-\d{2}$/).optional().describe("YYYY-MM-DD"),
   fields: z9.array(CustomFieldWriteSchema).optional().describe(
-    fieldsArrayDescriptor("get_project") + " Verified empirically in v1.6.5 wire-trace: Capsule's POST /kases accepts the same `fields[]` shape as PUT, so callers can set custom field values on creation without a follow-up update. Project-specific: setting a field whose definition lives under a 'data tag' populates the row's internal tagId but does NOT auto-add the data tag to the project's tags array \u2014 use add_tag explicitly if you want it visible via embed=tags."
+    fieldsArrayDescriptor("get_project") + " Verified empirically in v1.6.5 wire-trace: Capsule's project create endpoint accepts the same `fields[]` shape as PUT, so callers can set custom field values on creation without a follow-up update. Project-specific: setting a field whose definition lives under a 'data tag' populates the row's internal tagId but does NOT auto-add the data tag to the project's tags array \u2014 use add_tag explicitly if you want it visible via embed=tags."
   )
 });
 async function createProject(input) {
@@ -1823,7 +1890,7 @@ var updateProjectSchema = z9.object({
     "Reassign team: pass a team ID (discover via list_teams) to set, or `null` to unassign. Capsule preserves the existing owner across a team change (server-side), so `update_project { teamId }` alone is safe \u2014 the owner is carried through. Owner must be a member of the new team or Capsule returns 422 'owner is not a member of the team'. A project must always have at least one of {owner, team} set \u2014 `teamId: null` on a project whose owner is already null returns 422 'owner or team is required'."
   ),
   stageId: positiveId.nullable().optional().describe(
-    "Move the project to this stage (board column), or `null` to remove from all stages (verified empirically in v1.6.5 wire-trace \u2014 Capsule accepts `stage: null` on PUT /kases/:id and the project no longer appears on any board). Discover IDs via list_stages. Owner and team are preserved across stage-only updates (Capsule's PUT semantic). WARNING (cross-board): Capsule does NOT validate that the new stage belongs to the project's current board \u2014 passing a stageId from a different board silently relocates the project across boards. Team and other board-derived defaults are NOT updated to match the new board. Verify against the project's current board (read the project first, list its board's stages) before passing a cross-board id."
+    "Move the project to this stage (board column), or `null` to remove from all stages (verified empirically in v1.6.5 wire-trace \u2014 Capsule accepts `stage: null` on project update and the project no longer appears on any board). Discover IDs via list_stages. Owner and team are preserved across stage-only updates (Capsule's PUT semantic). WARNING (cross-board): Capsule does NOT validate that the new stage belongs to the project's current board \u2014 passing a stageId from a different board silently relocates the project across boards. Team and other board-derived defaults are NOT updated to match the new board. Verify against the project's current board (read the project first, list its board's stages) before passing a cross-board id."
   ),
   expectedCloseOn: z9.string().regex(/^\d{4}-\d{2}-\d{2}$/).optional().describe("YYYY-MM-DD"),
   fields: z9.array(CustomFieldWriteSchema).optional().describe(
@@ -1840,7 +1907,7 @@ async function updateProject(input) {
   let resolvedTeamId = teamId;
   let resolvedStageId = stageId;
   if (ownerId !== void 0 && (teamId === void 0 || stageId === void 0)) {
-    const current = await readEntityRefs(`/kases/${id}`, "kase");
+    const current = await readEntityRefs(`/kases/${id}`, "project");
     if (teamId === void 0) resolvedTeamId = current.teamId;
     if (stageId === void 0) resolvedStageId = current.stageId;
   }
@@ -1861,7 +1928,7 @@ var { schema: batchUpdateProjectSchema, handler: batchUpdateProject } = defineBa
 var { schema: deleteProjectSchema, handler: deleteProject } = defineDelete({
   toolName: "delete_project",
   pathPrefix: "/kases",
-  confirmHint: "Must be set to true. Permanently deletes the project (case). Consider update_project status='CLOSED' instead. Irreversible."
+  confirmHint: "Must be set to true. Permanently deletes the project. Consider update_project status='CLOSED' instead. Irreversible."
 });
 
 // src/tools/tasks.ts
@@ -1949,7 +2016,7 @@ var updateTaskSchema = z10.object({
     "Re-link the task to an opportunity by id, or `null` to orphan it. Mutually exclusive with `partyId` / `projectId` \u2014 see `partyId` for the XOR semantic."
   ),
   projectId: positiveId.nullable().optional().describe(
-    "Re-link the task to a project (kase) by id, or `null` to orphan it. Mutually exclusive with `partyId` / `opportunityId` \u2014 see `partyId` for the XOR semantic."
+    "Re-link the task to a project by id, or `null` to orphan it. Mutually exclusive with `partyId` / `opportunityId` \u2014 see `partyId` for the XOR semantic."
   )
 });
 async function updateTask(input) {
@@ -1991,13 +2058,13 @@ var { schema: deleteTaskSchema, handler: deleteTask } = defineDelete({
 import { z as z11 } from "zod";
 var listEntriesPagination = {
   ...paginationFields,
-  embed: z11.string().optional().describe(EMBED_ATTACHMENTS_PARTICIPANTS_DESCRIPTION)
+  embed: embedParam(ENTRY_EMBEDS)
 };
 var listPartyEntriesSchema = z11.object({
   partyId: positiveId,
   ...listEntriesPagination,
   includeLinkedPersons: z11.boolean().optional().describe(
-    "When true AND `partyId` is an ORGANISATION, also include entries filed against the organisation's linked people (the persons whose `organisation` field references this org). The connector enumerates linked persons via `GET /parties/{orgId}/people`, fans out `GET /parties/{personId}/entries` in parallel (concurrency-capped, default 5 / configurable via `CAPSULE_MCP_BATCH_CONCURRENCY`), and merges into a single feed sorted by `entryAt` descending, deduped by entry id. Default is `false` \u2014 single GET, existing behaviour unchanged. WHY THIS FLAG EXISTS: Capsule's API files each entry against exactly one party row (verified v1.6.6 wire-trace probe 4 \u2014 POST /entries rejects multi-party bodies with 422 'entry must be linked to either a party, opportunity or kase'). For an organisation with multiple contacts, captured emails almost always land on a person row, not the org. As a result, `list_party_entries(orgId)` with `includeLinkedPersons: false` will miss recent customer-facing email \u2014 even though the org's own `lastContactedAt` is updated by the activity. This flag is the correct call for any 'what's new with $ORG?' question. WHEN `partyId` IS A PERSON: silently no-op \u2014 persons have no linked-people relationship in Capsule's data model, so the flag is functionally inert (the connector still issues a cheap `/people` check; the response is empty). LATENCY: 1 + N round trips for an org with N linked people, concurrency-capped (typical: 2-3 waves for N=10). Linked-person enumeration reads the first 100 linked people; use list_employees for explicit pagination when an organisation has more contacts than that. Use `includeLinkedPersons: false` for fast pre-screen reads where you only need the org-row entries (e.g. invoice/contract notes that are typically filed at the org level). PAGINATION CAVEAT: `page` and `perPage` apply to the MERGED window, and the merge has a hard ceiling \u2014 it reliably orders only the most-recent ~100 entries across the org + its people (each party is fetched at Capsule's per-party cap of 100, and a top-100-per-party merge is correct only up to global position 100). Windows that cross the ceiling are truncated to the entries still inside that top-100 set; windows starting beyond it return no entries and end the feed. It does NOT continue into older history. To read a specific contact's full timeline beyond the merged ceiling, call `list_party_entries` on that person's id directly (the default single-GET path paginates natively with no ceiling). For the LLM-driven 'what's the latest with $ORG' query this is the typical use of, the first page is exact and the ceiling is never reached."
+    "When true AND `partyId` is an ORGANISATION, also include entries filed against the organisation's linked people (the persons whose `organisation` field references this org). The connector enumerates linked persons via `GET /parties/{orgId}/people`, fans out `GET /parties/{personId}/entries` in parallel (concurrency-capped, default 5 / configurable via `CAPSULE_MCP_BATCH_CONCURRENCY`), and merges into a single feed sorted by `entryAt` descending, deduped by entry id. Default is `false` \u2014 single GET, existing behaviour unchanged. WHY THIS FLAG EXISTS: Capsule's API files each entry against exactly one party, opportunity, or project row (verified v1.6.6 wire-trace probe 4 \u2014 POST /entries rejects multi-party bodies with 422). For an organisation with multiple contacts, captured emails almost always land on a person row, not the org. As a result, `list_party_entries(orgId)` with `includeLinkedPersons: false` will miss recent customer-facing email \u2014 even though the org's own `lastContactedAt` is updated by the activity. This flag is the correct call for any 'what's new with $ORG?' question. WHEN `partyId` IS A PERSON: silently no-op \u2014 persons have no linked-people relationship in Capsule's data model, so the flag is functionally inert (the connector still issues a cheap `/people` check; the response is empty). LATENCY: 1 + N round trips for an org with N linked people, concurrency-capped (typical: 2-3 waves for N=10). Linked-person enumeration reads the first 100 linked people; use list_employees for explicit pagination when an organisation has more contacts than that. Use `includeLinkedPersons: false` for fast pre-screen reads where you only need the org-row entries (e.g. invoice/contract notes that are typically filed at the org level). PAGINATION CAVEAT: `page` and `perPage` apply to the MERGED window, and the merge has a hard ceiling \u2014 it reliably orders only the most-recent ~100 entries across the org + its people (each party is fetched at Capsule's per-party cap of 100, and a top-100-per-party merge is correct only up to global position 100). Windows that cross the ceiling are truncated to the entries still inside that top-100 set; windows starting beyond it return no entries and end the feed. It does NOT continue into older history. To read a specific contact's full timeline beyond the merged ceiling, call `list_party_entries` on that person's id directly (the default single-GET path paginates natively with no ceiling). For the LLM-driven 'what's the latest with $ORG' query this is the typical use of, the first page is exact and the ceiling is never reached."
   )
 });
 var PER_PARTY_FETCH_CAP = 100;
@@ -2099,7 +2166,7 @@ async function listProjectEntries(input) {
 }
 var getEntrySchema = z11.object({
   id: positiveId,
-  embed: z11.string().optional().describe(EMBED_ATTACHMENTS_PARTICIPANTS_DESCRIPTION)
+  embed: embedParam(ENTRY_EMBEDS)
 });
 async function getEntry(input) {
   const { data } = await capsuleGet(`/entries/${input.id}`, {
@@ -2212,16 +2279,16 @@ import { z as z14 } from "zod";
 var TAG_LIST_PATH = {
   parties: "/parties/tags",
   opportunities: "/opportunities/tags",
-  kases: "/kases/tags"
+  projects: "/kases/tags"
 };
 var ENTITY_TO_WRAPPER = {
   parties: "party",
   opportunities: "opportunity",
-  kases: "kase"
+  projects: "kase"
 };
-var TagEntity = z14.enum(["parties", "opportunities", "kases"]).describe("Which entity type. Use 'kases' for projects (Capsule's legacy path name).");
+var TagEntity = z14.enum(["parties", "opportunities", "projects"]).describe("Which entity type.");
 var listTagsSchema = z14.object({
-  entity: z14.enum(["parties", "opportunities", "kases"]).describe("The resource type to list tags for"),
+  entity: z14.enum(["parties", "opportunities", "projects"]).describe("The resource type to list tags for"),
   ...paginationFieldsNoDefaults
 });
 async function listTags(input) {
@@ -2233,7 +2300,7 @@ async function listTags(input) {
 }
 var addTagSchema = z14.object({
   entity: TagEntity,
-  entityId: positiveId.describe("The party/opportunity/kase id."),
+  entityId: positiveId.describe("The party/opportunity/project id."),
   tagName: z14.string().min(1).describe(
     "Name of the tag to attach. Capsule resolves by name: if a tag with this name already exists in the tenant it is attached to the entity; if not, Capsule creates the tag and attaches it. Names are tenant-global. Capsule matches case-INSENSITIVELY when resolving (so 'VIP' and 'vip' attach the same tag), preserving the canonical casing from whichever variant was created first. To ensure consistent casing in your tag list, call list_tags first and reuse the exact name from there. Idempotent \u2014 re-attaching an already-attached tag is harmless."
   )
@@ -2241,7 +2308,7 @@ var addTagSchema = z14.object({
 async function addTag(input) {
   const { entity, entityId, tagName } = input;
   const wrapper = ENTITY_TO_WRAPPER[entity];
-  const result = await capsulePut(`/${entity}/${entityId}`, {
+  const result = await capsulePut(`/${ENTITY_PATH[entity]}/${entityId}`, {
     [wrapper]: { tags: [{ name: tagName }] }
   });
   invalidateByPrefix(TAG_LIST_PATH[entity], "add_tag");
@@ -2249,7 +2316,7 @@ async function addTag(input) {
 }
 var removeTagByIdSchema = z14.object({
   entity: TagEntity,
-  entityId: positiveId.describe("The party/opportunity/kase id."),
+  entityId: positiveId.describe("The party/opportunity/project id."),
   tagId: positiveId.describe(
     "The tag's id. Read via get_party / get_opportunity / get_project with embed='tags' \u2014 each tag entry in the response has an `id` field. list_tags returns the same ids for the same tags, so either source works; reading via embed first is the safer pattern because it confirms the tag is actually attached to this entity before you try to remove it (otherwise Capsule returns 422 'tag not found to delete'). Removing detaches the tag from this entity only; the tag definition itself persists in the tenant for other entities that share it."
   )
@@ -2258,7 +2325,7 @@ async function removeTagById(input) {
   const { entity, entityId, tagId } = input;
   const wrapper = ENTITY_TO_WRAPPER[entity];
   const result = await idempotentWithResult(
-    () => capsulePut(`/${entity}/${entityId}`, {
+    () => capsulePut(`/${ENTITY_PATH[entity]}/${entityId}`, {
       [wrapper]: { tags: [{ id: tagId, _delete: true }] }
     }),
     (result2) => ({
@@ -2293,7 +2360,7 @@ async function deleteTagDefinition(input) {
     throw new Error("delete_tag_definition requires confirm: true");
   }
   const result = await idempotent(
-    () => capsuleDelete(`/${entity}/tags/${tagId}`),
+    () => capsuleDelete(`/${ENTITY_PATH[entity]}/tags/${tagId}`),
     () => ({ deleted: true, alreadyDeleted: false, entity, tagId }),
     () => ({ deleted: true, alreadyDeleted: true, entity, tagId })
   );
@@ -2347,7 +2414,7 @@ var FilterInputSchema = z16.object({
   conditions: z16.array(FilterConditionSchema).min(1).describe(
     "Array of filter conditions. All conditions are ANDed together. To get newest records, use a date condition like {field: 'addedOn', operator: 'is within last', value: 7} and pick the highest-id row from the result (Capsule IDs are monotonic)."
   ),
-  embed: z16.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION),
+  embed: embedParam(RECORD_EMBEDS),
   ...paginationFields
 });
 async function runFilter(entityPath, input) {
@@ -2438,7 +2505,7 @@ var listEmployeesSchema = z18.object({
     "The organisation's party id. Returns the people whose `organisation` field links to this party."
   ),
   ...paginationFields,
-  embed: z18.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION)
+  embed: embedParam(RECORD_EMBEDS)
 });
 async function listEmployees(input) {
   return capsuleGetList(`/parties/${input.partyId}/people`, {
@@ -2481,19 +2548,22 @@ async function listDeletedProjects(input) {
 
 // src/tools/relationships.ts
 import { z as z19 } from "zod";
-var RelationshipEntity = z19.enum(["opportunities", "kases"]).describe("Which entity has the additional-party links. Use 'kases' for projects.");
+var RelationshipEntity = z19.enum(["opportunities", "projects"]).describe("Which entity has the additional-party links.");
 var listAdditionalPartiesSchema = z19.object({
   entity: RelationshipEntity,
   entityId: positiveId.describe("ID of the opportunity or project."),
-  embed: z19.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION),
+  embed: embedParam(RECORD_EMBEDS),
   ...paginationFields
 });
 async function listAdditionalParties(input) {
-  return capsuleGetList(`/${input.entity}/${input.entityId}/parties`, {
-    embed: input.embed,
-    page: input.page,
-    perPage: input.perPage
-  });
+  return capsuleGetList(
+    `/${ENTITY_PATH[input.entity]}/${input.entityId}/parties`,
+    {
+      embed: input.embed,
+      page: input.page,
+      perPage: input.perPage
+    }
+  );
 }
 var addAdditionalPartySchema = z19.object({
   entity: RelationshipEntity,
@@ -2504,7 +2574,9 @@ var addAdditionalPartySchema = z19.object({
 });
 async function addAdditionalParty(input) {
   try {
-    await capsulePostNoContent(`/${input.entity}/${input.entityId}/parties/${input.partyId}`);
+    await capsulePostNoContent(
+      `/${ENTITY_PATH[input.entity]}/${input.entityId}/parties/${input.partyId}`
+    );
     return {
       linked: true,
       alreadyLinked: false,
@@ -2541,7 +2613,7 @@ async function removeAdditionalParty(input) {
     throw new Error("remove_additional_party requires confirm: true");
   }
   return idempotent(
-    () => capsuleDelete(`/${input.entity}/${input.entityId}/parties/${input.partyId}`),
+    () => capsuleDelete(`/${ENTITY_PATH[input.entity]}/${input.entityId}/parties/${input.partyId}`),
     () => ({
       removed: true,
       alreadyRemoved: false,
@@ -2560,7 +2632,7 @@ async function removeAdditionalParty(input) {
 }
 var listAssociatedProjectsSchema = z19.object({
   opportunityId: positiveId,
-  embed: z19.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION),
+  embed: embedParam(RECORD_EMBEDS),
   ...paginationFields
 });
 async function listAssociatedProjects(input) {
@@ -2573,49 +2645,49 @@ async function listAssociatedProjects(input) {
 
 // src/tools/custom-fields.ts
 import { z as z20 } from "zod";
-var CustomFieldEntity = z20.enum(["parties", "opportunities", "kases"]).describe("Which entity type's custom field schema to inspect. Use 'kases' for projects.");
+var CustomFieldEntity = z20.enum(["parties", "opportunities", "projects"]).describe("Which entity type's custom field schema to inspect.");
 var listCustomFieldsSchema = z20.object({
   entity: CustomFieldEntity
 });
 async function listCustomFields(input) {
   const { data } = await capsuleGetCached(
-    `/${input.entity}/fields/definitions`
+    `/${ENTITY_PATH[input.entity]}/fields/definitions`
   );
   return data;
 }
 var getCustomFieldSchema = z20.object({
   entity: CustomFieldEntity,
-  fieldId: positiveId.describe("Custom field definition id.")
+  id: positiveId.describe("Custom field definition id.")
 });
 async function getCustomField(input) {
   const { data } = await capsuleGetCached(
-    `/${input.entity}/fields/definitions/${input.fieldId}`
+    `/${ENTITY_PATH[input.entity]}/fields/definitions/${input.id}`
   );
   return data;
 }
 
 // src/tools/tracks.ts
 import { z as z21 } from "zod";
-var TrackEntity = z21.enum(["parties", "opportunities", "kases"]).describe("Use 'kases' for projects.");
+var TrackEntity = z21.enum(["parties", "opportunities", "projects"]).describe("Which entity type.");
 var listEntityTracksSchema = z21.object({
   entity: TrackEntity,
   entityId: positiveId
 });
 async function listEntityTracks(input) {
   const { data } = await capsuleGet(
-    `/${input.entity}/${input.entityId}/tracks`
+    `/${ENTITY_PATH[input.entity]}/${input.entityId}/tracks`
   );
   return data;
 }
-var showTrackSchema = z21.object({
-  trackId: positiveId
+var getTrackSchema = z21.object({
+  id: positiveId
 });
-async function showTrack(input) {
-  const { data } = await capsuleGet(`/tracks/${input.trackId}`);
+async function getTrack(input) {
+  const { data } = await capsuleGet(`/tracks/${input.id}`);
   return data;
 }
 var applyTrackSchema = z21.object({
-  entity: z21.enum(["opportunities", "kases"]).describe("Which entity to apply the track to. Use 'kases' for projects."),
+  entity: z21.enum(["opportunities", "projects"]).describe("Which entity to apply the track to."),
   entityId: positiveId,
   trackDefinitionId: positiveId.describe(
     "The trackDefinition to apply (from list_track_definitions). Auto-creates task definitions on the target entity per the track's rules."
@@ -2634,7 +2706,7 @@ async function applyTrack(input) {
   return capsulePost("/tracks", { track });
 }
 var updateTrackSchema = z21.object({
-  trackId: positiveId,
+  id: positiveId,
   fields: z21.record(z21.string(), z21.unknown()).describe(
     "Object of fields to update on the track. Capsule's PUT semantics are partial \u2014 only the fields you provide are changed. Common: { complete: true } to mark a track completed. Capsule rejects unknown keys; consult Capsule's docs for the full updatable set."
   )
@@ -2643,12 +2715,12 @@ async function updateTrack(input) {
   if (Object.keys(input.fields).length === 0) {
     throw new Error("update_track: provide at least one field in `fields`");
   }
-  return capsulePut(`/tracks/${input.trackId}`, {
+  return capsulePut(`/tracks/${input.id}`, {
     track: input.fields
   });
 }
 var removeTrackSchema = z21.object({
-  trackId: positiveId,
+  id: positiveId,
   confirm: confirmFlag().describe(
     "Must be set to true. Removes the track instance from its entity. **Capsule also deletes the auto-tasks the track created when it was applied** \u2014 they go with the track and become unreachable (404 on GET /tasks/{id}, gone from list_tasks on the parent entity). If you need any of those tasks to outlive the track, copy their content into fresh tasks (or use the web UI) before calling remove_track."
   )
@@ -2658,9 +2730,9 @@ async function removeTrack(input) {
     throw new Error("remove_track requires confirm: true");
   }
   return idempotent(
-    () => capsuleDelete(`/tracks/${input.trackId}`),
-    () => ({ removed: true, alreadyRemoved: false, trackId: input.trackId }),
-    () => ({ removed: true, alreadyRemoved: true, trackId: input.trackId })
+    () => capsuleDelete(`/tracks/${input.id}`),
+    () => ({ removed: true, alreadyRemoved: false, id: input.id }),
+    () => ({ removed: true, alreadyRemoved: true, id: input.id })
   );
 }
 
@@ -2747,28 +2819,31 @@ async function uploadAttachment(input) {
 
 // src/tools/saved-filters.ts
 import { z as z23 } from "zod";
-var EntitySchema = z23.enum(["parties", "opportunities", "kases"]).describe(
-  "Which entity type the filter operates over. Use 'kases' for projects (Capsule's legacy name)."
-);
+var EntitySchema = z23.enum(["parties", "opportunities", "projects"]).describe("Which entity type the filter operates over.");
 var listSavedFiltersSchema = z23.object({
   entity: EntitySchema
 });
 async function listSavedFilters(input) {
-  const { data } = await capsuleGetCached(`/${input.entity}/filters`);
+  const { data } = await capsuleGetCached(
+    `/${ENTITY_PATH[input.entity]}/filters`
+  );
   return data;
 }
 var runSavedFilterSchema = z23.object({
   entity: EntitySchema,
   id: positiveId.describe("The saved filter id (from list_saved_filters)."),
-  embed: z23.string().optional().describe(EMBED_TAGS_FIELDS_DESCRIPTION),
+  embed: embedParam(RECORD_EMBEDS),
   ...paginationFields
 });
 async function runSavedFilter(input) {
-  return capsuleGetList(`/${input.entity}/filters/${input.id}/results`, {
-    page: input.page,
-    perPage: input.perPage,
-    embed: input.embed
-  });
+  return capsuleGetList(
+    `/${ENTITY_PATH[input.entity]}/filters/${input.id}/results`,
+    {
+      page: input.page,
+      perPage: input.perPage,
+      embed: input.embed
+    }
+  );
 }
 
 // src/server.ts
@@ -2779,7 +2854,7 @@ function createCapsuleMcpServer(opts) {
   const server2 = new McpServer(
     {
       name: "capsulemcp",
-      version: "1.8.1",
+      version: "2.0.1",
       description: "Read and (optionally) modify Capsule CRM data \u2014 parties, opportunities, projects, tasks, timeline entries, pipelines, tags.",
       websiteUrl: "https://github.com/soil-dev/capsulemcp",
       icons: ICONS
@@ -2839,7 +2914,7 @@ function createCapsuleMcpServer(opts) {
   registerTool(
     server2,
     "list_party_projects",
-    "List projects (cases) linked to a given party. Returns the same record shape as get_project, filtered to one party \u2014 use this to answer 'what cases is X involved in?' without enumerating all projects. Accepts optional embed (e.g. 'tags,fields'). For the opportunity-side analogue, use list_party_opportunities.",
+    "List projects linked to a given party. Returns the same record shape as get_project, filtered to one party \u2014 use this to answer 'what projects is X involved in?' without enumerating all projects. Accepts optional embed (e.g. 'tags,fields'). For the opportunity-side analogue, use list_party_opportunities.",
     listPartyProjectsSchema,
     listPartyProjects
   );
@@ -2853,7 +2928,7 @@ function createCapsuleMcpServer(opts) {
   registerTool(
     server2,
     "list_custom_fields",
-    "List custom field DEFINITIONS for an entity type (parties, opportunities, or projects/kases). Returns the schema \u2014 name, type, options for list-type fields, etc. \u2014 NOT the values on any specific record. To read values on a record, use get_party / get_opportunity / get_project with embed=fields.",
+    "List custom field DEFINITIONS for an entity type (parties, opportunities, or projects). Returns the schema \u2014 name, type, options for list-type fields, etc. \u2014 NOT the values on any specific record. To read values on a record, use get_party / get_opportunity / get_project with embed=fields.",
     listCustomFieldsSchema,
     listCustomFields
   );
@@ -2896,7 +2971,7 @@ function createCapsuleMcpServer(opts) {
     registerTool(
       server2,
       "delete_party",
-      "DESTRUCTIVE & IRREVERSIBLE: permanently delete a party (person or organisation). Cascades to all linked notes, tasks, opportunities, AND projects (kases). Deleting an organisation does NOT delete people linked to it via organisationId \u2014 their `organisation` field is silently cleared to null and they survive as standalone records. TRACK INSTANCES applied to cascaded opportunities/projects are NOT cleaned up either \u2014 they survive as orphan records reachable only by track id via show_track. Use remove_track on each track explicitly before deleting the parent party if orphan accumulation matters (rare in practice \u2014 orphans are unreachable from normal navigation). Requires confirm=true. Always read the party first with get_party and confirm with the user before calling. Idempotent on retry: response is `{deleted: true, alreadyDeleted: false, id}` on a fresh delete or `{deleted: true, alreadyDeleted: true, id}` if the party was already gone (Capsule's 404 is caught internally so reconciliation loops can re-issue safely).",
+      "DESTRUCTIVE & IRREVERSIBLE: permanently delete a party (person or organisation). Cascades to all linked notes, tasks, opportunities, AND projects. Deleting an organisation does NOT delete people linked to it via organisationId \u2014 their `organisation` field is silently cleared to null and they survive as standalone records. TRACK INSTANCES applied to cascaded opportunities/projects are NOT cleaned up either \u2014 they survive as orphan records reachable only by track id via get_track. Use remove_track on each track explicitly before deleting the parent party if orphan accumulation matters (rare in practice \u2014 orphans are unreachable from normal navigation). Requires confirm=true. Always read the party first with get_party and confirm with the user before calling. Idempotent on retry: response is `{deleted: true, alreadyDeleted: false, id}` on a fresh delete or `{deleted: true, alreadyDeleted: true, id}` if the party was already gone (Capsule's 404 is caught internally so reconciliation loops can re-issue safely).",
       deletePartySchema,
       deleteParty
     );
@@ -2995,14 +3070,14 @@ function createCapsuleMcpServer(opts) {
   registerTool(
     server2,
     "list_additional_parties",
-    "List secondary party links on an opportunity or project. The 'main' party is on the entity itself (opportunity.party); additional parties are e.g. partners, consultants, or referrers also involved in the deal. Set entity to 'opportunities' or 'kases' (Capsule's term for projects).",
+    "List secondary party links on an opportunity or project. The 'main' party is on the entity itself (opportunity.party); additional parties are e.g. partners, consultants, or referrers also involved in the deal. Set entity to 'opportunities' or 'projects'.",
     listAdditionalPartiesSchema,
     listAdditionalParties
   );
   registerTool(
     server2,
     "list_associated_projects",
-    "List projects (cases) associated with a given opportunity. Returns the same record shape as list_projects, filtered to one opportunity. The inverse direction (project \u2192 opportunity) is on each project's `opportunity` field directly, so this tool is only needed for opportunity \u2192 projects discovery \u2014 use list_party_projects for party \u2192 projects.",
+    "List projects associated with a given opportunity. Returns the same record shape as list_projects, filtered to one opportunity. The inverse direction (project \u2192 opportunity) is on each project's `opportunity` field directly, so this tool is only needed for opportunity \u2192 projects discovery \u2014 use list_party_projects for party \u2192 projects.",
     listAssociatedProjectsSchema,
     listAssociatedProjects
   );
@@ -3036,38 +3111,45 @@ function createCapsuleMcpServer(opts) {
       deleteOpportunity
     );
   }
+  registerTool(
+    server2,
+    "search_projects",
+    "Free-text search projects in Capsule CRM (matches name and description). Returns results in Capsule's default order (no sort parameter is supported here). Omit `q` to list all projects. For structured queries \u2014 'most recent project', 'projects opened this month', 'projects tagged X' \u2014 use filter_projects instead.",
+    searchProjectsSchema,
+    searchProjects
+  );
   registerTool(
     server2,
     "list_projects",
-    "List projects (cases) in Capsule CRM, optionally filtered by status. Returns results in Capsule's default order (no sort parameter is supported here). For structured queries \u2014 'most recent project', 'projects opened this month', 'projects tagged X' \u2014 use filter_projects instead.",
+    "List projects in Capsule CRM, optionally filtered by status. Returns results in Capsule's default order (no sort parameter is supported here). For free-text matching use search_projects; for structured queries \u2014 'most recent project', 'projects opened this month', 'projects tagged X' \u2014 use filter_projects instead.",
     listProjectsSchema,
     listProjects
   );
   registerTool(
     server2,
     "filter_projects",
-    "Filter projects (cases) by structured conditions (date ranges, status, tags, owner). Use this \u2014 not list_projects \u2014 for questions like 'most recent project', 'projects opened this month'. Capsule's API does not support ad-hoc sort, but for 'most recent X' you can filter by a date field and pick the highest-id row \u2014 Capsule IDs are monotonic, so newest id = newest record.",
+    "Filter projects by structured conditions (date ranges, status, tags, owner). Use this \u2014 not list_projects \u2014 for questions like 'most recent project', 'projects opened this month'. Capsule's API does not support ad-hoc sort, but for 'most recent X' you can filter by a date field and pick the highest-id row \u2014 Capsule IDs are monotonic, so newest id = newest record.",
     filterProjectsSchema,
     filterProjects
   );
   registerTool(
     server2,
     "get_project",
-    "Fetch a single project (Capsule's term: 'case') by its numeric id. Returns the full record including name, description, status (OPEN/CLOSED), owner, stage, board, opportunityId (if linked), and timestamps. Use embed='tags,fields' to include attached tags and custom field values in one round-trip. For batch fetches of up to 50 projects at once, use get_projects instead. For the project's timeline (notes, captured emails, completed-task records) use list_project_entries.",
+    "Fetch a single project by its numeric id. Returns the full record including name, description, status (OPEN/CLOSED), owner, stage, board, opportunityId (if linked), and timestamps. Use embed='tags,fields' to include attached tags and custom field values in one round-trip. For batch fetches of up to 50 projects at once, use get_projects instead. For the project's timeline (notes, captured emails, completed-task records) use list_project_entries.",
     getProjectSchema,
     getProject
   );
   registerTool(
     server2,
     "get_projects",
-    "Batch-fetch up to 50 projects (cases) by ID. For 1\u201310 ids this is a single Capsule round trip; for 11\u201350 ids the connector transparently splits into 10-id chunks and fans out parallel Capsule requests, so the caller sees a single tool call with all results merged.",
+    "Batch-fetch up to 50 projects by ID. For 1\u201310 ids this is a single Capsule round trip; for 11\u201350 ids the connector transparently splits into 10-id chunks and fans out parallel Capsule requests, so the caller sees a single tool call with all results merged.",
     getProjectsSchema,
     getProjects
   );
   registerTool(
     server2,
     "list_deleted_projects",
-    "Audit feature: list projects deleted on or after a given timestamp. The `since` parameter is REQUIRED. Response also includes a `restrictedKases` key for records the integration user can't read fully.",
+    "Audit feature: list projects deleted on or after a given timestamp. The `since` parameter is REQUIRED. Response also includes a `restrictedProjects` key for records the integration user can't read fully.",
     listDeletedProjectsSchema,
     listDeletedProjects
   );
@@ -3075,7 +3157,7 @@ function createCapsuleMcpServer(opts) {
     registerTool(
       server2,
       "create_project",
-      "Create a new project (case) in Capsule CRM linked to a party. Requires partyId and name; description, status, owner, and starting board/stage are optional. To pin a project to a specific board+stage on creation, pass stageId (which uniquely identifies a stage within a board). Discover valid ids via list_boards + list_stages. Returns the created project including its assigned id.",
+      "Create a new project in Capsule CRM linked to a party. Requires partyId and name; description, status, owner, and starting board/stage are optional. To pin a project to a specific board+stage on creation, pass stageId (which uniquely identifies a stage within a board). Discover valid ids via list_boards + list_stages. Returns the created project including its assigned id.",
       createProjectSchema,
       createProject
     );
@@ -3096,7 +3178,7 @@ function createCapsuleMcpServer(opts) {
     registerTool(
       server2,
       "delete_project",
-      "DESTRUCTIVE & IRREVERSIBLE: permanently delete a project (case). Prefer update_project with status='CLOSED' to close a project while preserving history. Requires confirm=true. Always read the project first with get_project and confirm with the user before calling. Idempotent on retry: response is `{deleted: true, alreadyDeleted: false, id}` on a fresh delete or `{deleted: true, alreadyDeleted: true, id}` if the project was already gone.",
+      "DESTRUCTIVE & IRREVERSIBLE: permanently delete a project. Prefer update_project with status='CLOSED' to close a project while preserving history. Requires confirm=true. Always read the project first with get_project and confirm with the user before calling. Idempotent on retry: response is `{deleted: true, alreadyDeleted: false, id}` on a fresh delete or `{deleted: true, alreadyDeleted: true, id}` if the project was already gone.",
       deleteProjectSchema,
       deleteProject
     );
@@ -3211,7 +3293,7 @@ function createCapsuleMcpServer(opts) {
   registerTool(
     server2,
     "list_project_entries",
-    "List timeline entries (notes, captured emails, completed-task records) for a project (case). Returns entries newest-first. Each entry has a type ('note', 'email', 'task'), free-text content, and timestamps. Use this to answer 'what's the latest on case X?' For party or opportunity timelines, use list_party_entries or list_opportunity_entries respectively.",
+    "List timeline entries (notes, captured emails, completed-task records) for a project. Returns entries newest-first. Each entry has a type ('note', 'email', 'task'), free-text content, and timestamps. Use this to answer 'what's the latest on project X?' For party or opportunity timelines, use list_party_entries or list_opportunity_entries respectively.",
     listProjectEntriesSchema,
     listProjectEntries
   );
@@ -3362,14 +3444,14 @@ function createCapsuleMcpServer(opts) {
   registerTool(
     server2,
     "list_boards",
-    "List all project (case) boards defined in Capsule. A board is a grouping of stages that projects flow through \u2014 the project equivalent of an opportunity pipeline. Returns each board's id, name, and stages. Use this to discover boardId when creating a project, then pick a starting stage via list_stages. Like pipelines, boards are stable per account.",
+    "List all project boards defined in Capsule. A board is a grouping of stages that projects flow through \u2014 the project equivalent of an opportunity pipeline. Returns each board's id, name, and stages. Use this to discover boardId when creating a project, then pick a starting stage via list_stages. Like pipelines, boards are stable per account.",
     listBoardsSchema,
     listBoards
   );
   registerTool(
     server2,
     "list_stages",
-    "List project (case) stages. Without arguments returns every stage across every board (each entry carries a `.board` reference so you can tell them apart). Pass `boardId` to scope the result to one specific board's stages. Use this to discover the numeric `stage.id` that `create_project` / `update_project` consume \u2014 stage names alone won't do, Capsule resolves by id. For opportunity (deal) stages, use `list_pipelines` instead \u2014 opportunities don't have stages in the project sense.",
+    "List project stages. Without arguments returns every stage across every board (each entry carries a `.board` reference so you can tell them apart). Pass `boardId` to scope the result to one specific board's stages. Use this to discover the numeric `stage.id` that `create_project` / `update_project` consume \u2014 stage names alone won't do, Capsule resolves by id. For opportunity (deal) stages, use `list_pipelines` instead \u2014 opportunities don't have stages in the project sense.",
     listStagesSchema,
     listStages
   );
@@ -3382,14 +3464,14 @@ function createCapsuleMcpServer(opts) {
   );
   registerTool(
     server2,
-    "list_lostreasons",
+    "list_lost_reasons",
     "List all configured opportunity-loss reasons (e.g. 'Poor Qualification', 'Lost to competitor', 'Price too high'). Returns each reason's id and name; the set is account-configured rather than a fixed enum, so call this to discover valid ids before referencing a lostReason in update_opportunity when closing a deal as lost. Useful for analysing closed-lost opportunities by reason.",
     listLostReasonsSchema,
     listLostReasons
   );
   registerTool(
     server2,
-    "list_activitytypes",
+    "list_activity_types",
     "List all configured activity types (e.g. Call, Meeting, Email). These are the categories used when logging timeline entries via add_note. Returns each type's id and name. The set is account-configured rather than a fixed enum, so call this to discover valid values before referencing an activityType in entry creation.",
     listActivityTypesSchema,
     listActivityTypes
@@ -3417,10 +3499,10 @@ function createCapsuleMcpServer(opts) {
   );
   registerTool(
     server2,
-    "show_track",
+    "get_track",
     "Fetch a single track instance by id. Returns the minimal Capsule projection: id, description, trackDateOn, direction, and the array of tasks attached to the track. Capsule's GET /tracks/{id} does NOT include a trackDefinition link, an entity reference, or a completion field \u2014 to find the entity a track is applied to, use list_entity_tracks (which lists track instances by their parent entity); to check completion, the track-tasks' own statuses are the proxy.",
-    showTrackSchema,
-    showTrack
+    getTrackSchema,
+    getTrack
   );
   registerTool(
     server2,
@@ -3453,7 +3535,7 @@ function createCapsuleMcpServer(opts) {
   registerTool(
     server2,
     "list_tags",
-    "List all tags available for a given entity type (parties, opportunities, or kases). Returns each tag's id, name, and any data-tag field schema. Tags are entity-specific \u2014 a party tag is not interchangeable with an opportunity tag. Use this to discover valid tag ids before calling add_tag, or to display the tag catalogue to the user when they ask 'what tags do we use?'",
+    "List all tags available for a given entity type (parties, opportunities, or projects). Returns each tag's id, name, and any data-tag field schema. Tags are entity-specific \u2014 a party tag is not interchangeable with an opportunity tag. Use this to discover valid tag ids before calling add_tag, or to display the tag catalogue to the user when they ask 'what tags do we use?'",
     listTagsSchema,
     listTags
   );
@@ -3461,21 +3543,21 @@ function createCapsuleMcpServer(opts) {
     registerTool(
       server2,
       "add_tag",
-      "Attach a tag to a party, opportunity, or project (kase) by NAME. Capsule resolves to an existing tag in the tenant or creates a fresh one with this name. Matching is case-insensitive \u2014 'VIP' and 'vip' attach the same tag, preserving the canonical casing from whichever variant was created first. To avoid creating a genuinely-distinct near-duplicate (e.g. 'VIP' vs 'V.I.P.'), call list_tags first and reuse the exact name. Idempotent \u2014 re-attaching an already-attached tag is harmless. To DETACH a tag, use remove_tag_by_id with the tag's id (read via get_party/get_opportunity/get_project with embed='tags').",
+      "Attach a tag to a party, opportunity, or project by NAME. Capsule resolves to an existing tag in the tenant or creates a fresh one with this name. Matching is case-insensitive \u2014 'VIP' and 'vip' attach the same tag, preserving the canonical casing from whichever variant was created first. To avoid creating a genuinely-distinct near-duplicate (e.g. 'VIP' vs 'V.I.P.'), call list_tags first and reuse the exact name. Idempotent \u2014 re-attaching an already-attached tag is harmless. To DETACH a tag, use remove_tag_by_id with the tag's id (read via get_party/get_opportunity/get_project with embed='tags').",
       addTagSchema,
       addTag
     );
     registerTool(
       server2,
       "remove_tag_by_id",
-      "Detach a tag from a party, opportunity, or project (kase). Atomic \u2014 one PUT to Capsule. Reversible \u2014 no `confirm: true` gate (re-attach with add_tag using the same tag name). The `tagId` parameter is the tag's id, readable via get_party/get_opportunity/get_project with embed='tags' (list_tags returns the same ids and also works, but reading via embed first confirms the tag is actually attached to this entity). The tag definition itself remains in the tenant for other entities that still share it. Idempotent on retry: response is `{removed: true, alreadyRemoved: false, entity, entityId, tagId, ...<updated entity>}` on a fresh detach or `{removed: true, alreadyRemoved: true, entity, entityId, tagId}` if the tag was already detached (Capsule's 422 'tag not found to delete' is caught and converted).",
+      "Detach a tag from a party, opportunity, or project. Atomic \u2014 one PUT to Capsule. Reversible \u2014 no `confirm: true` gate (re-attach with add_tag using the same tag name). The `tagId` parameter is the tag's id, readable via get_party/get_opportunity/get_project with embed='tags' (list_tags returns the same ids and also works, but reading via embed first confirms the tag is actually attached to this entity). The tag definition itself remains in the tenant for other entities that still share it. Idempotent on retry: response is `{removed: true, alreadyRemoved: false, entity, entityId, tagId, ...<updated entity>}` on a fresh detach or `{removed: true, alreadyRemoved: true, entity, entityId, tagId}` if the tag was already detached (Capsule's 422 'tag not found to delete' is caught and converted).",
       removeTagByIdSchema,
       removeTagById
     );
     registerTool(
       server2,
       "delete_tag_definition",
-      "DESTRUCTIVE & TENANT-WIDE: permanently delete a tag DEFINITION from an entity type's tag namespace (parties / opportunities / kases). Unlike remove_tag_by_id \u2014 which detaches a tag from ONE record and leaves the definition intact for others \u2014 this removes the definition itself, so the tag disappears from EVERY record that shared it. Use it to clean up stray / mistyped / test tag definitions polluting the tenant-global list. Requires confirm=true. Always read the affected tag first via list_tags and confirm with the user; if you only want to untag one record, use remove_tag_by_id instead. Irreversible (re-creating by name via add_tag mints a brand-new id). Idempotent on retry: `{deleted: true, alreadyDeleted: false, entity, tagId}` on a fresh delete, or `{deleted: true, alreadyDeleted: true, entity, tagId}` if the definition was already gone (Capsule's 404 is caught). Endpoint verified empirically (DELETE /<entity>/tags/{id} \u2192 204).",
+      "DESTRUCTIVE & TENANT-WIDE: permanently delete a tag DEFINITION from an entity type's tag namespace (parties / opportunities / projects). Unlike remove_tag_by_id \u2014 which detaches a tag from ONE record and leaves the definition intact for others \u2014 this removes the definition itself, so the tag disappears from EVERY record that shared it. Use it to clean up stray / mistyped / test tag definitions polluting the tenant-global list. Requires confirm=true. Always read the affected tag first via list_tags and confirm with the user; if you only want to untag one record, use remove_tag_by_id instead. Irreversible (re-creating by name via add_tag mints a brand-new id). Idempotent on retry: `{deleted: true, alreadyDeleted: false, entity, tagId}` on a fresh delete, or `{deleted: true, alreadyDeleted: true, entity, tagId}` if the definition was already gone (Capsule's 404 is caught). Endpoint verified empirically (DELETE /<entity>/tags/{id} \u2192 204).",
       deleteTagDefinitionSchema,
       deleteTagDefinition
     );