Schedule a Backlog Task
Find [task] in my Sunsama backlog and move it to [day].
Leina connects to Sunsama MCP to help you plan your day, schedule tasks, and reserve focus time. Ask in your team chat. Leina does the work and brings back the result.
Connect Sunsama MCP, choose what to share, and hand off your first task.
You
Timebox my selected “Launch brief” task tomorrow at 9:00 for 45 minutes in Sunsama.
Leina
I added a 45-minute timebox for Launch brief tomorrow morning.
Sunsama · Time reserved
Launch brief
A focused work session on tomorrow’s calendar.
A Sunsama AI agent helps find backlog tasks, move work to the right day, and reserve calendar time for focused work.
You specify the source and the destination. Leina uses the content available to your connection and returns the result for you to review.
Sunsama brings tasks and calendar time into a daily planning workspace.
Name the existing task and preferred start time.
Create a timebox with the requested duration.
See the scheduled task on your calendar.
Copy a prompt, add your details, and send it to Leina in your connected team chat.
Find [task] in my Sunsama backlog and move it to [day].
Put the selected Sunsama task on my calendar at [date and time] for [duration].
Your next Sunsama MCP task can start with a message.
Tell Leina what you need in your team chat. Include the source, destination, and expected result.
Connect the tools involved and give Leina access to the content it needs.
Share the source material, say where the result belongs, and describe what you need.
Review the result and any changes in the connected app.
Hand off these everyday tasks to your AI employee.
Creates a single task with a title, optional notes (markdown), and estimated time. Scheduled to a day by default; pass `backlog` instead to stage it in the backlog. This is also the tool for a task that links to an item in another tool — pass `integrationUrl`, which works for a backlog task too.
Repositions a task within the backlog by moving it to a specific time bucket (horizon) and position (append/prepend).
Moves one or more tasks to a backlog folder. If folderId is null, removes tasks from their current folder.
Aligns a task with an objective.
Adds a task to a channel.
Moves or defers a task to a specific date.
Moves a task out of the backlog and onto a specific date.
Unarchives a task and moves it to a specific date or the backlog if no date is provided.
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.
Gets the time estimate for a task in minutes.
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.
Updates the title of an existing task.
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).
Updates the time estimate of an existing task.
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.
Appends Markdown content to the end of an existing task's notes. Existing notes are preserved; the new content is added below them with a horizontal rule separator. Use edit_task_notes to replace the notes body entirely.
Deletes an existing task.
Adds multiple subtasks to an existing task. Do not use for merging existing tasks in as subtasks.
Changes a task from deleted to not deleted.
Marks a task as completed. Can also be used to move a task to a previous day which auto-completes the task.
Marks a task as incomplete.
Updates the title of an existing subtask.
Marks a subtask of an existing task as completed.
Marks a subtask of an existing task as incomplete.
Reorders tasks for the calendar day according to the provided order of taskIds.
Fetches the users backlog tasks
Fetches the users archived tasks
Searches for tasks. Returns tasks that match the search term or are similar to the search term.
Updates all incomplete instances of a recurring task to match the current task. This is useful when you want to apply changes made to one instance of a recurring task to all future incomplete instances.
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.
Starts the timer for a task or subtask. If a subtaskId is provided, starts the timer for that specific subtask.
Stops the timer for a task or subtask. If a subtaskId is provided, stops the timer for that specific subtask.
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.
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.
Fetches a single task by its Sunsama task ID. Returns full task details including integration information.
Updates a calendar event's date, time, and/or duration.
Creates a new calendar event.
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".
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.
Imports a calendar event as a task.
Confirms attendance to a meeting that the user is invited to.
Decline attendance to a meeting that the user is invited to.
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.
Enables or disables automatic importing of calendar events to the daily task list.
Updates the exclusion filters that determine which calendar events are excluded from automatic import. Events matching any of these filters will NOT be automatically imported.
Updates preferences for a specific calendar including whether it is the default for tasks, default for events, and whether it is included in auto-importing of events.
Creates a new weekly objective.
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.
Sets the shutdown time for a specific day.
Creates a new channel for the user.
Renames one of the user's channels. Takes a channel ID, not a channel name — use the search_channels tool to resolve a name the user mentions into an ID first. Renaming only changes the channel's label; the tasks, objectives, and calendar events assigned to it stay assigned.
Deletes one of the user's channels. Takes a channel ID, not a channel name — use the search_channels tool to resolve a name the user mentions into an ID first. Tasks, objectives, and calendar events in the channel are not deleted, but they lose their channel assignment and cannot be reassigned by undoing this. Deleting a category also uncategorizes the channels inside it. This cannot be undone, so confirm with the user before calling it.
Searches the user's channels by meaning, not just by exact name. Returns the closest matching channels ordered by relevance, so "client work" can match a channel named "Acme Corp". Use this to resolve a channel a user mentions into a channel ID before assigning tasks to it.
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
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.
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.
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.
Discover the current Sunsama task and daily planning MCP tools with their live input schemas.
Call a Sunsama MCP tool with JSON arguments.
Connect the Apps your work depends on, and give Leina the context to carry the task forward.
Hand off a task while your team is discussing it. Leina uses your connected tools and brings the result back to the conversation.
See How Leina Works in SlackI added a 45-minute timebox for Launch brief tomorrow morning.
The planned day and the due date are separate. Say explicitly if you want to change the deadline too.
Yes. Ask to append the new notes rather than replace the task’s notes.
Start with one task you already need to do. Tell Leina what a finished result should look like.
Connect Sunsama MCP, choose what to share, and hand off your first task.