Busabase for 扣子空间 Coze Space

Connect 扣子空间 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

Read the 扣子空间 Coze Space documentation

Busabase

MCP connector

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
Transport: Streamable HTTP
Authentication: Unknown

Coze Space adds a custom MCP from the web or desktop app (mobile can only view and use MCPs that are already added):

Open Extensions → MCP and choose Add custom MCP (top right).
Paste the full MCP JSON — one JSON can contain several servers; Coze connects and adds each one separately:

{
  "mcpServers": {
    "busabase": {
      "url": "https://busabase.com/api/mcp"
    }
  }
}

Name it and save it to My MCP. Saving alone does not attach it to an Agent: bind it via Me → My MCP → Add, in the Agent's settings, or by pasting the JSON into an Agent chat and asking it to connect.
If the page prompts for third-party authorization or connection credentials, complete that step as prompted; an MCP that needs no authentication can be added directly.

Coze's MCP documentation names no authentication scheme for custom servers (see Known issues), so whether Busabase's sign-in completes on this surface is not documented by Coze.

Coze MCP documentation

Known gotchas

Coze's MCP page supports Streamable HTTP and SSE only — STDIO is not supported. Creating a custom MCP is web/desktop only, and Coze recommends at most 10 MCPs per Agent. The page's only JSON example carries just a url key: no headers, command, args or auth key is documented, and the page names no OAuth flow, dynamic registration, static header or API-key scheme — each server's detail page shows its own auth method, and adding one may prompt for third-party authorization or connection credentials. An earlier version of this entry claimed a static-header/API-key route sourced from Busabase's own documentation rather than Coze's; that claim was removed on 2026-11-13 after re-reading Coze's page.

How it compares

Connection capabilities side by side with other agents already in this directory.

Capability	扣子空间 Coze Space	Claude Code	Cursor
Type	Web chat	Terminal agents	AI editors
Recommended path	MCP connector	Agent Skill	Agent Skill
How it connects	—	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill
Transport	Streamable HTTP	Streamable HTTP	Streamable HTTP
Authentication	Unknown	OAuth (dynamic registration)	OAuth (dynamic registration)

These stepsFrom official docsLast checked Nov 13, 2026

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.

Where these steps come from Official site

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 agent

Busabase MCP server

https://busabase.com/api/mcp