@sodiumhq/mcp-pm 0.1.0-beta.6257 → 0.1.0-beta.6351

package/dist/http.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { t as buildServer } from "./src-CMzdZk6e.mjs";
+import { t as buildServer } from "./src-CRE2Nlq7.mjs";
 import { createRequire } from "node:module";
 import { SUPPORTED_PROTOCOL_VERSIONS, createMcpHandler } from "@modelcontextprotocol/server";
 import { createHash, randomUUID } from "node:crypto";

package/dist/index.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { t as buildServer } from "./src-CMzdZk6e.mjs";
+import { t as buildServer } from "./src-CRE2Nlq7.mjs";
 import { createRequire } from "node:module";
 import { serveStdio } from "@modelcontextprotocol/server/stdio";
 import { parseArgs } from "node:util";

package/dist/{src-CMzdZk6e.mjs → src-CRE2Nlq7.mjs}

@@ -2070,11 +2070,26 @@ const getTaskItem = (options) => (options.client ?? client).get({
 	...options
 });
 /**
-* Update TaskItem
+* Patch TaskItem
 *
-* Updates a TaskItem for the specified tenant.
+* Updates part of one task, following JSON Merge Patch. Send only the fields to change: a field left
+* out is not touched, so a quick action (moving the task on the calendar, a status button, a checklist
+* tick) never overwrites details it did not send, such as the description. A field sent as null is
+* cleared: description, statutory due date, time estimate, checklist, assignee, team, category, service
+* and primary client. The name, status, dates and times are required on a task, so sending one of those
+* as null is a 400.
+*
+* **Clients**: the same rules as a full update. The primary client always stays on the task, and a task
+* with clients but no primary gets its first client as primary. To remove every client, send the client
+* list and the primary client as null. Changing the primary client clears the task's service and
+* pipeline links (they belong to a client) unless a service code is sent.
+*
+* The change is saved through the same update as a full update, so dated workflow steps follow the
+* task when its dates move (unless MoveWorkflowStepDates is false), and colleagues see the change live.
+*
+* Only a saved task can be patched. A projected (upcoming) task must be materialised first.
 */
-const updateTaskItem = (options) => (options.client ?? client).put({
+const patchTaskItem = (options) => (options.client ?? client).patch({
 	security: [{
 		name: "x-api-key",
 		type: "apiKey"
@@ -3756,9 +3771,9 @@ var SodiumApiClient = class {
 		if (error !== void 0 || !data) throw this.toError(response, error, correlationId, "create task");
 		return data;
 	}
-	async updateTask(code, body) {
+	async patchTask(code, body) {
 		const correlationId = randomUUID();
-		const { data, error, response } = await updateTaskItem({
+		const { data, error, response } = await patchTaskItem({
 			path: {
 				tenant: this.tenant,
 				code
@@ -7299,26 +7314,23 @@ const UpdateTaskInputSchema = {
 };
 async function handleUpdateTask(api, args) {
 	try {
-		const current = await api.getTask(args.taskCode);
 		const has = (key) => args[key] !== void 0;
-		const body = {
-			name: has("name") ? args.name : current.name ?? "",
-			description: has("description") ? args.description : current.description ?? null,
-			status: has("status") ? args.status : current.status ?? "NotStarted",
-			startDate: has("startDate") ? args.startDate : current.startDate ?? "",
-			dueDate: has("dueDate") ? args.dueDate : current.dueDate ?? "",
-			statutoryDueDate: has("statutoryDueDate") ? args.statutoryDueDate : current.statutoryDueDate ?? null,
-			timeEstimateMinutes: has("timeEstimateMinutes") ? args.timeEstimateMinutes : current.timeEstimateMinutes ?? null,
-			clientCodes: (current.clients ?? []).map((c) => c.code).filter((c) => Boolean(c)),
-			primaryClientCode: current.primaryClient?.code ?? null,
-			assignedUserCode: has("assignedUserCode") ? args.assignedUserCode : current.assignedUser?.code ?? null,
-			assignedTeamCode: has("assignedTeamCode") ? args.assignedTeamCode : current.assignedTeam?.code ?? null,
-			clientBillableServiceCode: current.clientBillableService?.code ?? null,
-			categoryCode: has("categoryCode") ? args.categoryCode : current.category?.code ?? null,
-			checklist: current.checklist ?? null,
-			recurringTaskCode: current.recurringTask?.code ?? null
-		};
-		const updated = await api.updateTask(args.taskCode, body);
+		const body = {};
+		if (has("status")) body.status = args.status;
+		if (has("name")) body.name = args.name;
+		if (has("description")) body.description = args.description;
+		if (has("startDate")) body.startDate = args.startDate;
+		if (has("dueDate")) body.dueDate = args.dueDate;
+		if (has("statutoryDueDate")) body.statutoryDueDate = args.statutoryDueDate;
+		if (has("timeEstimateMinutes")) body.timeEstimateMinutes = args.timeEstimateMinutes;
+		if (has("assignedUserCode")) body.assignedUserCode = args.assignedUserCode;
+		if (has("assignedTeamCode")) body.assignedTeamCode = args.assignedTeamCode;
+		if (has("categoryCode")) body.categoryCode = args.categoryCode;
+		if (Object.keys(body).length === 0) return { content: [{
+			type: "text",
+			text: `Task ${args.taskCode} not changed: no fields were passed to update.`
+		}] };
+		const updated = await api.patchTask(args.taskCode, body);
 		const changes = [];
 		if (has("status")) changes.push(`status → ${updated.status}`);
 		if (has("name")) changes.push(`name → ${updated.name}`);
@@ -7332,7 +7344,7 @@ async function handleUpdateTask(api, args) {
 		if (has("timeEstimateMinutes")) changes.push(`estimate → ${updated.timeEstimateMinutes ?? "cleared"}m`);
 		return { content: [{
 			type: "text",
-			text: [`Task updated: ${updated.name} (${updated.code})`, changes.length ? `Changed: ${changes.join(", ")}` : "No field changes were requested."].join("\n")
+			text: [`Task updated: ${updated.name} (${updated.code})`, `Changed: ${changes.join(", ")}`].join("\n")
 		}] };
 	} catch (error) {
 		return {
@@ -9364,15 +9376,25 @@ function captureClientInfo(server, api) {
 		version: info.version
 	});
 }
+function withAnnotationTitle(config) {
+	if (!config.title) return config;
+	return {
+		...config,
+		annotations: {
+			title: config.title,
+			...config.annotations
+		}
+	};
+}
 function registerTenantTool(server, api, name, config, cb) {
 	const inputSchema = {
 		...config.inputSchema ?? {},
 		practice: practiceField
 	};
-	server.registerTool(name, {
+	server.registerTool(name, withAnnotationTitle({
 		...config,
 		inputSchema
-	}, async (args, extra) => {
+	}), async (args, extra) => {
 		const started = Date.now();
 		captureClientInfo(server, api);
 		const { practice, ...rest } = args;
@@ -9452,7 +9474,7 @@ async function buildServer(config) {
 			openWorldHint: true
 		}
 	}, () => handleGetPracticeDetails(api));
-	server.registerTool("whoami", {
+	server.registerTool("whoami", withAnnotationTitle({
 		title: "Show current user and tenant info",
 		description: "Returns the identity of the authenticated user (name, email, code), the tenant/practice the call runs against (name, code, status), and the practice name. Use this when the user asks 'who am I?', 'which tenant am I connected to?', 'what account is this?', or when debugging authentication/permission issues. The optional 'practice' argument picks the practice section shown; without it the user's lone practice is used, and the identity section still answers when no practice can be resolved.",
 		inputSchema: { practice: practiceField },
@@ -9461,12 +9483,12 @@ async function buildServer(config) {
 			idempotentHint: true,
 			openWorldHint: true
 		}
-	}, async (args) => {
+	}), async (args) => {
 		captureClientInfo(server, api);
 		await resolveTenantForCall(api, args.practice);
 		return handleWhoami(api);
 	});
-	server.registerTool("list_practices", {
+	server.registerTool("list_practices", withAnnotationTitle({
 		title: "List the practices you can work in",
 		description: "List the practices (tenants) the signed-in user belongs to. Use this when the user belongs to more than one practice and you need the codes to pass in other tools' 'practice' argument, or when the user asks 'which practices can I access?'. Practices flagged 'unavailable' cannot be worked in.",
 		inputSchema: {},
@@ -9475,7 +9497,7 @@ async function buildServer(config) {
 			idempotentHint: true,
 			openWorldHint: true
 		}
-	}, () => {
+	}), () => {
 		captureClientInfo(server, api);
 		return handleListPractices(api);
 	});
@@ -9682,7 +9704,7 @@ async function buildServer(config) {
 		inputSchema: ListWorkflowOccurrencesInputSchema,
 		annotations: reportAnnotations
 	}, (args) => handleListWorkflowOccurrences(api, args));
-	server.registerTool("get_usage_examples", {
+	server.registerTool("get_usage_examples", withAnnotationTitle({
 		title: "Show example prompts for this integration",
 		description: "Returns a curated cookbook of example prompts this Sodium integration answers well, grouped by topic (daily-workflow, clients, tasks-and-deadlines, client-requests, time-tracking, reports, companies-house, proposals-and-engagements, making-changes). Use when the user asks 'what can you do?', 'what can I ask about my Sodium data?', 'give me some examples', or seems unsure how to get value from the integration. Also useful onboarding a new user: show the overview, then drill into the topic nearest their role. Static content — makes no API call.",
 		inputSchema: GetUsageExamplesInputSchema,
@@ -9691,7 +9713,7 @@ async function buildServer(config) {
 			idempotentHint: true,
 			openWorldHint: false
 		}
-	}, (args) => handleGetUsageExamples(args));
+	}), (args) => handleGetUsageExamples(args));
 	const lookupAnnotations = {
 		readOnlyHint: true,
 		idempotentHint: true,
@@ -10064,7 +10086,7 @@ async function buildServer(config) {
 	}, (args) => handleCreateTask(api, args));
 	registerWriteTool(server, api, config.context, "update_task", {
 		title: "Update a task (status, dates, assignment, details)",
-		description: "Update fields on an existing task by code: status (mark Completed / InProgress / Blocked / Skipped), name, description, start/due/statutory dates, time estimate, assigned user or team, and category. Only the fields you pass change — the handler fetches the current task and preserves everything else (clients, checklist, service and recurring-task links), so it's safe to pass just { taskCode, status: 'Completed' } for 'mark it done'. Pass null to clear a clearable field (description, statutory date, estimate, assignee, team, category). Use for 'mark TSK-123 complete', 'push the deadline to Friday', 'reassign it to Jane' (resolve her code from the roster), 'unassign this task' (assignedUserCode=null). Completing a task does NOT complete its workflow steps — if get_task_context showed open steps, tell the user they remain open. Cannot delete tasks — deletion isn't available through the MCP.",
+		description: "Update fields on an existing task by code: status (mark Completed / InProgress / Blocked / Skipped), name, description, start/due/statutory dates, time estimate, assigned user or team, and category. Only the fields you pass change — everything else on the task (clients, checklist, start and due times, service and recurring-task links) is left exactly as it is, so it's safe to pass just { taskCode, status: 'Completed' } for 'mark it done'. Pass null to clear a clearable field (description, statutory date, estimate, assignee, team, category). Use for 'mark TSK-123 complete', 'push the deadline to Friday', 'reassign it to Jane' (resolve her code from the roster), 'unassign this task' (assignedUserCode=null). Completing a task does NOT complete its workflow steps — if get_task_context showed open steps, tell the user they remain open. Cannot delete tasks — deletion isn't available through the MCP.",
 		inputSchema: UpdateTaskInputSchema,
 		annotations: {
 			readOnlyHint: false,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sodiumhq/mcp-pm",
-  "version": "0.1.0-beta.6257",
+  "version": "0.1.0-beta.6351",
   "description": "Sodium Practice Management MCP server — lets AI assistants interact with your Sodium tenant",
   "type": "module",
   "bin": {