- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add docker/skills --skill docker-sandboxes-mcp-gateway -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add docker/skills --skill docker-sandboxes-mcp-gateway -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add docker/skills --skill docker-sandboxes-mcp-gateway -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add docker/skills --skill docker-sandboxes-mcp-gateway -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/docker/skills/tree/HEAD/skills/docker-sandboxes-mcp-gateway來自發布者
Every local Docker Sandbox starts a host-side MCP gateway. The agent inside the microVM sees one MCP endpoint, while sbx mcp registers servers, holds OAuth and header credentials, and decides which servers each sandbox can use. This skill owns sbx mcp and the static/dynamic loading model. It does not cover the Docker Desktop MCP Toolkit (docker mcp), which is a separate product.
Activate this skill when:
sbx sandbox to use a remote or host-run MCP server.--static-mcp), or none.Do not use this skill when:
docker mcp (MCP Toolkit profiles, docker mcp gateway run, docker mcp client connect). It is a different product with separate server settings; use docker-docs to look up current Toolkit docs.docker-sandboxes-lifecycle.docker-sandboxes-network-credentials.mcp block of a checked-in sbxenv.yaml; use docker-sandboxes-env.agent.yaml; use docker-agent-config.sbx login first if the user is not authenticated. Docker must be running on the host for --local OCI servers and explicit docker commands.sbx mcp for agents inside Docker Sandboxes and docker mcp only for agents on the host. Servers enabled in the MCP Toolkit are not shared with Docker Sandboxes, and the Toolkit is not required.mcp.* setting advice, confirm which gateway the sandbox uses. A hosted (SaaS) gateway may be selected for the account, and mcp.forceLocalGateway can force the local one. Hosted gateways do not support sbx mcp unload, and the hosted gateway rejects header registrations unless --oauth-authorization-server is given. Before changing mcp.forceLocalGateway, state to the user that it is host-global, needs sbx daemon restart, and does not override organization governance, and get their agreement.sbx mcp add registrations. Connect the server in Docker Agentic Platform, then run sbx --cloud mcp load <server-name> --sandbox <sandbox>; inspect with sbx --cloud mcp ls [sandbox].sbx mcp add as host-only: it stores the definition and does not expose the server to any sandbox.--static-mcp at create/run time, or sbx mcp load on an existing sandbox.none is reserved.# Remote server; OAuth is prompted unless --skip-auth is passed
sbx mcp add notion --url https://mcp.notion.com/mcp
# Attach to a running sandbox; connected agents get a tool-list update
sbx mcp load notion --sandbox my-session
All flags and subcommands that were documented are in references/sbx-mcp-reference.md.
--static-mcp) pre-loads nothing and lets the agent find and attach registered servers. Static loads only the named servers and exposes no discovery tools (mcp-find, mcp-add, mcp-config-set).--static-mcp must already be registered. Pass a comma-separated list or repeat the flag.--static-mcp when reconnecting to an existing sandbox does not replace its initial set. Reuse the sandbox and use sbx mcp load, or create a new one with a new name.--static-mcp none (0.51.0+) to start with no servers and no discovery; it stays static after the last server is unloaded and after restarts.sbx mcp load can still attach host-registered servers, the agent may run its own MCP clients, and sandbox egress is governed by sbx policy and org MCP policy, which are separate controls.sbx mcp add linear --url https://mcp.linear.app/mcp
sbx run claude --name my-session --static-mcp notion --static-mcp linear
sbx run claude --name locked --static-mcp none
--command, or --local with a metadata URL) run on the host, not in the microVM. A server that starts a Docker container uses host Docker isolation. It can reach host files, the host network and credentials it is given.--command server.--skip-ssrf-check unless the provider and its redirects are fully trusted. If --url resolves to a private, loopback, link-local or cloud-metadata address, sbx registers but warns; stop and confirm with the user.mcp:-prefixed secrets stay on the host and are not injected into sandboxes.sbx mcp inspect <name> and re-authorize with sbx mcp auth <name>. If a server refuses dynamic client registration, register a client with the provider and pass --client-id (--oauth-authorization-server if needed) to sbx mcp add.sbx secret set prompts for it, so no token enters shell history:sbx mcp add acme --url https://mcp.acme.com/mcp \
--header 'Authorization: Bearer ${api-key}'
sbx secret set mcp:acme:api-key
sbx mcp inspect acme # shows header templates and whether secrets are set, never values
${api-key} reads mcp:acme:api-key), not environment variables. Credential headers such as Authorization must use a placeholder. Custom headers need a remote HTTP endpoint and cannot be used with --command or --local.sbx secret set using the same name. After setting, changing or removing a header secret, stop and restart the sandbox or restart sandboxd; an existing gateway keeps the old value and a server skipped for a missing secret is not retried. Changing the server endpoint requires setting the secret again for the new endpoint.sbx policy, not by MCP registration. Delegate policy and general secret commands to docker-sandboxes-network-credentials.sbx mcp inspect <name> for one registration; read sbx mcp ls --help first for the host listing, since its columns are not documented in the sources used here.sbx mcp unload <name> --sandbox <sb> (0.48.0+, local gateway only). It removes the saved attachment, so the server is not restored after a restart; the host registration, credentials and other sandboxes are untouched.sbx mcp rm <name>. It does not detach servers from sandboxes that already loaded them, and it keeps header secrets (it prints the removal commands, for example sbx secret rm mcp:acme:api-key). Unload from each sandbox first, then rm, then remove secrets deliberately.unload and rm. If it does, rm leaves that attachment in place.sbx mcp unload <name> --sandbox <sb> for each of those sandboxes.sbx mcp rm <name>. After this, the agent can no longer find it.unload accepts a name whose registration was already removed is unverified (checks/verification.md step 5). If it is rejected, stop that sandbox with sbx stop and escalate rather than resuming it.--static-mcp none.mcp.useServerNamePrefixes (0.51.0+) when tool names collide across servers: sbx settings set mcp.useServerNamePrefixes true. Settings are host-global; read the current value before changing it and restore it afterwards. The documented set command is sbx settings set; get/unset syntax is not verified here, so run sbx settings --help.add: the server was never attached. Run sbx mcp load, or create a new sandbox with --static-mcp.sandboxd.command servers from an environment file ask for approval: expected (0.50.0+); see docker-sandboxes-env.Verify with checks/verification.md after any registration, load or removal.
docker-sandboxes-lifecycle.sbx secret credentials, use docker-sandboxes-network-credentials.mcp block in sbxenv.yaml, use docker-sandboxes-env.docker-agent-config.docker-docs.skill.yaml — routing metadata for this skill.agents/openai.yaml — Codex discovery metadata.references/sbx-mcp-reference.md — documented sbx mcp subcommands, selected flags, versions and scope table.references/sources.md — claim-level evidence and unverified items.checks/verification.md — Verification runbook for registering, loading, unloading and removing MCP servers in a local sandbox.Use this skill when giving an agent in a local Docker Sandbox (sbx) access to MCP servers, even if the user just says "my sandboxed Claude can't see the GitHub tools", "add Notion MCP to my sandbox",
---name: docker-sandboxes-mcp-gatewaydescription: Use this skill when giving an agent in a local Docker Sandbox (sbx) access to MCP servers, even if the user…---# skills/docker-sandboxes-mcp-gateway/SKILL.md總覽
Use this skill when giving an agent in a local Docker Sandbox (sbx) access to MCP servers, even if the user just says "my sandboxed Claude can't see the GitHub tools", "add Notion MCP to my sandbox", or "take this MCP server away from the sandbox". Covers sbx mcp add/load/unload/ls/rm/auth/inspect, static vs dynamic mode, --static-mcp, host-side execution, OAuth and header secrets, untrusted URLs, and removal order.
常見問題
從發布者下載 skills/docker-sandboxes-mcp-gateway/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/docker/skills。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。