All agents
Busabase for WorkBuddy

Connect WorkBuddy to Busabase

Tencent's coding assistant: Settings → MCP on personal, Connector Management (MCP OAuth 2.1) on Enterprise.

Paste this into WorkBuddy

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Read the WorkBuddy documentation
Busabase
Agent Skill
The Busabase review inbox, showing proposed changes waiting for approval

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
Tencent
How it connects
MCP + OAuth · Plugin / Skill
Transport
Streamable HTTP
Authentication
OAuth (dynamic registration)
Config file
~/.workbuddy/mcp.json

Personal WorkBuddy / IDE

  1. Open Settings → MCP and add an MCP server.
  2. Name it busabase and set the URL to https://busabase.com/api/mcp.
  3. Choose OAuth or connect when WorkBuddy detects the protected server.
  4. Complete Busabase consent and test the connection.

Where file configuration is supported, use ~/.workbuddy/mcp.json globally or <project>/.workbuddy/mcp.json:

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

WorkBuddy Enterprise

Open Connector Management, create a connector with authentication type MCP OAuth 2.1, enter the Busabase MCP URL, save, authorize, and run the connector test. Busabase dynamic registration means no client id or secret is normally required.

If your WorkBuddy version or organization policy does not expose MCP OAuth, use the Enterprise Connector, the Busabase Agent Skill, or the API-key fallback below.

WorkBuddy MCP documentation

Known gotchas

Some versions or org policies do not expose MCP OAuth. Use the Enterprise Connector, the Busabase Agent Skill, or the API-key fallback instead.

These stepsFrom official docsNo check date recorded

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 fromOfficial site

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into WorkBuddy

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.