Connect Breeze to an AI assistant such as Claude or ChatGPT and run your projects by chatting. You can ask about your work and make changes - create tasks, move them, log time, leave comments - without leaving the conversation.
This works through MCP (the Model Context Protocol), an open standard for connecting AI assistants to apps like Breeze. There's nothing technical to set up: you add Breeze once in your assistant, sign in, and start typing. For what the Breeze MCP server is and how it compares to other ways of connecting, see the overview.
Looking for the AI built into Breeze instead? That's Breeze AI, which answers questions inside the app without connecting anything.
A few things you can ask:
The first three look things up. The rest make changes - which the assistant can now do for you. When this first launched it could only read your data and answer questions; it can now also create, update, and delete things on your behalf.
Connecting an assistant sends it the Breeze data you ask about - task names and descriptions, comments, time entries, and the names and email addresses of teammates you can already see. Once it reaches the assistant, that content is held by the assistant's provider (OpenAI for ChatGPT, Anthropic for Claude) under their privacy policy, so it is worth reading theirs before you connect, and granting view-only access if you don't need changes.
On the Breeze side: we log connector requests for 14 days for security and troubleshooting, we never use anything reached through the connector to train AI models, and searching by meaning runs on our own servers rather than going to an outside AI provider. The full detail - what each kind of request sends, what comes back, and what we keep - is in the privacy policy.
Add Breeze inside your AI assistant using this address: mcp.breeze.pm/mcp
Availability depends on your ChatGPT plan.
Any assistant that supports MCP connectors works the same way - add a custom connector with the address mcp.breeze.pm/mcp and sign in with Breeze. Setup takes about a minute and is a one-time thing.
Three things worth knowing about, because they work a little differently from everything else.
Say who you want to mention in plain language and the assistant works out who you mean - by first name, full name, or email address. You never type an @ yourself, and you never need to know anyone's ID.
The @name is written into the text for you, and the person gets the same in-app notification, browser push and email they would from a colleague's mention. It is not decorative, so "mention everyone" on a large project really does reach everyone.
You can mention people in task comments, in a task's description, in a project's discussion and in project notes. Only people who are on the project can be mentioned, and a note mention only reaches people who can see the project's notes. Guests invited to a single task can be mentioned in a comment if you name them specifically, but never through "everyone" or "the assignees".
There are two different things here, and they are deliberately separate.
A dependency is real scheduling information. Say "make the deploy task depend on the database migration" and the task shows "This task depends on", the other side shows "Tasks that depend on this task", and the Gantt chart draws an arrow between them. You can ask what something is blocked by, and ask for a link to be removed. The project needs task dependencies switched on in its settings; the assistant will tell you if it isn't.
A reference is just a link in the text. Say "comment on the deploy task and reference the migration task" and you get a clickable #412 link inside the comment. No dependency is created and nothing changes in the Gantt chart. This matters: if writing a task number in a comment created a dependency, an assistant mentioning a ticket in passing would quietly rearrange your schedule.
You can attach a file to a task or a comment, and choose whether it sits in the task's Files tab or inside the description or comment text, the way an image sits in a document.
Attaching a link to a file that already lives somewhere else - Google Drive, Figma, Dropbox - always works and needs nothing special.
Uploading an actual file needs an assistant that can send one. Claude Desktop and Claude Code can upload a file you point at, and can handle an image you drag into the conversation. A chat-only assistant such as ChatGPT on the web cannot upload files, so attach a link instead, or upload it in Breeze directly.
If an upload does not work, in order: point the assistant at the file, paste a public link, or upload it in Breeze itself. Uploaded images get a thumbnail automatically, which can appear a second or two after the file. If an assistant ever attaches the wrong file after you dropped an image into the chat, tell it the exact filename - it should ask when it is unsure rather than guess.
Custom fields. The assistant can set your custom fields when it creates or updates a task - "set Billing to Retainer and Time code to DEP-7" - by the field's name. It checks every value first: a dropdown only takes one of its options, a number field a number and a date field a date, so a value Breeze would not accept is refused before anything is saved rather than stored wrong. Changes show in the task's activity like any other edit. Setting a field leaves the task's other fields as they are, and you can ask for a field to be cleared. Creating or renaming the fields themselves stays in Breeze's settings.
Swimlanes. Swimlanes - the rows across your board - can be added, renamed, reordered and deleted, and tasks can be created in, moved to or copied into a swimlane.
Copying tasks. "Copy the Acme deployment task into Next week, in the new swimlane" makes a copy like Breeze's own Copy does: the description, custom fields, tags, assignees, dates, status and checklists (with ticked items still ticked) come along, and you can give the copy a new name or different custom field values as part of the same request. Comments, files, logged time, estimates and dependencies are not copied, so the copy starts with a clean history and no time counted twice. Copies go within the same project, and an archived task can be copied back onto the board.
You never call these by name - you just chat naturally, and the assistant picks the right one for what you asked. Below is the full set of underlying tools, grouped by area, with their exact technical names and an example of the kind of thing you'd say to trigger each.
| Tool | Description | Example usage |
|---|---|---|
| breeze_get_me | See who you're signed in as and what you can access | Who am I signed in as, and what can I access? |
| breeze_list_workspaces | List your workspaces | What workspaces do I have? |
| breeze_list_team_members | See who's on your team, to assign work | Who's on my team? |
| Tool | Description | Example usage |
|---|---|---|
| breeze_list_projects | List the projects you can access | Show me all my projects. |
| breeze_get_project | Open a project's lists, swimlanes, members, statuses and custom fields | What custom fields does the Website Redesign project have? |
| breeze_get_project_stats | See done vs. open, workload by person, and what's due soon | How is the Website Redesign project going? |
| breeze_create_projects | Create new projects | Create a project called Q4 Launch. |
| breeze_update_project | Change a project's name, budget and dates | Set the Q4 Launch deadline to August 30. |
| breeze_add_project_members | Give teammates access to a project | Add Sarah to the Marketing project. |
| breeze_delete_project | Remove a whole project - can be restored | Archive the old 2024 Campaign project. |
| breeze_restore_projects | Bring back a deleted project | Bring back the project I just deleted. |
| Tool | Description | Example usage |
|---|---|---|
| breeze_create_stages | Add lists/columns to a board | Add a "Review" column to the board. |
| breeze_update_stage | Rename a list/column or change its order | Rename "To do" to "Backlog" and move it first. |
| breeze_delete_stages | Archive a list/column and its tasks - can be restored | Remove the "On hold" column. |
| breeze_restore_stages | Bring back an archived list/column | Bring back the "On hold" column. |
| Tool | Description | Example usage |
|---|---|---|
| breeze_create_swimlanes | Add swimlanes (rows) to a board | Add a swimlane called "Deployment - Week of Oct 13th". |
| breeze_update_swimlane | Rename a swimlane or change its order | Rename the "Backend" swimlane to "API" and move it to the top. |
| breeze_delete_swimlanes | Permanently delete swimlanes - their tasks are kept and move to the default row | Delete last month's deployment swimlanes. |
| Tool | Description | Example usage |
|---|---|---|
| breeze_list_cards | List and filter tasks by list, assignee, due date and more | Show tasks due this week in Marketing. |
| breeze_get_card | Open one task with all its details | Open the homepage redesign task. |
| breeze_list_my_cards | See the tasks assigned to you | What am I working on right now? |
| breeze_create_cards | Add tasks to a project, with their custom field values | Add three tasks to the Marketing project and assign them to me. |
| breeze_update_cards | Change task details and custom fields, or move tasks between lists and swimlanes | Move the homepage task to Done and set Billing to Retainer. |
| breeze_copy_cards | Copy tasks into a list and swimlane, with their description, custom fields, tags, assignees and checklists | Copy each client's deployment task into this week's swimlane. |
| breeze_delete_cards | Archive tasks off the board - can be restored | Archive the finished onboarding task. |
| breeze_restore_cards | Bring archived tasks back | Restore the task I archived. |
| breeze_link_cards | Record that one task depends on others | Make the deploy task depend on the migration. |
| breeze_unlink_cards | Remove a dependency between tasks | Remove the link between those two tasks. |
| Tool | Description | Example usage |
|---|---|---|
| breeze_list_todos | List checklist items across tasks and projects | What checklist items are left on this task? |
| breeze_create_todo_lists | Add checklists to a task | Add a "Pre-launch" checklist to this task. |
| breeze_create_todos | Add items to a task's checklist | Add "proofread copy" and "check links" to the checklist. |
| breeze_update_todos | Rename, complete, or set due dates on checklist items | Mark "proofread copy" as done. |
| breeze_update_todo_list | Rename a checklist | Rename the checklist to "Launch day". |
| breeze_delete_todos | Permanently delete checklist items | Remove the "check links" item. |
| breeze_delete_todo_lists | Permanently delete checklists and their items | Delete the whole "Pre-launch" checklist. |
| Tool | Description | Example usage |
|---|---|---|
| breeze_list_comments | List comments on a task or across a project | What have people said on this task? |
| breeze_create_comments | Comment on a task | Comment "looks good, shipping today" on the homepage task. |
| breeze_update_comment | Edit a comment | Fix the typo in my last comment. |
| breeze_delete_comments | Permanently delete comments | Delete my comment on that task. |
| breeze_list_project_messages | Read a project's discussion messages | Show the discussion in the Marketing project. |
| breeze_create_project_messages | Post in a project's discussion | Post a status update in the Marketing project discussion. |
| breeze_update_project_message | Edit a discussion message | Edit my last project update. |
| breeze_delete_project_messages | Permanently delete discussion messages | Delete that discussion post. |
| Tool | Description | Example usage |
|---|---|---|
| breeze_list_notes | List a project's notes | What notes does the Marketing project have? |
| breeze_get_note | Read a note in full | Read me the release checklist note. |
| breeze_create_notes | Add notes to a project | Save these meeting notes as a note in Q4 Launch and mention Sarah. |
| breeze_update_note | Rename a note or replace its text | Add today's decisions to the release checklist note. |
| Tool | Description | Example usage |
|---|---|---|
| breeze_list_time_entries | See logged time | How much time did I log this week? |
| breeze_log_time | Record time worked on a task | Log 2 hours on the homepage task for today. |
| breeze_update_time_entry | Change a logged time entry | Change that time entry to 3 hours. |
| breeze_delete_time_entries | Permanently delete logged time | Delete the time I logged by mistake. |
| breeze_set_estimates | Add time estimates to a task | Estimate the homepage task at 5 hours. |
| breeze_update_estimate | Change a time estimate | Bump the estimate to 8 hours. |
| breeze_delete_estimates | Permanently delete estimates | Remove the estimate on this task. |
| Tool | Description | Example usage |
|---|---|---|
| breeze_get_upload_url | Get a secure, short-lived link to upload a file | Attach the brief on my Desktop to this task. |
| breeze_attach_files | Attach an uploaded file or a public link, in the Files tab or inside the text | Put this screenshot in the task description. |
| breeze_get_download_url | Get a short-lived link to read a file back | What does the attached CSV say? |
| Tool | Description | Example usage |
|---|---|---|
| breeze_search | Find tasks, comments, projects and more by keyword | Find every task that mentions "invoice". |
| breeze_semantic_search | Find things by meaning, even with vague wording | Find that task about the login bug, whatever it was called. |
| breeze_list_activity | See what changed and when | What changed in Marketing this week? |
| breeze_list_tags | See a project's tags | What tags does this project use? |