keepsake-mcp 1.14.1 → 1.15.0

package/README.md

@@ -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 (83)
+## Available tools (84)
 
 ### Contacts
 | Tool | Description |
@@ -165,10 +165,11 @@ rather than in the chat, which disappears.
 ### QuickNotes
 | Tool | Description |
 |------|-------------|
-| `list_notes` | List notes — filter by pinned/archived, day, company, page (`tag_id`) |
+| `list_notes` | List notes — filter by pinned/archived, day, company, page (`tag_id`), publication-flow stage (`status`) |
+| `list_note_statuses` | The stages of the user's publication flow (Idea → In progress → To review → Ready → Published by default — the user can rename, add or remove them) |
 | `get_note` | Get one note by ID with its tags, contacts, tasks and linked notes |
-| `create_note` | Create a note — supports `#tag#` and `[[tag]]` syntax |
-| `update_note` | Update note content |
+| `create_note` | Create a note — supports `#tag#` and `[[tag]]` syntax; `status` puts it straight into the publication flow |
+| `update_note` | Update note content, links, days, or its publication-flow stage (`status`) |
 | `delete_note` | Soft-delete (or permanent) |
 | `pin_note` | Pin as a post-it (short reference always at hand) |
 | `archive_note` | Archive a note |

package/build/tools.js

@@ -97,7 +97,8 @@ function withNoteHint(result) {
     if (count > 0) {
         hints.push(`This note carries ${count} marginalia — read them with list_note_comments before adding your own, so you do not repeat what is already said.`);
     }
-    if (note.workflow_status === "draft" || note.workflow_status === "review") {
+    const status = note.status;
+    if (status && (status.category === "unstarted" || status.category === "started")) {
         hints.push("The user is still working on this text: if they ask you to review it, put your remarks in the margin (create_note_comment, anchored with a verbatim quote) rather than in the chat, and do not rewrite the note itself.");
     }
     if (!hints.length)
@@ -546,8 +547,12 @@ export function registerAllTools(server, fetchApi) {
     // QUICK NOTES
     // ===========================================================================
     server.registerTool("list_notes", {
-        description: "List notes. QuickNotes (inbox, not yet archived) and Notes (archived, permanent). Filter by pinned or archived status, by tag (page) with `tag_id`, or by the day(s) a note is linked to (`date`, or `date_from`/`date_to`) — e.g. \"what did I note for tomorrow?\". Each note carries `dates`, the days it is linked to.",
+        description: "List notes. QuickNotes (inbox, not yet archived) and Notes (archived, permanent). Filter by pinned or archived status, by tag (page) with `tag_id`, by the day(s) a note is linked to (`date`, or `date_from`/`date_to`) — e.g. \"what did I note for tomorrow?\" —, or by publication-flow stage with `status` — e.g. \"which notes are waiting for review?\". Each note carries `dates` (the days it is linked to) and `status` (its stage in the publication flow, or null).",
         inputSchema: {
+            status: z
+                .string()
+                .optional()
+                .describe("Publication-flow stage: a stage name, key or id from list_note_statuses (e.g. \"review\"), \"publication\" (every note in the flow that is not published yet), or \"none\" (notes outside the flow)"),
             pinned: z.boolean().optional().describe("Filter pinned notes only"),
             archived: z.boolean().optional().describe("Filter by status: true = Notes (archived/permanent), false = QuickNotes (inbox)"),
             date: z.string().optional().describe("Only notes linked to this day (YYYY-MM-DD)"),
@@ -559,8 +564,15 @@ export function registerAllTools(server, fetchApi) {
             offset: z.number().int().nonnegative().optional().describe("Pagination offset"),
         },
         annotations: { title: "List notes", readOnlyHint: true, openWorldHint: false },
-    }, async ({ pinned, archived, date, date_from, date_to, company_id, tag_id, limit, offset }) => {
-        return toContent(await fetchApi(`/notes${qs({ pinned, archived, date, date_from, date_to, company_id, tag_id, limit, offset })}`));
+    }, async ({ status, pinned, archived, date, date_from, date_to, company_id, tag_id, limit, offset }) => {
+        return toContent(await fetchApi(`/notes${qs({ status, pinned, archived, date, date_from, date_to, company_id, tag_id, limit, offset })}`));
+    });
+    server.registerTool("list_note_statuses", {
+        description: "List the stages of the user's publication flow, in order (by default: Idea → In progress → To review → Ready → Published). A note enters this flow when the user may publish it — most notes never do and have no stage. Stages are the user's own: they can rename, recolor, add or remove them, so read this list before setting a stage with update_note or create_note. `category` is fixed: unstarted, started, or published (exactly one stage). Names are in the user's app language.",
+        inputSchema: {},
+        annotations: { title: "List note statuses", readOnlyHint: true, openWorldHint: false },
+    }, async () => {
+        return toContent(await fetchApi("/note-statuses"));
     });
     server.registerTool("get_note", {
         description: "Get a single note by ID, including its tags, linked contacts, linked tasks, linked notes and the days it is linked to (`dates`). Use this when the user points you at one specific note (e.g. gives you its URL — the UUID is the last path segment) instead of listing everything.",
@@ -588,13 +600,17 @@ export function registerAllTools(server, fetchApi) {
                 .array(z.string())
                 .optional()
                 .describe("Days to link the note to (YYYY-MM-DD each). The note appears in each day's view."),
+            status: z
+                .string()
+                .optional()
+                .describe("Put the note straight into the publication flow at this stage (name, key or id from list_note_statuses). The note is then created as a permanent Note, not an Inbox QuickNote — like \"Keep to publish\" in the app. Only when the user says they may publish it."),
         },
         annotations: { title: "Create note", destructiveHint: false, idempotentHint: false, openWorldHint: false },
     }, async (params) => {
         return toContent(await fetchApi("/notes", "POST", params));
     });
     server.registerTool("update_note", {
-        description: "Update an existing QuickNote or Note. `dates` REPLACES the full set of days the note is linked to — the way to move a note to another day (\"not done, push it to tomorrow\"). To add or remove a single day without touching the others, prefer link_note_date / unlink_note_date.",
+        description: "Update an existing QuickNote or Note. `dates` REPLACES the full set of days the note is linked to — the way to move a note to another day (\"not done, push it to tomorrow\"). To add or remove a single day without touching the others, prefer link_note_date / unlink_note_date. `status` moves the note along the publication flow (\"this one is ready\"); setting a stage on an Inbox QuickNote also keeps it as a Note.",
         inputSchema: {
             id: z.string().uuid().describe("Note UUID"),
             content: z.string().optional().describe("Updated content"),
@@ -614,6 +630,11 @@ export function registerAllTools(server, fetchApi) {
                 .array(z.string())
                 .optional()
                 .describe("Replace the days the note is linked to (YYYY-MM-DD each). Empty array = unlink from every day."),
+            status: z
+                .string()
+                .nullable()
+                .optional()
+                .describe("Publication-flow stage: name, key or id from list_note_statuses. null takes the note out of the flow."),
         },
         annotations: { title: "Update note", destructiveHint: false, idempotentHint: true, openWorldHint: false },
     }, async ({ id, ...body }) => {
@@ -661,7 +682,7 @@ export function registerAllTools(server, fetchApi) {
     // DAYS (Daily Summaries)
     // ===========================================================================
     server.registerTool("list_days", {
-        description: "List stored days with their intention or question of the day. An intention stays in place until changed: `intention` is the one in force that day (the last one written on that day or before, `intention_date` = when it was written); `note` is what was written on that exact day (null = nothing written). Filter by date range.",
+        description: "List stored days with their intention or question of the day (`note`; `intention` repeats it, null when empty). An intention is valid for its own day only — it does not carry over to the following days. 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)"),
@@ -673,7 +694,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 by date: its intention or question of the day AND the notes linked to that day (field `notes`, via link_note_date / `dates`). An intention stays in place until changed: `intention` is the one in force that day, as the user sees it (the last one written on that day or before; `intention_date` = the day it was written), while `note` is what was written on that exact day (null = nothing written there, '' = intention stopped from that day). Always 200 — `exists: false` means no row is stored for that date; `intention` and the linked notes are returned regardless.",
+        description: "Get a specific day by date: its intention or question of the day AND the notes linked to that day (field `notes`, via link_note_date / `dates`). `note` is the intention written for that day (null or '' = none; `intention` repeats it). An intention is valid for its own day only — it does not carry over. Always 200 — `exists: false` means no row is stored for that date; `intention` and the linked notes are returned regardless.",
         inputSchema: {
             date: z.string().describe("Date (YYYY-MM-DD)"),
         },
@@ -682,10 +703,10 @@ export function registerAllTools(server, fetchApi) {
         return toContent(await fetchApi(`/days/${date}`));
     });
     server.registerTool("update_day", {
-        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.\n\nAn intention stays in place until changed: writing it on a day replaces the intention from that day onward (following days show it too, until the next day with its own intention — set one on a future date for a one-off, e.g. before a meeting). `null` removes what was written on that day (the day goes back to the intention in force before it); an empty string stops any intention from that day onward. Check `intention` with get_day before writing: you may be replacing a long-running intention the user cares about.\n\nNOT for attaching a note to a day: this field is a single line and you would overwrite the user's intention. To put a note on a day, use create_note with `dates` or link_note_date.",
+        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.\n\nAn intention is valid for its own day only: it does not carry over to the following days. The user types it by hand each morning, on purpose — do not set it for them unless they ask. `null` or an empty string removes it.\n\nNOT for attaching a note to a day: this field is a single line and you would overwrite the user's intention. To put a note on a day, use create_note with `dates` or link_note_date.",
         inputSchema: {
             date: z.string().describe("Date (YYYY-MM-DD)"),
-            note: z.string().nullable().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. null = remove what was written on this day (back to the previous intention); empty string = stop any intention from this day onward."),
+            note: z.string().nullable().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. null or empty string = no intention that day."),
         },
         annotations: { title: "Update day", destructiveHint: false, idempotentHint: true, openWorldHint: false },
     }, async (params) => {

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "keepsake-mcp",
-  "version": "1.14.1",
-  "description": "MCP server for Keepsake personal CRM \u2014 connect your AI agent to your contacts, tasks, notes, and more",
+  "version": "1.15.0",
+  "description": "MCP server for Keepsake personal CRM — connect your AI agent to your contacts, tasks, notes, and more",
   "type": "module",
   "bin": {
     "keepsake-mcp": "build/index.js"
@@ -31,11 +31,11 @@
   "license": "MIT",
   "mcpName": "io.github.nicolascroce/keepsake",
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.12.1",
-    "zod": "^3.24.4"
+    "@modelcontextprotocol/sdk": "^1.32.1",
+    "zod": "^4.6.5"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",
-    "typescript": "^5.8.0"
+    "typescript": "^7.0.2"
   }
 }