Busabase for 扣子空间 Coze SpaceConnect 扣子空间 Coze Space to Busabase
ByteDance's agent space, which accepts custom MCP services; it is also the outward extension surface for 豆包.
Busabase MCP server
https://busabase.com/api/mcp
Busabase
Set it up
Hosted chat has no shell and no file system, so a connector is the way in.
Add the server
Point your chat client at the Busabase MCP endpoint.
Sign in
Complete OAuth in the browser — no client id or secret to create.
Pick the smallest permission
changeRequest lets the agent propose but never merge.
Verify
Ask the agent to call auth_verify before it does any work.
Step by step
This host has no shell, so a connector is the only way in.
At a glance
- Vendor
- ByteDance
- How it connects
- MCP + API key
- Transport
- Streamable HTTP
- Authentication
- API key
Add a custom MCP service and paste the URL. If the platform only accepts a static header rather than OAuth, create an API key scoped to changeRequest rather than write. The platform can then propose changes but can never merge them, so approval-first is enforced by the credential itself instead of by instructions the agent could ignore.
Known gotchas
The platform may only accept a static header rather than OAuth. Create a changeRequest-scoped API key (not write) — the credential itself then enforces propose-but-never-merge, which is more reliable than instructions an agent could ignore. It also cannot reach Busabase Desktop.
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 agentBusabase MCP server
https://busabase.com/api/mcp