[Go to site: main page, start]
Share feedback
Answers are generated based on the documentation.
{ const container = $el; // The div with overflow const item = document.getElementById('sidebar-current-page') if (item) { const containerTop = container.scrollTop; const containerBottom = containerTop + container.clientHeight; const itemTop = item.offsetTop - container.offsetTop; const itemBottom = itemTop + item.offsetHeight; // Scroll only if the item is out of view if (itemBottom > containerBottom - 200) { container.scrollTop = itemTop - (container.clientHeight / 2 - item.offsetHeight / 2); } } })" class="bg-background-toc dark:bg-background-toc fixed top-0 z-40 hidden h-screen w-full flex-none overflow-x-hidden overflow-y-auto md:sticky md:top-16 md:z-auto md:block md:h-[calc(100vh-64px)] md:w-[320px]" :class="{ 'hidden': ! $store.showSidebar }">
Reference

sbx mcp unload

DescriptionUnload an MCP server from a running sandbox
Usagesbx mcp unload NAME --sandbox SANDBOX [flags]

Description

Detach an MCP server from a running sandbox's gateway. Connected agents stop seeing the server's tools immediately via the standard MCP tools/list_changed notification — no agent restart required. The server is not restored when the sandbox is restarted.

The server stays registered in the local MCP store; load it again with 'sbx mcp load', or remove the registration with 'sbx mcp rm'.

Options

OptionDefaultDescription
--sandboxTarget sandbox name (required)

Global options

OptionDefaultDescription
--cloudDispatch to Docker Cloud Sandboxes API instead of local sandboxd (supported by a growing set of verbs — run 'sbx --cloud --help' for the current list)
-D, --debugEnable debug logging

Examples

# Unload the 'notion' server from the running sandbox 'my-sbx'.
sbx mcp unload notion --sandbox my-sbx