Breeze

Add one or more swimlanes to a project's board. A swimlane is a horizontal board row, also called a row, lane, band, track, stream or workstream; a list or column is a stage. Pass project_id and a `names` array; swimlanes are added at the bottom of the board in the order given (move one with breeze_update_swimlane). Up to 25 per call. Adding more than one is two-step: call once to preview, then again with confirm: true. Needs the 'write' scope; any project member but an observer can change a project's swimlanes.

breeze_create_swimlanes

Add one or more to-dos (checklist items) to a card. Pass card_id and a `todos` array; each item takes a name and optionally todo_list_id (the checklist to put it in, from breeze_get_card; without one it goes in the card's top checklist) and a duedate (ISO8601). A to-do has to be in a checklist, so on a card with none, create one first with breeze_create_todo_lists. Up to 25 per call — to add more, call again with the next batch. Adding more than one is two-step: call once to preview, then again with confirm: true. Needs the 'write' scope; observers cannot edit cards.

breeze_create_todos

Delete one or more to-do lists (checklists) AND all their items — PERMANENT, this CANNOT be undone. Pass a `todo_list_ids` array (up to 10). ALWAYS two-step, even for a single list: call once to preview the item counts, then again with confirm: true. Needs the 'write' scope; observers can only edit checklists if allowed.

breeze_delete_todo_lists

Delete one or more comments — PERMANENT, comments have no recycle bin and this CANNOT be undone. Pass a `comment_ids` array (up to 10). ALWAYS two-step, even for a single comment: call once to preview, then again with confirm: true. You can only delete your own comments, or, as a team owner/admin, comments by people in your team. Needs the 'write' scope.

breeze_delete_comments

Delete one or more estimates — PERMANENT, this CANNOT be undone. Card planned time and project total planned are recomputed. Pass an `estimate_ids` array (up to 10). ALWAYS two-step, even for a single estimate: call once to preview, then again with confirm: true. You can only delete your own estimates unless you're a team owner/admin and the project is your team's. Needs the 'write' scope and estimate permission.

breeze_delete_estimates

Delete a whole project — it and all its cards are removed from view, but it can be brought back later with breeze_restore_projects. ONE project per call (deleting a project cascades its entire contents, so it is deliberately not a bulk operation). Two-step: call once to preview (shows the card count), then again with confirm: true. Needs the 'write' scope; only a team owner or admin, or the project's owner with archive rights, can delete a project.

breeze_delete_project

Delete one or more project discussion messages — PERMANENT, this CANNOT be undone. Pass a `message_ids` array (up to 10). ALWAYS two-step, even for a single message: call once to preview, then again with confirm: true. You can only delete only your own messages, whatever your role. Needs the 'write' scope.

breeze_delete_project_messages

Delete one or more swimlanes — PERMANENT: Breeze has no swimlane archive, so a deleted swimlane cannot be brought back. A swimlane is a horizontal board row, also called a row, lane, band, track, stream or workstream; a list or column is a stage. No card is deleted: the cards in it move to the board's default row, in the same lists. Pass a `swimlane_ids` array (up to 10). ALWAYS two-step, even for one swimlane: call once to preview how many cards will move, then again with confirm: true. To archive the cards as well, archive them first with breeze_delete_cards. Needs the 'write' scope; any project member but an observer can change a project's swimlanes.

breeze_delete_swimlanes

Delete one or more logged time entries — PERMANENT, this CANNOT be undone. Card and project tracked totals are recomputed. Pass an `entry_ids` array (up to 10). ALWAYS two-step, even for a single entry: call once to preview, then again with confirm: true. You can only delete your own entries unless you're a team owner/admin and the project is your team's. Needs the 'write' scope and time-tracking permission.

breeze_delete_time_entries

Delete one or more to-dos (checklist items) — PERMANENT, there is no recycle bin and this CANNOT be undone. Pass a `todo_ids` array (up to 10). ALWAYS two-step, even for a single item: call once to preview, then again with confirm: true. Needs the 'write' scope; observers can only delete todos if allowed.

breeze_delete_todos

Edit a comment's text. Pass comment_id and the new body. Adding `mentions` here notifies those people, so you can @mention someone on a comment you already posted. `card_refs` links to other tasks inside the text. ALWAYS build the new body from the comment's `body_html` (breeze_list_comments returns it) rather than its `body`, which is a lossy plain-text rendering — editing from `body` strips formatting and REMOVES any inline images/files. You can only edit your own comments unless you're a team owner/admin. Needs the 'write' scope.

breeze_update_comment

Edit a project discussion message. Pass message_id (from breeze_list_project_messages) and the new body. Adding `mentions` notifies those people, so you can @mention someone on a message you already posted. You can only edit only your own messages, whatever your role. Needs the 'write' scope.

breeze_update_project_message

Return a short-lived download link for a file attached to a task, so you can fetch and read it yourself (e.g. with curl). Pass the attachment_id from breeze_get_card or breeze_search. Link attachments (files stored elsewhere, like Drive or Dropbox) return their own URL unchanged. The link expires in 15 minutes. Read-only: nothing is changed.

breeze_get_download_url

STEP 1 OF 2 for putting a file on a task. Returns a short-lived upload link for ONE file; you then upload the bytes yourself (a normal multipart POST — e.g. curl -F with each returned field, then -F file=@<path>), and finally call breeze_attach_files with the returned `key` to attach it. Nothing is attached until step 2, and this call creates nothing. The link expires in 15 minutes. Works for any file type: images, PDFs, zips. Needs the 'write' scope. BEFORE CALLING, CHECK YOU CAN ACTUALLY READ THE FILE. This flow needs (a) the file on disk at a path you know, and (b) the ability to run a command. File bytes never travel through these tools, so if you cannot run a shell command, you cannot attach an uploaded file at all. AN IMAGE PASTED OR DROPPED INTO THE CHAT COMES WITH NO PATH. A screenshot you were shown, a drag-and-dropped image, or output from another tool reaches you as pixels, not as a file, and no filename is supplied. Never invent one. In that situation, in order: 1. Get it onto disk if you can, from EITHER of two places, and check both before choosing: (a) the conversation itself — some clients persist pasted images where you can read and decode them (Claude Code keeps them in its session transcript under ~/.claude/projects/); (b) the original file, which a dropped image usually still has wherever the user dragged it from, and a screenshot usually has in ~/Desktop or ~/Downloads. PREFER THE ORIGINAL ON DISK. Clients routinely DOWNSCALE AND RE-ENCODE what they store in the conversation — a paste that reaches you as a 2000px lossy WebP can be a 2754px PNG on disk — so the transcript copy is a degraded derivative, not the file the user means. When you have both, compare dimensions and take the larger; use the transcript copy when no original exists. Matching an on-disk file to a paste is INFERENCE, not knowledge: a recent file whose image matches is a strong candidate, but size alone is not, and the transcript copy will NOT be byte-identical to it. CONFIRM with the user before uploading a file you matched rather than were given. 2. Otherwise ask. Request the path, or a public URL to attach as a link with breeze_attach_files `url`. NEVER upload a different file as a stand-in. Attaching the wrong image is worse than attaching nothing, because the user will not notice the swap. A file that already has a public URL (Drive, Figma, Dropbox) never needs this tool — call breeze_attach_files with `url` instead.

breeze_get_upload_url

Get full details of a single card (task): description, assignees, start/due dates, status, tags, time tracked, planned time, custom fields, attachments, and comment count.

breeze_get_card

Get the current authenticated Breeze user: identity, team, role, permission flags, and how many projects they can access. Call this first to learn who you are acting as.

breeze_get_me

Read one project note in full: its name and its body (`description`, as the HTML Breeze stores). Note ids come from breeze_list_notes or breeze_search.

breeze_get_note

Get full details of a project the user can access: stages (board columns, ordered), swimlanes (board rows, ordered; empty when the board has none), members, available statuses, custom fields (id, name, type and, for a dropdown, its options — the values breeze_create_cards / breeze_update_cards / breeze_copy_cards accept), and time/plan totals.

breeze_get_project

Project overview stats: total cards, done vs open (done = carrying the project's completed status, as Breeze counts it), card counts by stage / status / assignee, due-date buckets (overdue / today / upcoming / none), and time totals (tracked / planned, shown only if you have time-tracking / estimate permission).

breeze_get_project_stats

Record that one task DEPENDS ON one or more other tasks. The card shows these as 'This task depends on', and the dependent tasks show 'Tasks that depend on this task'; the Gantt chart draws them as arrows. Pass card_id (the task that is blocked) and depends_on_ids (the tasks it waits for) — up to 25 per call. All tasks must be in projects you can access, and the card's project must have task dependencies enabled. Linking more than one is two-step: call once to preview, then again with confirm: true. To reference a task inside a comment or description instead of creating a dependency, use the card_refs option on the comment/card tools. Needs the 'write' scope; observers cannot link tasks.

breeze_link_cards

Activity / audit feed (newest first). Pass card_id for a single card's full history, or project_ids (or omit for all accessible projects) for a project-wide feed, optionally filtered by user_ids. Filter the event kind with action_types (the verb: create/update/move/destroy/delete/reactivate — pass ["create"] for CREATION events) and/or actions (the subject: comment/name/todo/member/tag/stage/cardstatus/duedate/startdate/desc/tracked_time/planned_time/card_attach/note/custom_field/...). Returns structured entries — action, action_type, who, which card, when, and stripped text/old_text — for you to narrate. Filter the window with created_after/created_before (e.g. 'what changed this week').

breeze_list_activity

List/count cards (tasks). Pass project_id for one project, or OMIT it to query ALL accessible projects. Natural shortcuts: due (overdue/today/this_week/upcoming/none, timezone-aware) and unassigned — prefer these over computing dates yourself. Other filters: card_ids (several known cards in one call), stage_id, assignee_id, status_id, done, tags, swimlane_id, custom_fields, and explicit ranges for due / start / created / updated. stage_id/status_id/assignee_id are numeric ids — resolve names first via breeze_get_project (stages, statuses) or breeze_list_team_members (people). Returns compact card summaries (incl. created_at/updated_at) with a total count. Paginated. (For keyword text matching use breeze_search; for fuzzy/meaning use breeze_semantic_search.)

breeze_list_cards

List/count comments. With card_id: that one card's full thread — archive-aware (works for archived cards) and oldest-first, the natural reading order. Without card_id: a cross-card feed (newest first) over active cards — answers 'comments created today', 'comments by user X', 'comments in project Y today'. Pass project_id to scope the feed to one project, or omit both for all accessible projects. Filters: author_id and date ranges for created / updated. `body` is plain text; pass include_html: true to also get each comment's `body_html`, which you need ONLY when you intend to edit one (it is several times larger, so leave it off for reading). Paginated.

breeze_list_comments

List cards assigned to the current user across all accessible projects ('my tasks'). Filter by done flag and/or due bucket (overdue/today/this_week/upcoming/none) — e.g. due:'overdue' for 'my overdue tasks'. Sorted by due date.

breeze_list_my_cards

List a project's notes (its Notes panel), newest first: id, name, dates and the start of each note's text. Read one in full with breeze_get_note.

breeze_list_notes

List messages in a project's discussion (the project chat room, separate from card comments). Pass project_id. Newest first, paginated. Use the returned message ids with breeze_update_project_message.

breeze_list_project_messages

List projects the current user can access. Optionally filter by workspace. Returns id, name, slug, workspace, color, and card count. Paginated.

breeze_list_projects

List tags (with card counts) for a project, or across all accessible projects if project_id is omitted. Returns id, name, color, project_id, cards_count. Tags are per-project.

breeze_list_tags

List users the current user can see (their team, or co-members of their projects), plus the team's user groups. Use to resolve names to user ids for assignees and for @mentions. A group is mentioned by its `mention_id` — pass that in the `mentions` option of the comment, card or message tools.

breeze_list_team_members

List logged time entries, filtered by project, card, user, and date range (either end may be left open). Paged: when next_offset is set, call again with it as offset to get the rest. Requires time-tracking permission.

breeze_list_time_entries

List/count to-do (checklist) items as first-class objects, across cards and projects — the way to answer questions like 'todos created this week' or 'todos assigned to X'. Pass project_id for one project, card_id for one card, or OMIT both to query ALL accessible projects. Filters: assignee_id (the todo's own assignee), unassigned, done, todo_list_id, and date ranges for created / updated / due / start. Each todo carries its list name, parent card, assignee_ids and timestamps. Paginated, newest-first. (To read one card's checklist grouped by list, use breeze_get_card instead.)

breeze_list_todos

List the workspaces in the current user's team. Workspaces group projects. You see the workspaces holding projects you are a member of; an admin also sees workspaces with no projects.

breeze_list_workspaces

Log one or more time entries on a card, in MINUTES. Pass card_id and an `entries` array; each entry takes minutes and optionally logged_date (ISO8601, defaults to today), notbillable, and a desc — so a week of work can be logged in one call. Updates the card's and project's tracked totals automatically. Up to 25 per call. Logging more than one is two-step: call once to preview, then again with confirm: true. Needs the 'write' scope and time-tracking permission.

breeze_log_time

Post one or more comments on a card. Pass card_id and a `bodies` array (HTML is allowed; plain text is wrapped as-is). Use `mentions` to @mention people — they are notified in Breeze, by push and by email, exactly as if a person had mentioned them; the @names are added to the text for you. Use `card_refs` to link to other tasks inside the comment. Everyone subscribed to the card or its list is notified either way. Up to 25 per call. Posting more than one is two-step: call once to preview, then again with confirm: true. Needs the 'write' scope; any project member may comment, observers included.

breeze_create_comments

Post one or more messages in a project's discussion (the project chat room, separate from card comments). Pass project_id and a `bodies` array. The room is created on first use. Use `mentions` to @mention people — they are notified in Breeze and by push. In a discussion room, "all" means everyone in the room and mentions are limited to room participants; there is no "task" option here. Up to 25 per call. Posting more than one is two-step: call once to preview, then again with confirm: true. Needs the 'write' scope; observers cannot post.

breeze_create_project_messages

Remove the dependency link between one task and one or more others, in whichever direction it was created. Pass card_id and unlink_ids (up to 10). This only removes the link — no task is deleted. Two-step at ANY count: call once to preview, then again with confirm: true. Needs the 'write' scope; observers cannot change links.

breeze_unlink_cards

Rename a to-do list (checklist group). Pass todo_list_id and the new name. Needs the 'write' scope; observers cannot edit cards.

breeze_update_todo_list

Rename or reorder a stage (list/column). Pass stage_id plus name and/or position (1-based left-to-right). Needs the 'write' scope; any project member but an observer can change a project's lists.

breeze_update_stage

Rename or reorder a swimlane. A swimlane is a horizontal board row, also called a row, lane, band, track, stream or workstream; a list or column is a stage. Pass swimlane_id (from breeze_get_project) plus name and/or position (1-based, top to bottom). Needs the 'write' scope; any project member but an observer can change a project's swimlanes.

breeze_update_swimlane

Bring one or more archived cards back onto the board (undo breeze_delete_cards), along with their list if that was archived too. Pass a `card_ids` array (up to 25). Find archived card ids with breeze_search (only_archived: true). No confirmation needed — restoring only adds things back. Needs the 'write' scope; only a team owner/admin or a project admin with archive rights.

breeze_restore_cards