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.

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.
npx skills add busabase/skillsPrefer 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
- Open Settings → MCP and add an MCP server.
- Name it
busabaseand set the URL tohttps://busabase.com/api/mcp. - Choose OAuth or connect when WorkBuddy detects the protected server.
- 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 Enterprise Console → AI Resource Management → Connector Management → New connector. In step 1 the identifier you choose is stored with an enterprise_ prefix. In step 2 choose authentication type MCP OAuth 2.1; in step 3 enter only the Busabase MCP Server URL — per Tencent's page (updated 2026-11-10), credentials are then established automatically through the standard OAuth flow, with no Client ID or Secret to fill in. Transport is http (Streamable HTTP, the default) or sse. Save, authorize, and run the connector test.
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.
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. The Enterprise Connector Management page (updated 2026-11-10) also documents an OAuth 2.0 mode with a static Client ID/Secret and an API Key mode (header name, default X-API-Key, with an optional prefix such as 'Bearer '), and it documents no local config file at all — the ~/.workbuddy/mcp.json path above rests on the personal-edition documentation, not on that enterprise page.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | IDE plugins | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Streamable HTTP | Streamable HTTP | Streamable HTTP |
| Authentication | OAuth (dynamic registration) | 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 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.