# AI assistants, MCP and API (BreeStudio documentation)

Connect Claude, ChatGPT or Gemini to BreeStudio, see what they can do, from templates to client payments, and undo anything they changed.

Source: https://breestudio.com/docs/ai-assistants · Updated 2026-11-12 · Describes the BreeStudio web app at https://app.breestudio.com. Words in **bold** are the app's own button, tab and menu names.

## Connect an assistant

BreeStudio has an MCP server, the standard AI assistants use to work with apps. Its address is https://app.breestudio.com/api/mcp, also shown with a copy button in **Settings › AI assistants**.

1. In Claude, open Settings › Connectors › Add custom connector. In ChatGPT, Gemini, Cursor or another app that supports MCP, add a remote MCP server. Paste the address.
2. The assistant sends you to BreeStudio. Sign in if you need to.
3. Read what it will be able to do and press **Allow access**.

Only studio members can connect an assistant; clients and guests can’t. The connection appears under **Connected** in Settings, with when it was last used, and **Disconnect** stops it straight away.

> The MCP server and the API are in beta (version 1.0.0-beta.1). They work, and tools and fields can still change before 1.0. Check what an assistant changes; everything is listed in Settings and can be undone.

## What an assistant can do

| Area | It reads | It changes |
| --- | --- | --- |
| Projects | The projects you can see, with their lead, team, task groups and task counts | Creates draft projects with a client, colleagues, a project type and templates, and invites the client when you ask; renames them, changes their status, archives, restores and deletes them |
| Brief | The **Info** tab’s sections and fields, and which required ones are empty | Fills in or clears up to 50 fields at a time. A deadline, start date or budget field also updates the project’s dates or budget. The project type and the client stay as they are |
| Gallery | Folders, images, videos and links, and which ones the client sees | Adds folders, and images, videos or links from the web; renames, tags, moves, shares and trashes them |
| Tasks | Tasks by project, person, status or due date, with checklists, what each waits for and comments | Creates, re-dates, assigns, prioritises and archives up to 50 tasks at a time; checklists, key dates, what a task waits on (it starts when the other finishes), task groups and comments |
| Budget | Every line by table and category, with quantity, totals with and without VAT, status, supplier and approval | Adds, updates, moves and deletes lines; adds, renames and reorders tables and categories. Approval stays the client’s |
| Orders | Supplier orders with their lines, dates, what is late, and payments paid, due or overdue | Groups lines into an order, sets order and arrival dates, applies a payment plan or instalments, marks payments paid |
| Clients & offers | Clients, new and active, with their contact details, offers and projects; the board’s steps and each offer’s value, chance, who handles it, when an answer is expected, and notes | Adds and edits clients (an email already in Clients is refused); adds offers, moves them along the board, archives or deletes them; adds notes to a client or an offer |
| Templates | Task and budget templates, yours and the built-ins, with the project types each is offered for and each type’s default | Creates templates from what it writes (from an offer, say), a copy or a project; edits and deletes yours; sets a type’s default; applies one to a project |
| Finance | Per project and in total: received, to come, overdue and due in the next 30 days; payment schedules, design fees, supplier commissions, and invoice and contract records | Records a client payment, in part or in full; adds design fees and supplier commissions and marks them received |
| Calendar | Events, the next 30 days unless you ask otherwise, with attendees | Creates, moves and deletes events, with attendees |
| Notes | Project notes, pinned first | Adds, edits, pins and deletes notes |
| Changes | What assistants changed, by name, with before and after | Undoes a change |

Orders work as in the **Orders** tab: an arrival date moves the order’s lines to **Delivered**, an order date moves them to **In transit**, and paying a supplier sets the order date if it was empty.

It works with your role’s access and nothing more. It can’t upload files or put pictures and documents on a budget line, approve for the client, add or edit suppliers (it reads their names), build an offer’s quote or edit services and packages (it sets an offer’s value, not its quote lines), make or change a payment schedule, add invoices, edit the built-in templates, or change billing and settings. Files stays in the app.

## Templates and new projects

An assistant works with the same [Template library](https://breestudio.com/docs/templates) as **Settings › Templates**: task templates and budget templates. Project info templates (the brief) stay in the app.

| Start from | What the template gets |
| --- | --- |
| What the assistant writes | Anything you describe or attach, such as a design offer: phases (task groups) with tasks, descriptions, priorities, key dates, checklists, durations in calendar or working days, and which task waits for which. For a budget: tables, lines, quantities, units, categories and estimated prices without VAT |
| A copy | A whole template, a built-in included. Built-ins can’t be changed, so copy one to make it yours |
| A project | Its task groups, tasks, checklists and what each waits for, without dates, people or status. Or its budget: tables and lines with estimated unit prices, without suppliers |

A new template is offered for no project type until you say which. Ask the assistant to make it a type’s default and new projects of that type start from it.

Applying a template adds to the project and never replaces: its phases come in as new task groups after the existing ones, and budget lines are added at **To be ordered**, team-only, at the budget’s VAT and currency. Applying the same template twice adds everything twice. Tasks get dates only when the template schedules them and the project has a start date.

A new project can be made in one request: the title, the project type, an accepted offer or a client who is already in Clients, colleagues, and the type’s default task and budget templates. Colleagues join with the designer role. Give the start date in the same request: the assistant sets it on the **Info** tab first, when the brief has a start date field, so the tasks come in dated.

> The assistant invites the client only when you ask. BreeStudio then emails the invitation in your name, valid for 7 days, and an email can’t be unsent, even if the change is undone.

## Clients and offers

With access to Clients in your role, an assistant works with [Clients and offers](https://breestudio.com/docs/crm) as the app does. All your clients are one list: a new client is someone you are still talking to, and the others are active or past.

- **Clients**: it adds up to 20 at a time, as new clients unless you say otherwise, and edits their contact details, type, tags and status. An email already in Clients is refused. Adding someone doesn’t invite them to BreeStudio.
- **Offers**: it adds offers for a client with a value, chance, priority, who handles it and when an answer is expected, and moves them along your board’s steps. **Accepted** or **Declined** settles an offer at 100% or 0% chance, and Accepted makes a new client active. Ask it to start the project from an accepted offer.
- **Notes**: it adds a note, such as a call summary, to a client or an offer. These notes are team-only.
- **Deleting**: a client tied to a project, or an offer with a project, invoices, a payment schedule or recorded fees, isn’t deleted. The assistant marks the client as past or archives the offer instead.
- **Out of reach**: an offer’s quote (its service lines and the PDF), and services and packages. The assistant sets an offer’s value; you build the quote in the app.

## Client payments and commissions

With access to Finance in your role, an assistant reads the studio’s own money, as [Finance](https://breestudio.com/docs/finance) shows it: per project and in total, what was received, what is to come, what is overdue and what is due in the next 30 days, in each currency. In these totals a payment counts as overdue once it is invoiced and its due date has passed. BreeStudio’s own subscription and billing are not available to it.

- **Record a payment**: tell it what a client paid and when. It records it against that payment in the schedule, in part or in full. A payment stays open until what came in covers it, and more than is left is refused.
- **Design fees and commissions**: it adds design fees and supplier commissions, pending or received, and marks them received later.
- **Out of reach**: making or changing a payment schedule, marking a payment invoiced, adding invoices or contracts, and attaching proofs. Invoice and contract records can be read, their files can’t.

## Things to ask

Ask in your own words. The assistant reads before it changes anything, and tells you when something is out of its reach.

| For | Ask |
| --- | --- |
| A look across the studio | What’s overdue across all projects, and whose is it? Which supplier payments are overdue or due this week? |
| A budget check | Is anything missing or counted twice in this budget? Add the missing items as lines I can price later |
| Tidying a budget | Move the lines into the right room tables. Split Living & kitchen into two tables. Delete the test lines |
| Orders and payments | The lounge chairs arrived, mark the order arrived. We paid the balance on Friday, mark it paid |
| Planning | Re-plan the open tasks from today so we finish by the 27th, with what each task waits on, and move the deadline. What is the install day waiting for? |
| Follow-up | Make me a task with a checklist of what I still have to sort out |
| Ideas and references | Find pictures of a rust wool armchair and put them in a gallery folder |
| Templates | Make this offer a task template, one phase per service. Make it the default for Residential. Save this project’s tasks as a template |
| The board | Which offers need me this week? Log my call with Radu and move his offer to Contacted. Add Ioana as a new client with a €7,000 offer. Mark Vila Snagov as accepted |
| A new project | Start the project from Dan’s accepted offer, starting on the 16th, from the Residential templates. Invite the client |
| Money | Who owes us money, and what’s overdue? The client paid €4,000 today, record it. Log Atelier Nord’s commission as pending |
| Work from outside | Add this supplier quote to the budget. Turn my site notes into tasks. Fill in the brief from the client’s questionnaire |
| Undo | What did assistants change yesterday? Undo the last change |

More examples, by job, are on the [AI page](https://breestudio.com/ai).

## What keeps it safe

- **The studio decides**: in **Settings › AI assistants**, set the studio to **Read and change**, **Read only** or **Off**.
- **Deletes wait for you**: the assistant shows what it would delete and asks before it does. At most 20 at a time and 200 a day. Tasks and lines with comments or attachments, and lines on an order, are left for you to delete in BreeStudio.
- **No duplicates**: a project, task, line, table, category, event, note, gallery item, order, template or a client’s offer with the same name as an existing one, or a client with an email already in Clients, is refused unless you ask for it. Applying a template is the exception: it adds its tasks or lines again.
- **No silent overwrites**: if someone edited a row after the assistant read it, the change is refused.
- **Names must match**: every change carries the current name of what it touches, so the approval prompt shows names, and a name that doesn’t match is refused.
- **Team-only by default**: new tasks, lines, notes and gallery items stay hidden from the client unless you say otherwise.
- **Client text is data**: comments and notes reach the assistant marked as data, so a message in a project can’t give it orders.

Some changes tell people, as they do in the app: a task comment notifies the task’s people, event attendees hear about the event, the project lead hears about a status change, and an invited client gets an email. A notification or an email can’t be taken back by an undo.

## Narrow a connection

Add options to the server address to limit what one connection can do. The studio’s switch in Settings can narrow it further, never widen it.

| Add to the address | What it does |
| --- | --- |
| ?read_only=true | Only reading; every change is refused |
| ?features=tasks,calendar | Only these areas: projects, tasks, budget, templates, crm (Clients), finance, calendar, notes, changes. The gallery and the brief are part of projects, orders part of budget |
| ?organization_id=… | Only one studio, when you belong to several |

## See and undo changes

Every request that changes something is saved as one change, with a line saying what it was for. **Settings › AI assistants › Changes** lists them, newest first. Open one to see each field before and after, and **Undo change** to put every row back. The undo is a change too, so it can be undone in turn. If someone edited the same rows since, nothing is undone and you see what clashed.

## The REST API

The same operations are a REST API at https://app.breestudio.com/api/v1, described in OpenAPI at /api/v1/openapi.json. It signs in with OAuth, like the assistants, works with the access of the person who connected, and follows the same rules. See [AI, API and MCP](https://breestudio.com/ai).
