@starascendin/lifeos-mcp 0.7.71 → 0.7.72

package/README.md

@@ -98,8 +98,8 @@ Add to your `.mcp.json` (project root or `~/.claude/mcp.json`):
 - **get_tasks** - Get tasks with filters (project, status, priority)
 - **get_todays_tasks** - Get today's tasks and top priorities
 - **get_overdue_tasks** - Get open tasks that are already overdue
-- **create_issue** - Create a new task/issue
-- **update_issue** - Update an existing task, including estimate/story points
+- **create_issue** - Create a new task/issue, optionally with a calendar start/end time
+- **update_issue** - Update an existing task, including estimate/story points and scheduled calendar time
 - **mark_issue_complete** - Mark a task as done
 
 ### Phases

package/dist/build-info.d.ts

@@ -1,2 +1,2 @@
-export declare const VERSION = "0.7.71";
-export declare const BUILD_TIME = "2026-05-18T00:11:44.962Z";
+export declare const VERSION = "0.7.72";
+export declare const BUILD_TIME = "2026-05-18T00:53:07.616Z";

package/dist/build-info.js

@@ -1,3 +1,3 @@
 // AUTO-GENERATED — do not edit. Regenerated on every build.
-export const VERSION = "0.7.71";
-export const BUILD_TIME = "2026-05-18T00:11:44.962Z";
+export const VERSION = "0.7.72";
+export const BUILD_TIME = "2026-05-18T00:53:07.616Z";

package/dist/index.js

@@ -295,7 +295,7 @@ const TOOLS = [
     },
     {
         name: "create_issue",
-        description: "Create a new task/issue. Assign to a project (by key like 'KORT') and optionally a phase (by name like 'Building Foundation' or by ID). Set priority, due date, cycle, and initiative.",
+        description: "Create a new task/issue. Assign to a project (by key like 'KORT') and optionally a phase (by name like 'Building Foundation' or by ID). Set priority, due date, calendar start/end time, cycle, and initiative.",
         inputSchema: {
             type: "object",
             properties: {
@@ -324,6 +324,18 @@ const TOOLS = [
                     type: "string",
                     description: "Due date in ISO format like '2024-01-15' (optional)",
                 },
+                scheduledStartAt: {
+                    type: "string",
+                    description: "Calendar start datetime in ISO format like '2026-05-18T09:00:00-07:00' (optional)",
+                },
+                scheduledEndAt: {
+                    type: "string",
+                    description: "Calendar end datetime in ISO format like '2026-05-18T10:30:00-07:00' (optional, required when scheduledStartAt is provided)",
+                },
+                scheduledTimezone: {
+                    type: "string",
+                    description: "IANA timezone for the scheduled block, e.g. 'America/Los_Angeles' (optional)",
+                },
                 cycleId: {
                     type: "string",
                     description: "Assign to a specific cycle (optional)",
@@ -423,6 +435,22 @@ const TOOLS = [
                     type: "string",
                     description: "Due date in ISO format, or empty to clear (optional)",
                 },
+                scheduledStartAt: {
+                    type: "string",
+                    description: "Calendar start datetime in ISO format like '2026-05-18T09:00:00-07:00' (optional)",
+                },
+                scheduledEndAt: {
+                    type: "string",
+                    description: "Calendar end datetime in ISO format like '2026-05-18T10:30:00-07:00' (optional)",
+                },
+                scheduledTimezone: {
+                    type: "string",
+                    description: "IANA timezone for the scheduled block, e.g. 'America/Los_Angeles' (optional)",
+                },
+                clearScheduledTime: {
+                    type: "boolean",
+                    description: "Clear the task's calendar start/end time (optional)",
+                },
                 isTopPriority: {
                     type: "boolean",
                     description: "Mark as top priority (optional)",
@@ -980,7 +1008,7 @@ const TOOLS = [
     },
     {
         name: "apply_planning_patch",
-        description: "Apply an agent-generated day/week/cycle planning patch. Mutates tasks, due dates, top priorities, current cycle goals/assignments, daily fields, issue comments, Daily AI Comments, Weekly AI Comments, and daily/weekly notes.",
+        description: "Apply an agent-generated day/week/cycle planning patch. Mutates tasks, due dates, scheduled start/end times, top priorities, current cycle goals/assignments, daily fields, issue comments, Daily AI Comments, Weekly AI Comments, and daily/weekly notes.",
         inputSchema: {
             type: "object",
             properties: {
@@ -1031,7 +1059,7 @@ const TOOLS = [
                             },
                             payload: {
                                 type: "object",
-                                description: "Operation-specific payload. Use issueIdOrIdentifier for existing tasks, dueDate for scheduling, userNote for notes, body/source for comments, goals for cycle goals.",
+                                description: "Operation-specific payload. Use issueIdOrIdentifier for existing tasks, dueDate for day assignment/deadlines, scheduledStartAt/scheduledEndAt ISO datetimes or startTime/endTime with scheduledDate for calendar time blocks, userNote for notes, body/source for comments, goals for cycle goals.",
                             },
                         },
                         required: ["type", "payload"],
@@ -5459,10 +5487,10 @@ ${notesClause}
 
 Workflow:
 1. Call get_planning_context with daily=true, weekly=true, currentCycle=true, backlog=true, habits=true, dailyFields=true, calendar=true, voiceMemos=true.
-2. Decide today's top 3, tasks to schedule via dueDate, backlog items to pull into the current cycle, and any cycle goal updates.
+2. Decide today's top 3, tasks to assign to the day via dueDate, tasks to time-block via scheduledStartAt/scheduledEndAt, backlog items to pull into the current cycle, and any cycle goal updates.
 3. Call apply_planning_patch with mode "day" and dryRun=false. Use operations as needed:
    - create_issue for new tasks
-   - schedule_issue/update_issue for dueDate/status/priority/estimate changes
+   - schedule_issue/update_issue for dueDate, scheduledStartAt/scheduledEndAt, status, priority, and estimate changes
    - assign_issue_to_current_cycle for current cycle work
    - set_top_priority for today's top 3
    - update_cycle_goals when the current cycle goal should change
@@ -5587,10 +5615,10 @@ ${notesClause}
 
 Workflow:
 1. Call get_planning_context with daily=true, weekly=true, currentCycle=true, backlog=true, habits=true, dailyFields=true, calendar=true, voiceMemos=true.
-2. Shape the week around the current cycle: update cycle goals, pull/assign tasks, schedule tasks with dueDate, and set near-term priorities.
+2. Shape the week around the current cycle: update cycle goals, pull/assign tasks, assign tasks to days with dueDate, time-block tasks with scheduledStartAt/scheduledEndAt, and set near-term priorities.
 3. Call apply_planning_patch with mode "week" and dryRun=false. Use operations as needed:
    - create_issue for new tasks
-   - schedule_issue/update_issue for dueDate/status/priority/estimate changes
+   - schedule_issue/update_issue for dueDate, scheduledStartAt/scheduledEndAt, status, priority, and estimate changes
    - assign_issue_to_current_cycle for current cycle work
    - set_top_priority for immediate focus
    - update_cycle_goals for the active cycle
@@ -5614,11 +5642,11 @@ Do not ask for confirmation; the user intends this planning workflow to mutate L
                     text: `Help me plan my current cycle/sprint in LifeOS and apply the resulting mutations.
 
 1. Call get_planning_context with currentCycle=true, backlog=true, weekly=true, daily=true.
-2. Shape the current cycle: update cycle goals, pull/assign tasks, schedule tasks with dueDate, and set near-term priorities.
+2. Shape the current cycle: update cycle goals, pull/assign tasks, assign near-term tasks with dueDate, time-block tasks with scheduledStartAt/scheduledEndAt, and set near-term priorities.
 3. Call apply_planning_patch with mode "cycle" and dryRun=false. Use operations as needed:
    - create_issue for new tasks
    - assign_issue_to_current_cycle for current cycle work
-   - schedule_issue/update_issue for dueDate/status/priority/estimate changes
+   - schedule_issue/update_issue for dueDate, scheduledStartAt/scheduledEndAt, status, priority, and estimate changes
    - update_cycle_goals for active cycle goals
    - save_daily_note or save_weekly_note when useful as the readable plan artifact
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@starascendin/lifeos-mcp",
-  "version": "0.7.71",
+  "version": "0.7.72",
   "description": "MCP server for LifeOS Project Management - manage projects, tasks, notes, and contacts via AI assistants",
   "type": "module",
   "main": "dist/index.js",