把 DeepSeek Harness 連接到 Busabase
DeepSeek's open-source agent harness — a plugin-based framework (Cordis) with its own shell, file editing, and sandboxes, currently in developer preview.
把這段貼進 DeepSeek Harness
請閱讀 https://busabase.com/SETUP_SKILL.md,並幫我設定好 Busabase。請照著文件一路做到完成,最後確認連線是否正常運作。

把這一句指令交給你的 Agent
你得到的不只是一個連接器:busabase 技能還帶著完整的變更請求工作流程、CLI 與完整 API —— 之後每一次工作階段都在,不必再重新貼一次。
會先問你
Busabase Cloud 還是個人桌面版 —— 在動手之前,由你決定。
完成連線
幫你登入並自行儲存憑證,不需要手動複製 API 金鑰。
建立一個資料表
建立並填入你的第一個資料表,讓工作區一開始就不是空白畫面。
安裝技能
busabase 與 busabase-app-creator 會永久安裝,之後每一次工作階段都能直接使用。
此 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.
比較想用連接器?
如果你不想讓 Agent 自行安裝技能,而是想把 Busabase 當作 MCP 工具接進來,可以使用下面這個伺服器網址。
一覽表
- 廠商
- DeepSeek
- 連接方式
- 外掛/技能 · MCP + API 金鑰
- 傳輸方式
- Streamable HTTP
- 驗證方式
- 未知
- 設定檔
- 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
已知的注意事項
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.
能力比較
與目錄中其他已收錄的 Agent,並列比較連線能力。
| 能力 | DHDeepSeek Harness | ||
|---|---|---|---|
| 類型 | Agent 平台 | 終端機 Agent | AI 編輯器 |
| 推薦路徑 | Agent Skill | Agent Skill | Agent Skill |
| 連接方式 | 外掛/技能 · MCP + API 金鑰 | MCP + OAuth · 外掛/技能 | MCP + OAuth · 外掛/技能 |
| 傳輸方式 | Streamable HTTP | Streamable HTTP | Streamable HTTP |
| 驗證方式 | 未知 | OAuth(動態註冊) | OAuth(動態註冊) |
把這段貼進 DeepSeek Harness
請閱讀 https://busabase.com/SETUP_SKILL.md,並幫我設定好 Busabase。請照著文件一路做到完成,最後確認連線是否正常運作。