The Superlist connector brings your tasks, lists, and projects into Claude, so you can plan and act on your work without leaving the conversation. Superlist is a collaborative task manager for people and teams. With this connector, Claude can see what is on your plate, capture new work as it comes up, and keep your lists current. Ask what is due today, turn meeting notes into a structured list, reassign work across your team, or tidy up a project that has drifted out of date. Key features Capture tasks: add a single task, or create a whole list of tasks at once from notes, a transcript, or a conversation. Tasks support due dates in your local timezone and repeat rules for recurring work. Stay on top of your day: pull up your Today view and your Inbox to see what is due and what still needs sorting. Search your workspace: find any task or list by keyword before acting on it, so updates land on the right item. Organize lists: create, rename, update, and delete lists. Move tasks between lists, and add or remove labels to keep everything grouped the way you work. Collaborate: assign and unassign tasks to teammates, and share or unshare lists with the people who need them. Complete and clean up: mark tasks done, edit their titles and details, or delete items you no longer need. Everything runs against your live Superlist account, so what Claude sees is what you see in the app, and any change made through Claude shows up instantly for you and your collaborators.
task_uuid (with label) for a single task, or labels for several — never both. Prefer labels when the user asks to label more than one task, so the whole change is applied as one operation.content as GitHub-flavoured markdown task items (e.g. - [ ] First task\n- [ ] Second task) — this seeds the whole list in a single call. Prefer this over creating an empty list and then calling add_task repeatedly. To build a tree of lists, create the parent first, then create each child with parent_list_uuid set to the parent's uuid.update_task instead. Read the thread first with get_messages.update_task or add_label. Provide exactly one of title (single task) or tasks (several) — never both. Prefer tasks when the user asks for more than one task, so they are created as one operation. The exception: for many plain tasks going into a single list, with no per-task due dates or repetition, GitHub-flavoured markdown task items in the content of add_list (new list) or update_list (existing list) are cheaper.assignee_uuid or assignee_email. Assigning a user grants them access to the task.task_uuid (single task) or task_uuids (several) — never both. Prefer task_uuids when the user asks to complete more than one task, so the whole change is applied as one operation. Check each result's outcome — a batch can mix completed and rolled_forward entries.task_uuid (single task) or task_uuids (several) — never both. Prefer task_uuids when the user asks to delete more than one task, so the whole change is applied as one operation.id returned from the search tool.add_task or add_label, and reuse an existing label name instead of inventing a new one. Returns up to 100 unique labels, sorted alphabetically.tasks_truncated is true, use search to find specific tasks within the list.truncated is true, use the search tool to find specific lists by title.get_task. Deleted messages are omitted. To check back for replies, pass the newest synced_at you have seen as since; only messages created or edited after it are returned.get_messages for that.truncated is true, use the search tool to find specific tasks.list_uuid to move into a list, or parent_task_uuid to make the task a subtask of another task — never both. If both are omitted (or list_uuid is null), the task is moved to the user's inbox. Works on subtasks too: a subtask can be moved out of its parent into a list, the inbox, or a different parent task. Provide exactly one of task_uuid (single task) or moves (several) — never both. Prefer moves when the user asks to move more than one task, so the whole change is applied as one operation.task_uuid (with label) for a single task, or labels for several — never both. Prefer labels when the user asks to unlabel more than one task, so the whole change is applied as one operation.complete_task. A task that is already open is left as it is and reported with outcome already_open. Deleted tasks must be restored with restore_task first. Provide exactly one of task_uuid (single task) or task_uuids (several) — never both. Prefer task_uuids when the user asks to reopen more than one task, so the whole change is applied as one operation.task_uuid (single task) or task_uuids (several) — never both. Prefer task_uuids when the user asks to restore more than one task, so the whole change is applied as one operation.fetch tool to retrieve full content.user_uuid or user_email. The actor must already have access to the list. Plan limits on shared list count and collaborators per list are enforced.truncated is true, use the search tool to find specific tasks.user_uuid or user_email. The actor must already have access to the list.content as GitHub-flavoured markdown task items rather than calling add_task repeatedly. Editing body content replaces it wholesale — to ADD to existing content, read it first with get_list and resend it with your additions.task_uuid (single task) or updates (several) — never both. Prefer updates when the user asks to change more than one task, so the whole change is applied as one operation. Editing body content replaces it wholesale — to ADD to existing content, read it first with get_task and resend it with your additions.
