MCP Server Reference

List the user's task records (execution instances). Filter by keyword, state, date range (ISO 8601), or project. Returns brief entries — use get_task for full detail.

Get a task record in full detail, including all structured writing fields (description, target, expectation, obstacle, stakes, result, retrospect), schedule, state, and satisfaction.

Create a task record. priority/difficulty 1-5, dates ISO 8601, project_id links it to a goal. Title only — add a description later via update_task_writing only if the user dictates one. reminder_minutes_before (needs start_date): 0/5/15/30/60/1440; omit = none.

Change a task record's fields after creation — pass only what changes. start_date/end_date set the schedule (ISO 8601); reminder_minutes_before is 0/5/15/30/60/1440 before start (needs a start_date); satisfaction 1-5 rates a completed task; priority/difficulty 1-5; point_color is the star color; address is a place name; instruction is how-to guidance; assigned_to is an achiever id (project tasks only); duration_seconds is planned duration. (To change state use set_task_state; for writing spaces target/result/… use update_task_writing.)

Change a task record's state (registered → started → completed / cancelled).

Set (or unset) the user's single focused task — the one task to concentrate on now. Focusing a task automatically unfocuses any previously focused task.

Write one of a task's structured writing spaces (Fecit core). Fields: target=current situation; expectation=desired change; obstacle=what's in the way; stakes=cost if it fails; result=what happened; retrospect=lessons; also description. Plain text with newlines OK.

Split a big task into a sequential chain of subtasks linked in order (step 1 → 2 → …). Use when a task feels too big and the user wants concrete next steps. Provide 2-5 SHORT ordered action titles (never numbered in the text); never more than 5. Steps append after existing ones; don't over-split a simple to-do.

Permanently delete a task record. This cannot be undone.

Add a preparation item to a task record (what's needed to do it). materials/tools take quantity+unit, venue takes address, personnel takes specialty, qualification takes issuer; cost is free text. Existing items are in get_task (each has an `order`).

Remove a preparation item from a task record by its `order` (from get_task).

Add a response rule (implementation intention) to a task record — an if-then plan: when `situation` happens, do `response`. Existing rules are visible in get_task (each has an `order`).

Remove a response rule from a task record by its `order` (from get_task).

Search the user's task templates (reusable blueprints in the Library).

Get a task template in full detail.

Instantiate a task record from a template, optionally scheduling it.

List the user's projects. A project IS a goal (not a folder), carrying target/expectation/result/retrospect.

Get a project (goal) in full detail: goal-definition fields (target, expectation, obstacle, stakes), outcome fields (result, retrospect, satisfaction), state, dates, and milestones.

Create a new project (goal). abbreviation is a short code (e.g. 'FIT' for a fitness goal) used in task codes.

Write into a project's goal-definition or outcome fields. target: the concrete goal / expectation: anticipated outcome / obstacle: foreseen blockers / stakes: why it matters / result: what actually happened / retrospect: lessons learned.

Change a project's state.

Permanently delete a project (goal) along with its goal fields, journal, and milestones. This cannot be undone.

Add a journal entry to a project — an in-progress checkpoint note on how the goal is going.

List a project's journal entries (newest first).

Add a milestone (intermediate goal checkpoint) to a project. Milestones deliberately do not link to tasks.

Mark a project milestone as achieved (or back to pending). Get milestone_key from get_project's milestones array.

Get a project's activity feed — who did what (task completions, journal entries, member joins, state changes, milestone achievements). Useful for shared projects.

Search the user's memo records by keyword and/or project.

Get a memo record in full, including its content.

Create a memo record. Plain text content with newlines is accepted.

Replace a memo's content. Plain text with newlines is accepted.

Permanently delete a memo record. This cannot be undone.

List the user's daily reviews in a date range (newest first).

Create or update the daily review for a given date (ISO 8601, the day being reviewed). satisfaction is 1-5.

Create or update the weekly review for the week starting at week_start (ISO 8601 datetime — local midnight of the user's week start day, as provided by the weekly-review prompt or list_weekly_reviews). satisfaction is 1-5.

List the user's labels (color-coded tags for tasks/memos). Filter by keyword or state.

Create a label (color-coded tag). point_color is one of the 20 Fecit colors.

Archive a label (hide it) or reactivate it.

Permanently delete a label and its links to tasks/memos.

Attach a label to a task record OR a memo record. Provide exactly one of task_id / memo_id.

Detach a label from a task/memo by its label-link id (get the id from list_label_links).

List the label links on a task record OR a memo record (provide exactly one). Each entry has its link id (for unlink_label) and the nested label.

List folders for one of the four item trees (task/memo × record/template). Folders are exclusive containers, separate from labels and projects. scope='project' needs project_id.

Create a folder in one of the four item trees. Nest it under parent_folder_id if given. scope='project' needs project_id.

Rename a folder and/or move it under another parent folder. Only the fields you pass change.

Delete a folder and its subfolders (cascade). Items inside are NOT deleted — they just leave the folder.

Move a task/memo (record or template) into a folder, or remove it from its folder (omit folder_id). item_type selects which of the four trees the folder belongs to.

List the user's routines (recurring task generators). Filter by period (daily/weekly) and whether they're archived. With no period, returns both daily and weekly.

Get a single routine in full detail.

Create a routine that spawns a task on a schedule. period='daily'/'weekly'. start_date (ISO 8601) sets when it begins and the time of day; for 'weekly' give weekday. Base it on a task_template_id or give a title. end_date optionally stops it; reminder_minutes_before reminds on each spawned task.

Permanently delete a routine. Tasks it already spawned are not affected.

Attach a web link (URL) to a task or memo (record or template). item_type selects which.

Remove a web link from a task/memo by its order index (see the item's web_links list).

Get the user's completion streak: current_streak, longest_streak, completed_today, and streak start/last-completion dates. Use to recognize and celebrate their momentum.

List the user's achievements (badges) with progress — each has title, description, threshold, progress, and achieved_at (null if not yet earned). Use to acknowledge milestones.

Get the user's current Dana balance (Fecit's reward points).

Current datetime in the user's local timezone. Call before interpreting relative dates ('today'/'tonight'/'tomorrow'). When passing a datetime to other tools, output local wall-clock time (e.g. 2026-06-13T21:00:00); the system converts it to the correct instant.