Connect Manus to Busabase
Manus is an autonomous general AI agent that works in its own cloud sandbox (a virtual computer with internet access and a persistent file system) and takes actions instead of only answering.
Paste this into Manus
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

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
Manus Skills are SKILL.md folders (upload a .zip/.skill/folder or 'Import from GitHub'), so `npx skills add busabase/skills ...` run inside the sandbox may not register in the Skills tab; if it does not, import https://github.com/busabase/skills from the Skills page. Whether the sandbox allows `npx` and the device-login flow was not tested.
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.
At a glance
- Vendor
- Manus AI
- How it connects
- Plugin / Skill · busabase-cli · REST API · MCP + API key
- Transport
- Unknown
- Authentication
- API key
- Config file
- Connectors page: Create > Add MCP by URL (developer docs instead say Settings > Integrations > Custom MCP Servers > Add Server)
Manus runs in a sandbox where it can install software, so the Skill path applies. Paste the prompt above into a Manus task: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Review the commands it plans to run and approve the Busabase device-login link in your browser when Manus posts it.
Prefer a connector?
Manus can add a remote MCP server by URL.
- Open Connectors, choose Create, then Add MCP by URL. (The developer docs describe the same flow as Settings > Integrations > Custom MCP Servers > Add Server; the two vendor pages name different menus, so use whichever your app shows.)
- Name it
Busabaseand enterhttps://busabase.com/api/mcp. - If Manus offers an OAuth sign-in, approve the Busabase consent screen (scope
mcp). If it only offers a bearer token or API key, create a key in Busabase Settings > API Keys (smallest permission, finite expiry) and enter it as the token. - Ask Manus to call
auth_verify.
See the vendor docs: https://manus.im/docs/integrations/custom-mcp and https://manus.im/docs/features/skills
Known gotchas
The vendor's custom-MCP page lists 'API key, Bearer token, or other credentials' and does not say whether a custom server can use OAuth with dynamic client registration; only prebuilt catalog connectors are documented as OAuth 2.0. The English connectors page and the developer docs describe different menu paths. Ownership and operations are in flux: Meta acquired Manus on 2025-12-29, and in August 2026 the vendor announced a return to independent operation with a backup/delete/restore window for affected accounts (data generated on/after 2025-12-29 deleted 2026-08-23 to 08-24 SGT).
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | Agent platforms | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | Plugin / Skill · busabase-cli · REST API · MCP + API key | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Unknown | Streamable HTTP | Streamable HTTP |
| Authentication | API key | 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 Manus
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.