createTask and updateTask carry the fields that usually get lost when a task is filed through an API — starts_at and due_at alongside timeless_starts_at and timeless_due_at for tasks with no clock time, duration_minutes, location, and labels applied by name rather than by id if that is all you have. updateTask also separates add_label_ids and add_label_names from their remove counterparts, so a label edit does not overwrite the rest of the set. What the tool set does not carry is any description text of its own; every capability above is read from the tool names and their parameters.
A task-management front end for a Godspeed account, 11 tools covering tasks and the lists they sit in.
- Task creation with the scheduling fields attached: createTask takes a title, notes, list, start and due times, a timeless variant of each, duration in minutes, labels by id or name, a location and free-form metadata; bulkCreateTask takes an array of them in one call.
- Updates that address labels individually: updateTask adds or removes labels by id or name, moves start and due times, sets duration, notes, completion and cleared state, and can snooze a task until a given time.
- Completion handled in both directions: completeTask, uncompleteTask and deleteTask, with getTask for a single task by id.
- Reading the list back with filters: listTasks narrows by list, by status and by an updated_after / updated_before window.
- List-level operations: getTaskLists returns the account's lists, createTaskList makes a new one, duplicateList copies an existing list under a new name.
A Godspeed account and the access token the server reads from the environment. Tasks and lists are addressed by id, so getTaskLists comes before anything that takes a list_id.
One command plus a key — npx -y godspeed-mcp, then supply credentials