keepsake-mcp 1.8.0 → 1.9.1

package/README.md

@@ -2,7 +2,7 @@
 
 MCP server for [Keepsake](https://keepsake.place) — the personal CRM that helps you nurture your relationships.
 
-Connect your AI assistant (Claude, Cursor, or any MCP-compatible client) to your Keepsake data: contacts, interactions, tasks, notes, daily journal, companies, and tags.
+Connect your AI assistant (Claude, Cursor, or any MCP-compatible client) to your Keepsake data: contacts, interactions, tasks, notes, daily intentions, companies, and tags.
 
 ## Why
 
@@ -114,7 +114,7 @@ rather than in the chat, which disappears.
 |--------|-----------|-------------|
 | `review_note` | `note_id` | Act as the editor of a note: read it, judge form and substance, leave anchored remarks in the margin, never rewrite the text |
 
-## Available tools (67)
+## Available tools (71)
 
 ### Contacts
 | Tool | Description |
@@ -181,12 +181,20 @@ Material kept *alongside* a note without entering its text — an idea, a refere
 | `update_note_comment` | Edit the content of a marginalia |
 | `delete_note_comment` | Permanently delete a marginalia |
 
-### Daily Journal
+### Days (intention or question of the day)
 | Tool | Description |
 |------|-------------|
-| `list_days` | List journal entries by date range |
-| `get_day` | Get a specific day's journal |
-| `update_day` | Create or update a day's journal (upsert) |
+| `list_days` | List days with their intention or question of the day, by date range |
+| `get_day` | Get a day and its intention or question (field `note`) |
+| `update_day` | Set a day's intention or question — one short line, not a journal (upsert) |
+
+### Day blocks (Day-view timeline)
+| Tool | Description |
+|------|-------------|
+| `list_day_blocks` | List a day's time blocks, in timeline order |
+| `create_day_block` | Create a block, auto-placed first-fit (or pinned via anchor_time) |
+| `update_day_block` | Update a block (title, duration, anchor, note, done) |
+| `delete_day_block` | Delete a block and prune its timeline ref |
 
 ### Tags
 | Tool | Description |

package/build/tools.js

@@ -7,8 +7,14 @@ export function toContent(result) {
             : result.error.message || JSON.stringify(result.error);
         return { content: [{ type: "text", text: `Error: ${msg}` }] };
     }
+    // List endpoints ship pagination alongside the rows (meta.total / limit /
+    // offset). Dropping it forced agents to binary-search offsets just to count
+    // an inbox — keep data and meta together whenever meta is present.
+    const payload = result.meta !== undefined
+        ? { data: result.data ?? [], meta: result.meta }
+        : (result.data ?? result);
     return {
-        content: [{ type: "text", text: JSON.stringify(result.data ?? result, null, 2) }],
+        content: [{ type: "text", text: JSON.stringify(payload, null, 2) }],
     };
 }
 /** Build query string from optional params, skipping undefined values. */
@@ -358,6 +364,18 @@ export function registerAllTools(server, fetchApi) {
                 .positive()
                 .optional()
                 .describe("Recurrence interval (e.g., every N days)"),
+            start_time: z
+                .string()
+                .regex(/^([01]\d|2[0-3]):[0-5]\d$/)
+                .optional()
+                .describe("Wall-clock start time HH:MM (24h). A task of the day WITH a time appears anchored on the Day-view timeline; without one it stays in the day's task list."),
+            duration_minutes: z
+                .number()
+                .int()
+                .min(1)
+                .max(1440)
+                .optional()
+                .describe("Estimated duration in minutes (Day-view timeline shows 15 by default when a start time is set)"),
             contact_ids: z
                 .array(z.string().uuid())
                 .optional()
@@ -383,6 +401,20 @@ export function registerAllTools(server, fetchApi) {
                 .optional()
                 .describe("Date type: specific (has a due date), asap (do as soon as possible), one_day (someday/no rush)"),
             priority: z.enum(["low", "medium", "high"]).optional().describe("Priority level"),
+            start_time: z
+                .string()
+                .regex(/^([01]\d|2[0-3]):[0-5]\d$/)
+                .nullable()
+                .optional()
+                .describe("Wall-clock start time HH:MM (24h) — anchors the task on the Day-view timeline. Pass null to clear it (unschedule)."),
+            duration_minutes: z
+                .number()
+                .int()
+                .min(1)
+                .max(1440)
+                .nullable()
+                .optional()
+                .describe("Estimated duration in minutes. Pass null to clear."),
             contact_ids: z
                 .array(z.string().uuid())
                 .optional()
@@ -535,7 +567,7 @@ export function registerAllTools(server, fetchApi) {
     // DAYS (Daily Summaries)
     // ===========================================================================
     server.registerTool("list_days", {
-        description: "List daily journal summaries. Filter by date range.",
+        description: "List days with their intention or question of the day (field `note`). Filter by date range.",
         inputSchema: {
             from: z.string().optional().describe("Start date (YYYY-MM-DD)"),
             to: z.string().optional().describe("End date (YYYY-MM-DD)"),
@@ -547,7 +579,7 @@ export function registerAllTools(server, fetchApi) {
         return toContent(await fetchApi(`/days${qs({ from, to, limit, offset })}`));
     });
     server.registerTool("get_day", {
-        description: "Get a specific day's journal summary by date.",
+        description: "Get a specific day by date, including its intention or question of the day (field `note`).",
         inputSchema: {
             date: z.string().describe("Date (YYYY-MM-DD)"),
         },
@@ -556,16 +588,89 @@ export function registerAllTools(server, fetchApi) {
         return toContent(await fetchApi(`/days/${date}`));
     });
     server.registerTool("update_day", {
-        description: "Create or update a daily journal summary. If a day entry already exists for this date, it will be updated (upsert).",
+        description: "Create or update a day's intention or question of the day (upsert on the date). The `note` field is the intention or question of the day — one short line at the top of the Today view (a mantra, an intention, a single priority, or a question to keep in mind). Not a journal: never write a summary of the day here.",
         inputSchema: {
             date: z.string().describe("Date (YYYY-MM-DD)"),
-            note: z.string().describe("Journal content for the day"),
+            note: z.string().describe("The intention or question of the day: one short line (mantra, intention, single priority, or a question to keep in mind). Not a journal summary."),
         },
         annotations: { title: "Update day", destructiveHint: false, idempotentHint: true, openWorldHint: false },
     }, async (params) => {
         return toContent(await fetchApi("/days", "POST", params));
     });
     // ===========================================================================
+    // DAY BLOCKS (Day-view timeline)
+    // ===========================================================================
+    server.registerTool("list_day_blocks", {
+        description: "List the time blocks of a day's timeline (Day view), in timeline order. A block is either an activity (type 'block') or a task bucket (type 'tasks' — groups the day's untimed tasks). The meta carries the day's raw timeline_order: \"b:<uuid>\" refs are blocks, bare uuids are tasks inside a bucket's run.",
+        inputSchema: {
+            date: z.string().describe("Date (YYYY-MM-DD)"),
+        },
+        annotations: { title: "List day blocks", readOnlyHint: true, openWorldHint: false },
+    }, async ({ date }) => {
+        return toContent(await fetchApi(`/day-blocks${qs({ date })}`));
+    });
+    server.registerTool("create_day_block", {
+        description: "Create a time block on a day's timeline. The block is auto-placed in the earliest free gap large enough for it (same first-fit engine as the app); pass anchor_time to pin it at a fixed hour instead. Its \"b:<id>\" ref is inserted into the day's timeline_order for you — never write timeline_order by hand.",
+        inputSchema: {
+            date: z.string().describe("Date (YYYY-MM-DD)"),
+            title: z.string().optional().describe("Block label (e.g. \"Deep work\", \"Lunch\")"),
+            type: z
+                .enum(["block", "tasks"])
+                .optional()
+                .describe("'block' = activity (default). 'tasks' = task bucket: a window that gathers the day's untimed tasks."),
+            duration_minutes: z
+                .number()
+                .int()
+                .min(1)
+                .max(1440)
+                .optional()
+                .describe("Duration in minutes (default 30 for an activity, 60 for a bucket)"),
+            anchor_time: z
+                .string()
+                .regex(/^([01]\d|2[0-3]):[0-5]\d$/)
+                .optional()
+                .describe("Pin the block at a fixed wall-clock hour HH:MM (it becomes a wall other blocks flow around). Omit for automatic first-fit placement."),
+            note: z.string().optional().describe("Free note attached to the block"),
+        },
+        annotations: { title: "Create day block", destructiveHint: false, idempotentHint: false, openWorldHint: false },
+    }, async (params) => {
+        return toContent(await fetchApi("/day-blocks", "POST", params));
+    });
+    server.registerTool("update_day_block", {
+        description: "Update a time block (title, duration, anchor, note, done). Only send fields you want to change. The block keeps its position in the timeline order.",
+        inputSchema: {
+            id: z.string().uuid().describe("Block UUID"),
+            title: z.string().nullable().optional().describe("Block label"),
+            duration_minutes: z
+                .number()
+                .int()
+                .min(1)
+                .max(1440)
+                .optional()
+                .describe("Duration in minutes"),
+            anchor_time: z
+                .string()
+                .regex(/^([01]\d|2[0-3]):[0-5]\d$/)
+                .nullable()
+                .optional()
+                .describe("Fixed wall-clock hour HH:MM. Pass null to unpin (the block flows with the rest again)."),
+            note: z.string().nullable().optional().describe("Free note. Pass null to clear."),
+            done: z.boolean().optional().describe("Mark the block done (true) or not done (false)"),
+        },
+        annotations: { title: "Update day block", destructiveHint: false, idempotentHint: true, openWorldHint: false },
+    }, async ({ id, ...body }) => {
+        return toContent(await fetchApi(`/day-blocks/${id}`, "PATCH", body));
+    });
+    server.registerTool("delete_day_block", {
+        description: "Delete a time block. Its ref is pruned from the day's timeline_order; for a task bucket, the tasks themselves are untouched (they fall back to the day's computed bucket).",
+        inputSchema: {
+            id: z.string().uuid().describe("Block UUID"),
+        },
+        annotations: { title: "Delete day block", destructiveHint: true, idempotentHint: true, openWorldHint: false },
+    }, async ({ id }) => {
+        return toContent(await fetchApi(`/day-blocks/${id}`, "DELETE"));
+    });
+    // ===========================================================================
     // TAGS
     // ===========================================================================
     server.registerTool("list_tags", {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "keepsake-mcp",
-  "version": "1.8.0",
+  "version": "1.9.1",
   "description": "MCP server for Keepsake personal CRM \u2014 connect your AI agent to your contacts, tasks, notes, and more",
   "type": "module",
   "bin": {