Productivity & Project Management · Breeze + Claude
Breeze MCP with Claude: Plan, Track and Update Projects Through Natural Language
The short answer
Claude works with Breeze through the Model Context Protocol (MCP), an open standard that gives Claude secure, permissioned access to the tool. Once connected with an API key, Claude can create projects, assign and update tasks, fetch team progress and manage deadlines from natural language instructions, with approvals kept in place.
What is Breeze?
Breeze is a project management platform that helps teams plan, track and collaborate on their work. It streamlines workflows and keeps everyone aligned on priorities, owners and due dates. Project managers, team leads, operations staff and department heads typically use it to run projects from kickoff through delivery. Because it holds the live state of tasks and deadlines, it is a valuable source of information for automation.
How Claude connects to Breeze through MCP
The Model Context Protocol is an open standard that lets Claude securely use other software, reading information and taking actions with permissions the organisation controls. Think of it as a universal adapter between Claude and the tool. For Breeze, the connection can be made through an MCP server or a direct API, using an API key for sign-in.
Once connected, Claude can typically read project status, task lists, owners and deadlines, and summarise progress across teams. It can also take actions such as creating a project, assigning a task, updating a status or adjusting a due date when someone asks for it in plain language.
Permissions and approvals keep people in charge. The API key is scoped to the access the organisation chooses, following least-privilege principles. Consequential changes, such as moving deadlines for a client project, can require a named person to approve before Claude acts, and every action is recorded in an audit log.
What you can automate
Weekly progress summaries for leaders
A department head asks Claude for a summary of every active project and its status. Claude reads task progress from Breeze and produces a short briefing listing what is on track, what is slipping and which items need a decision. Leaders get a clear view without opening each project board.
Turning meeting notes into tasks
After a project meeting, a team lead pastes the notes into Claude. Claude identifies the action items, creates matching tasks in Breeze, assigns owners and sets due dates. The team starts work the same day, and nothing discussed in the meeting is lost.
Deadline risk monitoring
Each morning, a project manager asks Claude to review upcoming deadlines. Claude flags tasks that are overdue or unlikely to finish on time, based on current progress, and suggests which owners should be contacted. The manager decides what to change and approves any date updates.
Onboarding new projects quickly
When a new client is signed, an operations coordinator describes the scope in plain language. Claude creates the project in Breeze with its standard phases and starter tasks, adjusted to the scope. This saves hours of manual setup and keeps every project structured in the same way.
Workload checks across teams
Before allocating new work, a resource planner asks Claude how tasks are spread across team members. Claude fetches current assignments and highlights who is overloaded and who has capacity, helping managers balance work before problems appear.
An end-to-end workflow: Client project kickoff to weekly reporting
TriggerA signed client contract is saved in the company's document system and logged in the CRM.
Claude reads the contract summary and the scope recorded in the CRM.
Claude creates a new project in Breeze with phases and starter tasks matching the agreed scope.
Claude assigns owners based on the team roster and sets due dates from the agreed timeline.
A project manager reviews and approves the plan before the team is notified.
Each week, Claude fetches task progress from Breeze and drafts a status update for the client.
The account manager reviews the draft in Microsoft 365 and sends it after approval.
OutcomeProjects start with a complete, consistent plan within the same day of signing, and clients receive accurate weekly updates without manual reporting work. Typical outcomes depend on how well the scope and team data are maintained.
How we set it up
Free automation audit
We review how your teams currently use Breeze, where updates are repeated and which workflows are worth automating. You leave with a clear list of priorities and an estimate of effort.
Connection through API key
We set up the connection to Breeze using an API key, either through an MCP server or a direct API, scoped to least-privilege access. Credentials are stored securely and never shared in chat.
Workflow design
We design the end-to-end workflow across Breeze and your other systems such as Microsoft 365, CRM or ticketing. People approve consequential actions, and we agree the rules together.
Testing and launch
We test the workflow against real past projects and tasks, then launch with monitoring and audit logs turned on. Any issues found in testing are fixed before your teams rely on it.
Team training
We train project managers, team leads and leaders on how to use Claude with Breeze, including how to review approvals and read the audit trail. Support is available as your workflows grow.
Who benefits
- Project managers
- Spend less time on status updates and task admin, and more time resolving blockers.
- Team leads
- Turn meeting outcomes into tracked tasks quickly, with clear owners and dates.
- Department heads
- Get a clear, current picture of progress across several projects without manual reporting.
- Operations coordinators
- Set up new projects consistently and faster, with fewer errors in dates and assignments.
Security and control
- Access uses an API key scoped to least-privilege permissions, limited to what the workflow needs.
- Consequential changes such as deadline shifts or reassignments can require named human approval before Claude acts.
- Every action Claude takes is recorded in an audit log that your team can review.
- Credentials are stored securely and rotated on a schedule your organisation sets.
- We test each workflow against real cases before launch and monitor it afterwards.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can set up Breeze workflows with access controls and audit trails aligned to their internal policies. Companies in India must consider the Digital Personal Data Protection Act, 2023, when project data includes personal details. Organisations in the UAE and Saudi Arabia must follow their local data protection laws. We choose the hosting region for your Claude workflows to meet these requirements, though compliance depends on your own policies and advice.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Breeze MCP server do?
The Breeze MCP server acts as a secure bridge between Claude and your Breeze account. It lets Claude read project and task information and carry out permitted actions, such as creating projects or updating tasks. The server uses the access you approve, so Claude only sees and changes what your workflow requires.
Is connecting Claude to Breeze secure?
Security depends on the setup. We use an API key with least-privilege access, store it securely, and keep audit logs of every action. Consequential changes can require human approval. We also test the connection and monitor it after launch so issues are caught early.
What can Claude do with Breeze once connected?
Typically Claude can create projects, assign and update tasks, fetch team progress and manage deadlines when asked in natural language. It can also summarise status across projects. The exact actions available depend on the access granted and what your workflow is designed to allow.
How long does setup take?
Many organisations complete a first working workflow within a few weeks, though this varies with the number of workflows and the state of your project data. The free automation audit gives a clearer estimate for your team before any work begins.
Which plan or permissions do I need?
Generally, you need a Breeze account with permission to generate an API key and access the projects you want automated. The exact plan requirements depend on your Breeze subscription, so please confirm your account level during the free audit.