Claude Bonsai connectorWhat Claude can do in your Bonsai account.
The Claude Bonsai connector exposes 39 tools. 16 read your CRM, projects, time and invoices, 23 create, update or delete. Below: what Claude can look up, what it can change in your business, what your role hides, and the limits Bonsai sets.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for freelancers and small service businesses
Bonsai holds your clients, deals, projects, tasks, time and invoices. With the connector, you run that from a conversation: ask where things stand, keep the CRM current, turn a won deal into a project and bill the hours, while Claude calls the Bonsai tools itself.
A morning digest. list_tasks pulls what is due today or overdue, and list_projects adds how much of each budget the current cycle has used.
A CRM that keeps up after calls. create_contact and create_company record the people you met, update_deal moves the opportunity forward and create_note keeps what was said on the client's record.
From hours to invoice. create_time_entry logs the work, create_invoice bills it and update_time_entry marks the hours as billed afterwards.
What Claude will not do here. It never does more than your Bonsai role allows: a tool your role cannot use does not even appear, and without financial access, time entries and tasks come back without their money fields. Bonsai documents more tools than the 39 on the directory sheet, and describes payments and reports as still to come. Nothing runs on its own either: no tool fires when a deal is won. Background rules of that kind belong to an automation tool, a different job, gathered on the Integrations hub. For another project tool, see the Claude asana connector.
Five words before you plug it in
The vocabulary you will meet while connecting Bonsai.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in that account while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude picks the ones it needs by itself, and the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use later. Given once per person, and taken back the same way.
- Approval
- The confirmation Claude waits for before it goes through with a change to your account, shown in the chat at the moment it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Bonsai.
Connecting Bonsai to Claude in three steps
- 01
Find Bonsai in Claude
In Claude's settings, open Customize, then Connectors, and look for Bonsai in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Bonsai in the window the service opens itself. If the link breaks later, Disconnect and connect again from the same row.
- 03
Read the authorization screen
Read Bonsai's screen before you accept it. It belongs to the service, not to Claude, and it decides what the access covers. You can also withdraw that access later from your Bonsai account itself.
The 39 tools, sorted by what they do
Bonsai gives Claude 39 tools: 16 that read your account, 23 that change something in it.
Two groups: what Claude reads, and what it creates, updates or deletes in your Bonsai account. Tool names stay as Claude shows them.
- 16 read
- 23 write
What Claude reads (16)
16 toolsSixteen tools that look up clients, deals, work, time and invoices without touching them.
get_note
Opens one note in full, including its body, which the list of notes never returns. It is the step Claude takes once it knows which note matters.
get_task
Fetches a single task by its ID, so Claude can answer questions about that one piece of work rather than a whole list.
list_board_groups
Lists your pipeline stages and your project groups. Claude uses it to learn the names of your columns before it sorts deals or projects into them.
list_comments
Lists the comments on a task or a deal, newest first, and can include system activity alongside what people wrote. You get the thread as it happened.
list_companies
Lists the companies in your CRM, with a name search, and each result carries the full profile: description, industry, size, source and social links.
list_company_tags
Lists the tags your account uses to label clients, deals, projects, tasks and more, with filters on name and type.
list_contacts
Lists your CRM contacts, with filters on name, email and company. Claude uses it to find the person behind a name mentioned in conversation.
list_deals
Lists your deals with filters on title, number and assignee, so Claude can report on the whole pipeline or pick out one deal in particular, by its number or its owner.
list_invoices
Lists invoices, each with how it repeats, the series it belongs to and whether that series is still running, filterable by number, project or company.
list_notes
Lists notes, most recent first, filtered by the record they are attached to, their author or the day they are about. The list does not include the body of each note.
list_projects
Lists projects with their dates, billing currency and budget, including how much of the budget the current cycle has used, with filters on status, group and budget.
list_subtasks
Lists the subtasks of a parent task, the child items that break a larger piece of work into steps.
list_task_statuses
Lists the board columns a task can sit in, such as To Do, In Progress or Done, as your own account defines them. Claude needs those names to report accurately.
list_tasks
Lists tasks with filters on title, assignee, status, due date, priority, project, deal, billable flag and tag. It is the tool behind most everyday questions about workload and deadlines.
list_team_members
Lists the people in your company with their roles. Claude can combine it with the task list to show who carries what, and who has room for more.
list_time_entries
Lists logged time with filters on dates, owner, project, company, billing status and currency.
What Claude creates, updates or deletes (23)
23 toolsTwenty-three tools that change your Bonsai data, invoices and time included. No source describes a Claude-side confirmation: the general rule below applies.
create_comment
Approval: see the rulePosts a comment on a task or a deal, written from the conversation you just had with Claude.
create_company
Approval: see the ruleAdds a company to your CRM, with domains, a primary contact and its profile: description, industry, size, source and social links.
create_contact
Approval: see the ruleAdds a contact to your CRM, optionally linked to a company.
create_deal
Approval: see the ruleOpens a new deal for a company, with a value and a pipeline stage.
create_invoice
Approval: see the ruleCreates a one-off, recurring or subscription invoice for a client company and project, with optional line items and due terms.
create_invoice_item
Approval: see the ruleAdds a line item to an invoice you just created and recomputes its total.
create_note
Approval: see the ruleWrites a note in Markdown, attached to a company, project or contact, or standing on its own, and can keep it private to you.
create_note_link
Approval: see the ruleAttaches a note you already wrote to a client company, a project or a contact, so it appears on that record too.
create_project
Approval: see the ruleStarts a project for a company, with its dates and billing setup.
create_task
Approval: see the ruleCreates a task with a title, project or parent task, deal, assignee, priority, dates, description, estimate, status, billable flag and tags.
create_time_entry
Approval: see the ruleLogs time against a project or a task, with notes, an hourly rate, billable status and who did the work.
destroy_invoice_item
Approval: see the ruleRemoves a line item from an invoice and recomputes its total.
destroy_note
Approval: see the ruleDeletes a note for good, handing back what it said so you can see what went.
destroy_note_link
Approval: see the ruleDetaches a record from a note, leaving the note itself in place.
destroy_task
Approval: see the ruleDeletes a task by its ID.
update_company
Approval: see the ruleUpdates a company's name, domains, primary contact or any profile field.
update_contact
Approval: see the ruleUpdates a contact's name, email address, job title or phone number, the four fields Bonsai lists for this tool.
update_deal
Approval: see the ruleUpdates a deal's value, stage, owner, probability or close date.
update_invoice
Approval: see the ruleUpdates an invoice's billing contact, currency, title or due terms. The line items are handled by separate tools.
update_invoice_item
Approval: see the ruleChanges a line item on an invoice and recomputes its total, so the amount due always matches the lines.
update_note
Approval: see the ruleRewrites what a note says, or changes its title, the day it is about or who can read it, keeping the rest intact.
update_task
Approval: see the ruleUpdates a task's title, project, deal, assignee, priority, dates, description, estimate, status, billable flag or tags.
update_time_entry
Approval: see the ruleUpdates a logged entry's duration, date, link, notes, rate, billable status, owner or billing status, including marking it billed or back to unbilled.
What Claude checks with you before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account on your behalf. The request shows up in the chat, right when it matters.
On Team and Enterprise, the owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organisation, keeping reading open and closing writing, for instance. That setting applies to everyone and nobody works around it from their own account. Bonsai adds its own layer: when you connect, it reads your permissions once and only shows the tools your role may use.
Which Claude plans include it
Out of the 819 sheets in the official directory, none shows availability by plan. The connector-by-connector answer is not published anywhere: it is a real gap in the catalogue.
The general rule is published: remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before members can connect. For the current state of this one, check the connector's sheet in the official directory. Bonsai's own subscription terms are set by Bonsai.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a deal is won, an invoice falls due or a task slips.
Everything here comes from Bonsai's own documentation: neither Claude's help centre nor Anthropic's developer docs have a page on this connector. The tool list is an observed floor, not a promise, since an admin can open actions no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic writes on every sheet that it does not choose the tools a publisher exposes nor guarantee how they behave. Bonsai itself describes its server as a beta, documents 46 tools against 39 on the sheet, and says payments and reports are still planned.
Need help connecting Bonsai to Claude?
A person reads every message.
