add-subtask
Convenience method to create a subtask with a title in one call (recommended for single subtask creation)
LABSCO SUMMARY
The end-of-day sweep becomes two calls: complete what got done, push the rest to tomorrow.
Two things separate this from a thin API wrapper. Updates are field-scoped, so changing an estimate or a due date does not mean reading the task back and resubmitting it. And the bulk variants are built for the moment a plan is rebuilt — they take a list of task IDs and let individual failures pass rather than aborting the batch. Most of the write tools also carry limitResponsePayload, which keeps the reply small when many tasks change at once; streams are called channels in the Sunsama UI, and get-streams is where that mapping comes from.
What it is
A server over the Sunsama task and calendar API, 30 tools spanning tasks, subtasks, streams and calendar events, with bulk variants of the operations that repeat.
What you get
- The day and the backlog as separate reads: get-tasks-by-day with a completion filter and timezone, get-tasks-backlog, get-archived-tasks with limit and offset, get-task-by-id for one
- Scheduling moves that match how a day gets rebuilt — update-task-snooze-date to push a task to another day or back to the backlog, update-task-backlog, and reorder-task to a 0-based position where 0 is the top
- Field-scoped updates instead of resubmitting a task: text, notes as markdown or html, due date, planned time in minutes, and stream assignment each have their own tool
- Subtasks handled both ways: add-subtask creates one from a title in a single call, create-subtasks covers bulk, and complete-subtask, uncomplete-subtask and update-subtask-title work on them individually
- Bulk endpoints for the end-of-day sweep — update-task-complete-bulk, update-task-uncomplete-bulk, update-task-snooze-date-bulk, update-task-backlog-bulk and delete-task-bulk — each documented so that individual failures do not block the others
- Calendar events created and updated in the same session, with get-streams resolving the channels that tasks are filed under
Requirements
A Sunsama account, signed in with its email and password as SUNSAMA_EMAIL and SUNSAMA_PASSWORD. update-calendar-event needs the full CalendarEventUpdateData object, so the event has to be fetched before it is changed. MIT licensed.
Setup effort
One command plus credentials — npx -y mcp-sunsama, then supply credentials
USE CASES
01
Building tomorrow out of the backlog
Pull what is waiting, move the chosen items onto tomorrow's date, attach a realistic estimate to each, and put them in the order you intend to work them.
02
Closing out the day
Read the day with a completion filter to see what is left, mark everything finished in one call, and push the remainder to a chosen date in another.
03
Breaking a task that has grown too big
Read the task as it stands, add the steps — one at a time by title, or as a batch — and tick them off as they land without touching the parent.
04
Getting prep time on the calendar next to the meeting
Resolve the channel the work belongs to, put the event on the calendar, and create the task that prepares for it so the estimate lands in the same day's plan.
30 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
complete-subtask
Mark a subtask as complete with optional completion timestamp
create-calendar-event
Create a new calendar event in Sunsama
create-subtasks
Create multiple subtasks for a task (low-level API for bulk operations)
create-task
Create a new task with optional properties
delete-task
Delete a task permanently
delete-task-bulk
Delete multiple tasks permanently in a single operation. Individual failures do not block others.
get-archived-tasks
Get archived tasks with optional pagination
get-streams
Get streams for the user's group (streams are called 'channels' in the Sunsama UI)
get-task-by-id
Get a specific task by its ID
get-tasks-backlog
Get tasks from the backlog
get-tasks-by-day
Get tasks for a specific day with optional filtering by completion status
get-user
Get current user information including profile, timezone, and group details
reorder-task
Reorder a task within a day by moving it to a specific 0-based position (0 = top)
uncomplete-subtask
Mark a subtask as incomplete (uncomplete it)
update-calendar-event
Update an existing calendar event. Requires the full CalendarEventUpdateData object — fetch the event first to get all required fields.
update-subtask-title
Update the title of a subtask
update-task-backlog
Move a task to the backlog
update-task-backlog-bulk
Move multiple tasks to the backlog in a single operation. Individual failures do not block others.
update-task-complete
Mark a task as complete with optional completion timestamp
update-task-complete-bulk
Mark multiple tasks as complete in a single operation. Individual failures do not block others.
update-task-due-date
Update the due date for a task
update-task-notes
Update the notes content for a task
update-task-planned-time
Update the planned time (time estimate) for a task
update-task-snooze-date
Update task snooze date to reschedule tasks or move them to backlog
update-task-snooze-date-bulk
Reschedule multiple tasks to a specific date in a single operation. Individual failures do not block others.
update-task-stream
Update the stream/channel assignment for a task
update-task-text
Update the text/title of a task
update-task-uncomplete
Mark a completed task as incomplete
update-task-uncomplete-bulk
Mark multiple completed tasks as incomplete in a single operation. Individual failures do not block others.
BEFORE YOU INSTALL
What to know first
Tools you get
30 tools when we connected. The documentation covers 21 and omits the bulk variants, update-task-uncomplete, reorder-task, and the calendar tools create-calendar-event and update-calendar-event.
Requires
- Sunsama account with API access
- SUNSAMA_EMAIL in your environment
- SUNSAMA_PASSWORD in your environment
CONTEXT COST
Moderate Standing cost
Rated by the size of the 30 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y mcp-sunsamaMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"sunsama": {
"command": "npx",
"args": [
"mcp-sunsama"
],
"env": {
"SUNSAMA_EMAIL": "<YOUR_SUNSAMA_EMAIL>",
"SUNSAMA_PASSWORD": "<YOUR_SUNSAMA_PASSWORD>"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add sunsama --scope user \
-e SUNSAMA_EMAIL=<YOUR_SUNSAMA_EMAIL> \
-e SUNSAMA_PASSWORD=<YOUR_SUNSAMA_PASSWORD> \
-- npx mcp-sunsama
