That is the admin around your work, and it is the part everyone puts off. It is also the part that is easiest to describe in a sentence and slowest to click through. Connect Breeze to the AI assistant you already use, and you can hand it over.
There is nothing to learn and no commands to remember. Paste your meeting notes and say "turn these into tasks in Q4 Launch and assign the owners we named". Or say "log 2 hours on the homepage task, move it to Review, and comment that the copy needs sign-off". Your assistant reads your board, does the work, and tells you what it did. It handles tasks, checklists, comments, time, estimates, and whole projects with their columns and people. The full list of what it can do is in our help pages.
Breeze enforces all of this, not the assistant, so there is nothing for it to talk its way around.
| Breeze MCP server | Other connectors | ||
|---|---|---|---|
| Covers all of Breeze | Other connectors for Breeze, like Zapier's and Composio's, cover a slice of it | ||
| Sign in with your Breeze login | Nothing to copy out of Breeze and paste into someone else's platform | ||
| Choose view-only or view plus changes | You decide what the assistant is allowed to do when you connect it | ||
| Connects straight to Breeze | Nothing routed through a third company in between | ||
| Finds things by meaning, not just keywords | Ask for the card about the login bug without remembering its title | ||
| Previews bulk and destructive changes | Nothing is written until you say go, and most of it can be restored | ||
| Included in your Breeze plan | No per-action AI billing, and no second subscription to route through |
Zapier and Composio both run their own MCP connectors for Breeze, and they are a reasonable choice if you already build multi-app workflows in those platforms. For working with Breeze directly from Claude or ChatGPT, the official server is the more complete option.
Breeze has single-handedly transformed the way our company interacts and communicates between teams ...
It has allowed us to do what we love the most and that is to effectively and efficiently help our clients ...
This platform is that perfect mixture for teams wanting to have everything they need and nothing they don't. I would recommend this tool to any team, big or small.
MCP is the Model Context Protocol, an open standard for connecting AI assistants to the apps you already use. An MCP server exposes one app's data and actions to any assistant that speaks the standard. Breeze runs one, so Claude, ChatGPT or Cursor can work with your projects and tasks without anyone building a custom integration.
Yes. The official Breeze MCP server runs at mcp.breeze.pm/mcp. It is remote and authenticated with OAuth, so there is nothing to install or host. It gives an assistant 48 tools: 17 for reading and searching, 31 for making changes.
Breeze AI is built into Breeze and answers questions about your work inside the app. The MCP server is how an outside assistant like Claude or ChatGPT connects in and does the work with you. One is ours, one is yours, and they work independently of each other.
No. It is a remote server, so there is nothing to install, host or configure. You paste one address into your assistant's connector settings, sign in with your normal Breeze login, and choose whether it gets view-only access or view plus the ability to make changes. The step-by-step setup for Claude, ChatGPT and other assistants takes about a minute.
No. It is part of your Breeze plan and Breeze does not charge per AI action. You pay for your AI assistant separately, directly to whoever makes it.
No. It signs in as you and follows the same visibility rules as the Breeze app: your team, your projects, your role. Anything hidden from you in Breeze stays hidden here, and it cannot reach other teams or any project you do not have access to.
It can read everything you can see, but a few things stay hands-on: attachments, custom fields, statuses, swimlanes, and creating new tags. It also cannot do anything your role does not allow. Observers can look but not change, and creating projects, changing board columns or adding people needs a team owner or admin.
Yes, deliberately. It handles up to 25 items in one go, and 10 when something is being deleted for good. An oversized request is refused rather than quietly trimmed, so nothing goes missing. There is also an hourly ceiling on how much one person's assistant can change, and a limit on repeating the same action over and over, so an assistant stuck in a loop stops early instead of rewriting your board.
Yes, and it is the safer place to start. When you connect, you choose between view-only access and view plus making changes. You can reconnect later to change your mind.
Use the official Breeze MCP server if you want an assistant like Claude or ChatGPT to work with Breeze directly. Use Zapier if you already build multi-step automations there that connect several apps together. Use the Breeze API if you have a developer building something custom. The official server covers the most of Breeze, and it is the only one you sign into with your normal Breeze login.
Because you already pay for an AI assistant, and it is probably better than one we could bundle. Through 2025 and 2026 most work management tools repositioned around their own agents and moved toward charging per AI action. Breeze went the other way: it stays simple and connects to the assistant you already have, over an open standard, with no per-action AI billing and no agent builder to configure. It also means you are not locked into our judgement about which model is good.
Bulk changes and every deletion are previewed and wait for your go-ahead before anything happens. Tasks, board columns and projects are archived rather than deleted, so they can be restored. Every change also lands in the project activity feed under your name, so you can see exactly what happened.