Connect Cursor to Busabase
The AI-first code editor; MCP servers are managed under Settings → Tools & MCP.
Paste this into Cursor
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 approval-first 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.
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
- Anysphere
- How it connects
- MCP + OAuth · Plugin / Skill
- Transport
- Streamable HTTP
- Authentication
- OAuth (dynamic registration)
- Config file
- ~/.cursor/mcp.json
Add Busabase globally in ~/.cursor/mcp.json, or add the same entry to .cursor/mcp.json for one project:
{
"mcpServers": {
"busabase": {
"url": "https://busabase.com/api/mcp"
}
}
}
Open Cursor Settings → Tools & MCP, find Busabase, and choose Connect or Log in to complete OAuth. The server should show as enabled with its tools available. Ask the agent to call auth_verify.
If Cursor keeps an old account, disconnect Busabase in MCP settings, remove its saved authorization, and connect again. You do not need to add a static client id or secret because Busabase supports dynamic client registration.
Known gotchas
Cursor remembers an old account: disconnect Busabase in MCP settings and remove its saved authorization before reconnecting. No static client id or secret is needed — Busabase supports 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, reviewed access, and every change it makes afterwards arrives as a proposal you approve.
Browse every agentPaste this into Cursor
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.