Connecting Muse
Muse is Meta’s assistant. It runs on its own machine in the cloud, runs tasks on a schedule, and connects to remote MCP servers as custom connectors. Connected to Bonsai, it becomes a reminder that walks past your Inbox for you: it checks what needs you at an interval you choose, messages you when something does, and asks again if you haven’t acted on it.
1. Connect Bonsai
Send Muse this message:
Create a Custom Connector for a remote MCP server, then connect to it:
Name: Bonsai
Transport: remote streamable HTTP
URL: https://livewithbonsai.com/mcp
Auth: OAuth
If your Muse has Settings → Connectors → Add custom connector, you can paste the URL there instead.
Muse opens Bonsai’s sign-in page. Sign in, then choose what Muse may see (all documents you can access, or only the sources you tick: your personal content, content shared directly with you, specific Groups) and whether it may write (read-only, or read and write). It is the same consent page other assistants use; see Connecting AI agents. To check the connection, ask Muse: “Ask Bonsai what needs me.”
2. Set up reminders
Muse runs recurring tasks that you describe in plain words. Paste this, then change the interval and the hours to suit you:
Every 15 minutes from 8:00 to 23:00, call Bonsai's list_inbox.
For each item you haven't told me about yet, send me one message with
its title, the question, the recommended option and its link.
If an item is still there 2 hours after you told me, remind me once more.
If nothing needs me, don't send anything.
The task appears in Muse’s Upcoming tab, where you can change or cancel it. Each run uses some of your Muse allowance: a shorter interval is closer to real time and costs more.
3. Choose what Muse brings you
list_inbox returns Need you unless the task asks for more: decisions waiting in an issue, and runs that failed or couldn’t be dispatched. To also hear about You should know or Completed, add it to the task, for example “include You should know”. Each item comes with a link that opens that card in your Bonsai Inbox, and a link to its issue or note.
A PR to review or a staging build to check isn’t an Inbox item. Those issues sit in Your turn on the board. To hear about them too, add a line to the task:
Also call list_issues with turn "human" and tell me about any issue
that is new there since the last time you checked.
4. Talk back
| You say to Muse | What happens in Bonsai |
|---|---|
| “Tell Bonsai: the pricing page needs a FAQ.” | Muse keeps your words unchanged in Capture: as a note in 0_Inbox/, or as a line in today’s daily note. |
| “What’s being worked on right now?” | Muse lists the issues that have a run going at this minute, with the machine and the role (list_issues with running). |
| “Which of my issues changed since yesterday?” | Muse filters issues by owner and by when they last changed. |
| “Move issue 12 to Done.” | Muse changes the issue’s status within its type’s workflow. |
To answer a decision, open the link Muse sends and choose on the card in Bonsai. Once the last open decision on an issue is answered, the issue moves on and Automation dispatches the next run to your runtime, so answering happens where you can see it.
What Muse can and can’t see
- Only the content you granted when you connected it. A read-only grant can’t write.
- When Muse creates or edits a note, the change waits under You should know with a short summary, like any assistant’s, until you mark it seen. Captures and issue status changes don’t wait there: a capture is your own words, and a status change shows on the board.
- Text inside your notes is data. It never changes what Muse is allowed to do.
- Muse runs in Meta’s cloud, and Meta doesn’t review custom connectors. To disconnect, remove Bonsai under Settings → Connectors in Muse.