把 NemoClaw 連接到 Busabase
NVIDIA's open-source (alpha) reference stack for running OpenClaw, Hermes or LangChain Deep Agents Code more safely inside NVIDIA OpenShell sandboxes with managed inference, network policy and managed MCP servers.
Busabase MCP 伺服器
https://busabase.com/api/mcp

設定步驟
代管聊天沒有 shell、也沒有檔案系統,連接器是唯一的入口。
加入伺服器
把你的聊天用戶端指向 Busabase 的 MCP 端點。
登入
在瀏覽器中完成 OAuth —— 不需要建立 client id 或密鑰。
選擇夠用的最小權限
changeRequest 只讓 Agent 提出變更提案,永遠無法自行合併。
驗證
請 Agent 在開始任何工作之前,先呼叫 auth_verify。
逐步說明
這個主機沒有 shell,連接器是唯一的入口。
一覽表
- 廠商
- NVIDIA
- 連接方式
- MCP + API 金鑰
- 傳輸方式
- Streamable HTTP
- 驗證方式
- API 金鑰
- 設定檔
- Managed by `nemoclaw <sandbox> mcp add`; for OpenClaw it writes `mcp.servers` in the sandbox's openclaw.json
curl -fsSL https://www.nvidia.com/nemoclaw.sh | bashNemoClaw is a sandbox wrapper, not a separate agent: the agent inside (OpenClaw by default, or Hermes / Deep Agents Code) does the work. Its egress policy is deny-by-default and its MCP integration keeps the credential outside the sandbox, so the connector is the cleanest route.
- In Busabase, open Settings -> API Keys and create a key (smallest permission, finite expiry).
- On the NemoClaw host, export it and register the server (replace
my-sandbox):
export BUSABASE_MCP_TOKEN='<paste key>'
nemoclaw my-sandbox mcp add busabase --url https://busabase.com/api/mcp --env BUSABASE_MCP_TOKEN
unset BUSABASE_MCP_TOKEN
- Check readiness with
nemoclaw my-sandbox mcp status busabase. - In the sandboxed agent, ask it to call
auth_verify.
Skill path alternative: the sandbox agent has a shell, but you must first approve or add network policy for busabase.com and registry.npmjs.org (see the network policy docs), then use the agent's own Skill setup (see /connect-agents/openclaw or /connect-agents/hermes-agent).
已知的注意事項
Alpha project (maintainers respond best-effort). Managed MCP accepts Streamable HTTP over HTTPS only (no stdio), exactly one bearer credential via `--env` per server, a unique env var name per server, and needs OpenShell 0.0.116. NemoClaw resolves the hostname and pins the validated IP addresses in the policy; public endpoints that rotate address sets (CDN-fronted hosts) need `mcp` pin refresh ('Change Endpoint Pins'). No OAuth flow is documented. Do not test the route with `curl` from a sandbox shell: only the adapter's runtime binaries are allowed.
能力比較
與目錄中其他已收錄的 Agent,並列比較連線能力。
| 能力 | |||
|---|---|---|---|
| 類型 | Agent 平台 | 終端機 Agent | AI 編輯器 |
| 推薦路徑 | MCP 連接器 | Agent Skill | Agent Skill |
| 連接方式 | MCP + API 金鑰 | MCP + OAuth · 外掛/技能 | MCP + OAuth · 外掛/技能 |
| 傳輸方式 | Streamable HTTP | Streamable HTTP | Streamable HTTP |
| 驗證方式 | API 金鑰 | OAuth(動態註冊) | OAuth(動態註冊) |
Busabase MCP 伺服器
https://busabase.com/api/mcp