Busabase for Meta MuseConnect Meta Muse to Busabase
Meta's consumer personal AI agent: each user shares a persistent cloud Linux VM (terminal, file system, browser) with the agent; chat in the Muse app, Mac app, or WhatsApp. US rollout; free tier plus paid plans.
Paste this into Meta Muse
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.
Busabase
Give your agent this one instruction
You end up with more than a connector: the busabase skill carries the whole change-request workflow, the CLI, and the full API — available in every future session without re-pasting anything.
Asks first
Busabase Cloud or Personal Desktop — your call, before anything happens.
Connects
Signs you in and stores the credential itself. No API key to copy by hand.
Seeds a Base
Creates and fills your first Base, so the workspace is not an empty screen.
Installs the skills
busabase and busabase-app-creator become permanent, for every session after this.
For this agent
Meta's security post says Muse is trained on tool calling 'using CLIs and skills' and that it can 'develop custom skills' in its VM, but it does not say whether it reads the open Agent Skills (SKILL.md) format, so `npx skills add` is untested here.
Other ways in
Busabase can't be added to this agent as an MCP connector, so there is nothing to wire in. These routes work instead.
At a glance
- Vendor
- Meta
- How it connects
- busabase-cli · REST API
- Transport
- Unknown
- Authentication
- Unknown
- Config file
- Settings > Connectors
Muse runs on its own cloud computer with a terminal, so the Skill path applies: tell Muse "Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me" and approve the network and sign-in prompts it shows.
Prefer a connector?
Muse has no field for pasting a remote MCP server URL. Its Help Center says: ask Muse to create a Custom Connector for a service not in the list; Muse walks you through it using the service's API information and keeps secrets in its Secure Credentials Store. For Busabase, give it the REST API and an API key created in Busabase Settings → API Keys (smallest permission, finite expiry). Meta does not review custom connectors, so grant access with caution. The Muse Connector Platform (platform.muse.ai) is for vendors submitting connectors for Meta review, not for end users.
Known gotchas
Rolling out in the US (iOS, Android, muse.ai; Mac app). All network egress from the VM goes through Meta's Sentinel, which asks the user to approve; expect approval prompts for busabase.com. Whether Node/npx (needed by `npx busabase-cli`) is installed in the VM is not documented, so the CLI step may need Muse to install it. No documented way for a user to add a remote MCP server by URL. Meta says it does not review user-created custom connectors.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | Meta Muse |  Claude Code |  Cursor |
|---|---|---|---|
| Type | Agent platforms | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | busabase-cli · REST API | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Unknown | Streamable HTTP | Streamable HTTP |
| Authentication | Unknown | OAuth (dynamic registration) | OAuth (dynamic registration) |
Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.
Let your agent do the setup
One instruction, one authorization, and every change it makes afterwards carries a message and a diff you can check or revert.
Browse every agentPaste this into Meta Muse
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.