Connect DeepSeek Harness to Busabase
DeepSeek's open-source agent harness — a plugin-based framework (Cordis) with its own shell, file editing, and sandboxes, currently in developer preview.
Paste this into DeepSeek Harness
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 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.
For this agent
The product ships as a local web UI (`npx @deepseek-ai/dsh web`, default http://127.0.0.1:3080) rather than a terminal chat — the agent loop runs with shell and file-editing tools in the background, so the setup prompt still works, but you'll watch its progress in a browser tab rather than a terminal.
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
- DeepSeek
- How it connects
- Plugin / Skill · MCP + API key
- Transport
- Streamable HTTP
- Authentication
- Unknown
- Config file
- cordis.yml (mcp-client plugin entries)
DeepSeek Harness ships its own shell and file-editing tools (dsh minimal/standard modes), so the Skill path applies — paste the prompt above and let it read the setup document.
Prefer a connector?
MCP support is an official first-party plugin, mcp-client (packages/mcp/mcp-client in the deepseek-harness repo) — not enabled by default. Add an entry under mcp-client in your cordis.yml:
mcp-client:
- transport: streamable-http
serverName: busabase
url: https://busabase.com/api/mcp
headers: {}
toolCallTimeoutMs: 30000
failOnStartupError: false
Put your Busabase API key in headers (e.g. Authorization: Bearer <key>) — the official config catalog documents no OAuth flow for this plugin, only a generic headers passthrough.
DeepSeek Harness config catalog
Known gotchas
This is a developer preview per the product's own framing, and a very recently public, actively-changing project — the config surface may shift. The mcp-client plugin documents only a generic `headers` field for authentication, with no named OAuth or API-key scheme, so there is no documented path for Busabase's dynamic-registration OAuth here — a static Authorization header is the only route the vendor's own docs confirm. Do not confuse this official repo (github.com/deepseek-ai/deepseek-harness) with the many third-party "dsh-*" plugins on GitHub (dsh-mcp-panel, dsh-mcp-manager, deepseek-harness-plugin-mcp, etc.) that surfaced in search results — those are community projects and were not used as a source for this record.
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 agentPaste this into DeepSeek Harness
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.