MCP server: expose due date/reminder on notes, and per-task management tools

[virtuarsys]

Following up on the recent 6.61.0 additions (calendar view, recurring reminders, colored tags, due dates on Kanban cards) — really happy with those. While using the MCP server to automate note/task creation, I ran into two related gaps:

1. No way to set a note's due date/reminder via create_note / update_note
   These tools accept content, tags, folder, workspace, etc., but nothing for the due date + reminder (+ recurrence, now that it exists) that's available in the UI via the bell icon. Right now, setting a reminder on a note created through MCP requires opening the note manually afterward.

2. No dedicated tools for managing individual tasks inside a tasklist
   The only way to add/update/complete a single task via MCP today is to re-fetch and rewrite the entire tasklist's content JSON array. Beyond being inefficient, the JSON schema for a task (due date, reminder, important flag) isn't documented anywhere (README or API-REST.md), so it has to be guessed. Dedicated tools, e.g. add_task(note_id, text, due_date?, reminder?), update_task(note_id, task_id, ...), complete_task(note_id, task_id), would fix both the ergonomics and the schema ambiguity in one go. planka-style tools (isCompleted, dueDate as explicit typed parameters) are a good reference model.

Both would make MCP-driven task automation (calendar reminders, recurring routines, migrating boards from other tools) much more reliable.

[timothepoznanski]

Thanks for the detailed write-up, and glad the 6.61.0 additions are working well for you! Both gaps are now implemented.

1. Due date / reminder on create_note and update_note

Both tools now accept reminder_at, reminder_recurrence, reminder_message and reminder_email, so you can set the bell-icon reminder in the same call that creates the note, no manual follow-up needed. There are also three dedicated tools if you'd rather set it separately: get_reminder, set_reminder and remove_reminder. update_note can set a reminder on its own without touching the note content, and reminder_at: "none" clears it.

2. Per-task tools

Added exactly along the lines you suggested: add_task, update_task, complete_task, plus list_tasks and delete_task. Due dates, reminders, recurrence and the important flag are explicit typed parameters, so there's no more fetching and rewriting the whole content array. Call list_tasks to get task IDs, then act on one task at a time. Reminders stay in sync automatically: completing or deleting a task retires its pending notification.

One naming note: I went with due_at rather than due_date, to match the dueAt field the task JSON already uses and the existing reminder_at parameter on the reminder endpoints. Happy to revisit if due_date reads better to you.

On the schema being undocumented: the task object schema was actually already in docs/API-REST.md under "Tasks", though it clearly wasn't easy to find, which amounts to the same problem in practice. It's now joined by the new per-task REST endpoints (GET/POST /notes/{id}/tasks, PATCH/DELETE /notes/{id}/tasks/{taskId}), and the whole API reference plus the Swagger spec have been audited for completeness along the way. The MCP tool lists in the docs are up to date too.

Two things worth knowing about dates:

reminder_at is an ISO datetime, e.g. 2026-09-01T09:00:00+02:00. Include the offset, or it's read as UTC.
Task due_at is local wall-clock time (YYYY-MM-DD or YYYY-MM-DDTHH:MM, no offset), resolved through your configured timezone. A date with no time reminds at 09:00, same as the UI.
Recurrence uses the same format as the UI (i/h/d/w/m/y), e.g. 30i, 1d, 2w.

You’re right. I had quite a bit of work to do to get my documentation and endpoints back in order. 😅