Busabase for NemoClaw

Connect NemoClaw to 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 server

https://busabase.com/api/mcp

Read the NemoClaw documentation

Busabase

MCP connector

Set it up

Hosted chat has no shell and no file system, so a connector is the way in.

Add the server

Point your chat client at the Busabase MCP endpoint.

Sign in

Complete OAuth in the browser — no client id or secret to create.

Pick the smallest permission

changeRequest lets the agent propose but never merge.

Verify

Ask the agent to call auth_verify before it does any work.

Step by step

This host has no shell, so a connector is the only way in.

At a glance

Vendor: NVIDIA
How it connects: MCP + API key
Transport: Streamable HTTP
Authentication: API key
Config file: Managed by `nemoclaw <sandbox> mcp add`; for OpenClaw it writes `mcp.servers` in the sandbox's openclaw.json

Run this

curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash

NemoClaw 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).

NemoClaw: Add an MCP server

Known gotchas

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.

How it compares

Connection capabilities side by side with other agents already in this directory.

Capability	NemoClaw	Claude Code	Cursor
Type	Agent platforms	Terminal agents	AI editors
Recommended path	MCP connector	Agent Skill	Agent Skill
How it connects	MCP + API key	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill
Transport	Streamable HTTP	Streamable HTTP	Streamable HTTP
Authentication	API key	OAuth (dynamic registration)	OAuth (dynamic registration)

These stepsFrom official docsLast checked Oct 21, 2026

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.

Where these steps come from Official site

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 agent

Busabase MCP server

https://busabase.com/api/mcp