Install
"command": "npx",
"args": ["-y", "node-code-sandbox-mcp"],Who it is for
If you can already run Docker locally and want MCP to drop an arbitrary piece of JavaScript into a temporary container—and, when needed, install npm dependencies on the spot—this server matches. Officially it is a Node.js service that implements Model Context Protocol, built to run arbitrary JavaScript in short-lived Docker containers and to support installing npm dependencies immediately.
It is not suitable on a machine where Docker is not installed or not running. The current excerpt only describes two capability kinds—“one-shot script” and “Detached Mode keeps the container alive after the script ends”—and does not give tool function names, a parameter table, or resource limits. If you need a call signature you can copy as-is, the evidence stops here.
The first use should pick a one-shot, throw-away container rather than leaving the container alive. Running arbitrary scripts is a write-oriented action: it creates a container, runs the code you supply, and may pull dependencies.
First try in 3 minutes
First confirm Docker is installed and running. The official recommended main path is to put the following block in the MCP client's server config; do not write a second installer beside it:
"command": "npx",
"args": ["-y", "node-code-sandbox-mcp"],
Put this block in the MCP client config location you already use. The excerpt does not hard-code a config file name, so do not treat any particular client path as confirmed. Save and reload that server.
Before you act, check two things: the Docker daemon is actually running; and the script you are about to submit is the content you intend to execute. The side effect is that the service will create a one-shot Docker container, run this JavaScript inside it, and may install npm dependencies on the spot. After those two checks, send a request to “run a one-shot JS script in a brand-new disposable container.” Do not turn on Detached Mode the first time.
The success signal is that this request runs along the one-shot container path, not a message that Docker is not running or that npx cannot start node-code-sandbox-mcp. This is not a zero-risk read: a container, script execution, and dependency installation will happen, and it is not the same as no network or no privacy boundary.
Use cases
Case 1: Run a throw-away script. The excerpt states you can run a one-shot JS script in a brand-new disposable container. Confirm the script content first, then submit. What can be confirmed is that this script is executed in a new container; return fields, stdout format, and tool names do not appear in the current excerpt, so do not treat specific fields as confirmed.
Case 2: You need the container to stay alive after the script ends, for example a long-running service. The excerpt states Detached Mode can keep the container alive after script execution. The side effects are larger than the one-shot path: the container remains. The excerpt gives no stop, delete, or revoke steps, so do not write “shut down the container” as an official recovery path. Take this path only when you explicitly need the container to keep living.
These two cases correspond to “one-shot execution” and “keep-alive after execution.” Do not merge them into one unconfirmed call.
Limits
The precondition is that Docker must already be installed and running. The main install path is npx -y node-code-sandbox-mcp. Confirmed capabilities: run a piece of JS in a brand-new disposable container; and Detached Mode keeps the container alive after the script ends. Immediate npm dependency install is also written into the overall description, but install scope, cache location, and network policy do not appear in the current excerpt.
The official page is https://github.com/alfonsograziano/node-code-sandbox-mcp . The excerpt does not give credential fields, a client list, CPU or memory numbers, or revoke or cleanup commands. Do not treat container execution as freely rollbackable, and do not invent missing tool names and parameters.