Connect Qwen Code to Busabase
Open-source terminal coding agent from the Qwen team with shell tools and stdio or remote HTTP MCP support.
Paste this into Qwen Code
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.
For this agent
Qwen Code can run shell commands, so the Skill path avoids manual static OAuth client setup.
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.
Qwen Code MCP documentationAt a glance
- Vendor
- Alibaba Cloud
- How it connects
- MCP + OAuth · MCP + API key · Plugin / Skill · busabase-cli · REST API
- Transport
- Streamable HTTP
- Authentication
- OAuth (static client)
- Config file
- ~/.qwen/settings.json or .qwen/settings.json
npm install -g @qwen-code/qwen-code@latestInstall Qwen Code, start qwen in a trusted project, and ask: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Review the commands, complete authentication, and ask it to verify the active workspace. Its native remote MCP command shape is qwen mcp add --transport http <name> <url>, but OAuth normally needs explicit client metadata.
Known gotchas
Qwen Code's documented OAuth configuration expects explicit client ID, client secret, authorization URL, and token URL. That is not Busabase's preferred dynamic-registration flow, so use the Skill path unless you provision a static client.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | Terminal agents | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | MCP + OAuth · MCP + API key · Plugin / Skill · busabase-cli · REST API | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Streamable HTTP | Streamable HTTP | Streamable HTTP |
| Authentication | OAuth (static client) | 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 Qwen Code
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.