Sunsama

Creates a new channel for the user.

create_channel

Creates a single task with a title, optional notes (markdown), and estimated time.

create_task

Creates a new weekly objective.

create_weekly_objective

Decline attendance to a meeting that the user is invited to.

decline_meeting_invite

Removes a calendar event and deletes all associated tasks. If the event is a meeting then any access role can remove the event. Otherwise only owners or writers can remove the event. Note: If the event is a meeting and the user is an owner or write this will remove the event for ALL attendees.

delete_calendar_event

PERMANENTLY deletes incomplete instances of a recurring task and TERMINATES the series, preventing any future instances from ever being created. This is irreversible. When afterDate is provided, only instances after that date are deleted and the series is terminated at that date. When omitted, all incomplete instances are deleted. WARNING: If the user wants to temporarily skip a period (e.g. vacation) and resume the series afterwards, do NOT use this tool — use edit_task_recurrence_rule with deleteOldInstancesAfter and firstOccurrenceOnOrAfter instead.

delete_all_incomplete_recurring_task_instances

Deletes an existing task.

delete_task

Updates the title of an existing subtask.

edit_subtask_title

Sets or clears the due date of a task. This is the hard deadline, not the day the task is planned/scheduled for (use move_task_to_day for that).

edit_task_due_date

Replaces the notes body of an existing task with new Markdown content. The full notes field is overwritten — use append_task_notes to add to existing notes without replacing them.

edit_task_notes

Updates the recurrence rule of an existing task. This is the preferred tool for temporarily pausing or skipping a recurring task for a specific period (e.g. vacation, leave). By combining deleteOldInstancesAfter (to clear instances during the skip period) and firstOccurrenceOnOrAfter (to restart the series afterwards), you can maintain the recurrence while accommodating temporary breaks — unlike delete_all_incomplete_recurring_task_instances which permanently terminates the series. When firstOccurrenceOnOrAfter is provided, this forks the recurring series: a new series begins from that date and the old series ends the day before.

edit_task_recurrence_rule

Updates the time estimate of an existing task.

edit_task_time_estimate

Updates the title of an existing task.

edit_task_title

Fetches the users archived tasks

get_archived_tasks

Fetches the users backlog tasks

get_backlog_tasks

Gets a list of daily highlights (end of day journal entries of your work day) for the user. Returns published daily wraps in Markdown format. If startDate and endDate are omitted, returns only the most recent one.

get_daily_highlights

Fetches the full text of a single Sunsama help center article. First call "list_help_articles" to find the relevant article, then pass its id here. Returns the article title, url, and plain-text body so you can answer the user's question from the docs.

get_help_article

Fetches a single task by its Sunsama task ID. Returns full task details including integration information.

get_task_by_id

Imports a calendar event as a task.

import_task_from_calendar_event

Lists all available resources and resource templates exposed by this MCP server. Use this tool to discover what data sources are available when the client doesn't support the MCP resources protocol natively. Returns an array of resources, where each resource has: - name: The resource identifier - uri: The static URI (for fixed resources) OR uri_template (for parameterized resources) - description: What the resource provides - mimeType: The content type returned

list_resources

Lists Sunsama's help center articles as a catalog: each entry has an id, title, description, category, and url. Use this whenever the user asks how a Sunsama feature works, what Sunsama can or cannot do, or whenever you are unsure about product behavior or a limitation. Pick the most relevant article from the list, then call "get_help_article" with its id to read it and answer from the docs instead of guessing. You can also share the article url with the user.

list_help_articles

Marks a subtask of an existing task as incomplete.

mark_subtask_as_incomplete

Marks a task as incomplete.

mark_task_as_incomplete

Updates a calendar event's date, time, and/or duration.

move_calendar_event

Moves a task out of the backlog and onto a specific date.

move_task_from_backlog

Moves a task to the backlog. IF THE USER ASKS YOU TO MOVE A TASK TO A SPECIFIC DAY THEN YOU SHOULD USE THE move_task_to_day TOOL NOT THIS ONE.

move_task_to_backlog

Moves or defers a task to a specific date.

move_task_to_day

Gets the time estimate for a task in minutes.

get_task_time_estimate

Reads a specific resource by URI. Use this tool to fetch data from resources when the client doesn't support the MCP resources protocol natively. For static resources, pass the exact URI from list_resources. For templated resources, fill in the placeholders with actual values. Example: If list_resources shows uri_template "sunsama://tasks/{calendarDay}", you would call this with uri "sunsama://tasks/2025-01-15" to get tasks for that day.

read_resource

Reorders tasks for the calendar day according to the provided order of taskIds.

reorder_tasks

Repositions a task within the backlog by moving it to a specific time bucket (horizon) and position (append/prepend).

reposition_task_in_backlog

Changes a task from deleted to not deleted.

restore_task

Searches for tasks. Returns tasks that match the search term or are similar to the search term.

search_tasks

Sets the backlog priority of a task. Backlog priority persists and is used for tasks in the backlog. Valid values: "urgent", "high", "medium", "low", "none". Set to null to clear.

set_backlog_priority

Sets the daily priority of a task. Daily priority is tied to a specific day and decays after that day. Valid values: "urgent", "important", "normal", "low". Set to null to clear. The date is automatically determined from the task.

set_daily_priority

Sets whether tasks are allowed to be automatically projected (scheduled) at the same time as a calendar event. When set to true, tasks can be automatically projected during the event. When set to false, tasks cannot be automatically projected during the event. Note: This only affects automatic projections; users can still manually timebox tasks during this event.

set_calendar_event_allow_task_projections

Sets the shutdown time for a specific day.

set_shutdown_time

Starts the timer for a task or subtask. If a subtaskId is provided, starts the timer for that specific subtask.

start_task_timer

Stops the timer for a task or subtask. If a subtaskId is provided, stops the timer for that specific subtask.

stop_task_timer

Timeboxes a task to the calendar. This will create a timebox event for the task. This may also be referred to as "scheduling" a task or "adding a task to the calendar".

timebox_a_task_to_calendar