Busabase for Factory DroidConnect Factory Droid to Busabase
Factory's terminal agent runtime for interactive coding, headless execution, custom droids, skills, plugins, and MCP tools.
Paste this into Factory Droid
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
Droid supports skills and shell commands. Run setup in the intended project and inspect all commands before execution.
Prefer a connector?
If you would rather wire Busabase in as MCP tools than let the agent install a skill, use the server URL below.
Factory Droid MCP documentationAt a glance
- Vendor
- Factory
- How it connects
- MCP + OAuth · MCP + API key · Plugin / Skill · busabase-cli · REST API
- Transport
- Streamable HTTP
- Authentication
- Unknown
- Config file
- ~/.factory/mcp.json or .factory/mcp.json
curl -fsSL https://app.factory.ai/cli | shInstall Droid, run droid in a trusted repository, and ask: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Review and approve the setup, then ask Droid to verify the active account. A manual remote MCP fallback can be added with droid mcp add busabase https://busabase.com/api/mcp --type http.
Known gotchas
Droid can authenticate OAuth servers in the /mcp UI, but the official page does not state whether it uses dynamic or static client registration. OAuth tokens are stored in the system keyring or a fallback file.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | Factory Droid |  Claude Code |  Cursor |
|---|---|---|---|
| Type | Terminal agents | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | MCP + OAuth · MCP + API key · Plugin / Skill · busabase-cli · REST API | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Streamable HTTP | 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 Factory Droid
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.