Breeze

@Breeze show me all cards assigned to me that are due this week across all my projects

Here are your cards due this week: **Project: Q1 Marketing Campaign** - "Finalize ad copy" (due Jan 18, Stage: In Review) - "Schedule social posts" (due Jan 19, Stage: To Do) **Project: Website Redesign** - "Review wireframes" (due Jan 20, Stage: In Progress) All three cards are currently assigned to you. The Marketing Campaign project has 2 other team members, and Website Redesign has 4. This is an illustrative example based on typical Breeze project structures.

This example demonstrates Breeze's read capabilities for personal task tracking. Requires API key with read access to all projects where you're a member. Response shape varies by your actual project memberships and card states. Breeze organizes work by projects and stages (lists), so cross-project queries return grouped results.

@Breeze create a new card called "Draft Q2 budget proposal" in the Finance Planning project, assign it to sarah@company.com, and set the due date for February 1st

Card created successfully in **Finance Planning** project: **Card Details:** - Name: "Draft Q2 budget proposal" - Assigned to: Sarah Chen (sarah@company.com) - Due date: February 1, 2024 - Stage: To Do (default list) - Card ID: #8472 Sarah will receive a notification about this assignment. You can move this card to a different stage or add additional details like description, tags, or attachments through Breeze's interface. This is an illustrative example of a successful card creation.

This example shows Breeze's task creation workflow. Requires write permissions and a valid project ID (the MCP resolves project names to IDs). If the assignee email isn't already in the project, you'll need to use the "Add Project People" tool first. Card creation triggers email notifications to assignees by default.

@Breeze look at all overdue cards in the Product Launch project and draft a status update email summarizing what's blocking us

I found 5 overdue cards in **Product Launch**: **Blocking items:** - "API integration testing" (7 days overdue, assigned to Dev Team, Stage: In Progress) - "Legal review of terms" (3 days overdue, assigned to Legal, Stage: Waiting) - "Finalize pricing tiers" (2 days overdue, unassigned, Stage: To Do) **Draft status update:** Team — we have 5 overdue items in Product Launch that need immediate attention. The API integration testing is our biggest blocker at 7 days overdue. Legal review is waiting on external counsel (3 days). We also need to assign and complete the pricing tiers work before we can proceed with marketing materials. Recommend a sync today to unblock Legal and reassign the pricing task. This is an illustrative synthesis based on typical project states.

This example combines Breeze's data retrieval with AI reasoning to create actionable summaries. The MCP fetches card metadata (status, assignees, due dates), and the AI interprets patterns to identify blockers. Useful for standups or stakeholder updates. Note that Breeze doesn't track time-in-stage or velocity metrics natively, so deeper project health analysis requires manual interpretation.

When Breeze wins for fast project access grants

A 6-person agency brings on two freelance designers for a 3-week campaign push. The PM needs to spin up a new workspace, add both contractors to the active project, and create their first task cards—all before the kickoff call in 20 minutes. Breeze's MCP handles this in one prompt: create workspace, add people by email, scaffold cards with due dates. The API_KEY auth means no OAuth dance per contractor. This works cleanly for teams under 15 people who onboard contributors weekly. If you're managing 40+ projects with complex permission tiers, Breeze's flat workspace model gets messy fast. For small shops doing frequent short-term collabs, the MCP collapses 8 clicks into one sentence.

Archive completed projects without opening the app

A 3-person dev shop finishes a client build and needs to archive 4 old projects, delete placeholder cards from the final sprint, and remove the client's PM from the workspace—all while prepping the invoice. Breeze's MCP lets you script the teardown: archive by project ID, bulk-delete cards, remove users. The 18-tool scope covers the full project lifecycle, so cleanup happens in Switchy's chat instead of tab-switching through Breeze's UI. This is ideal for teams closing 2-5 projects per month who want handoff checklists automated. If your projects stay active for years with ongoing maintenance, archiving isn't frequent enough to justify the MCP setup. For shops with high project turnover, the MCP turns post-mortem admin into a 90-second prompt.

When Breeze bridges customer feedback and sprint boards

A 5-person SaaS team reviews 30 support tickets each Monday and converts 8-10 into Breeze cards for the current sprint. The support lead copies ticket summaries, assigns them to devs, and sets due dates based on severity. Breeze's MCP automates the conversion: paste ticket text, specify project and list, assign by email, set deadline. The Create Card tool accepts all metadata in one call, so batch triage takes 3 minutes instead of 20. This works for teams processing under 50 tickets weekly where most map 1:1 to tasks. If your tickets need multi-stage workflows or link to external CRMs, Breeze's simple card model won't capture the nuance. For lean teams doing weekly ticket-to-task sprints, the MCP eliminates the copy-paste grind.