Skip to main content
Glama
mozicim

Node Code Sandbox MCP

by mozicim

run_js

Execute JavaScript code in a secure Node.js sandbox container. Install npm dependencies, run ESModules, and manage persistent files for complex workflows. Manually stop the sandbox to free resources after execution.

Instructions

Install npm dependencies and run JavaScript code inside a running sandbox container. After running, you must manually stop the sandbox to free resources. The code must be valid ESModules (import/export syntax). Best for complex workflows where you want to reuse the environment across multiple executions. When reading and writing from the Node.js processes, you always need to read from and write to the "./files" directory to ensure persistence on the mounted volume.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
container_idYesDocker container identifier
dependenciesNoA list of npm dependencies to install before running the code. Each item must have a `name` (package) and `version` (range). If none, returns an empty array.
codeYesJavaScript code to run inside the container.
listenOnPortNoIf set, leaves the process running and exposes this port to the host.

Implementation Reference

  • The main handler function that installs npm dependencies (if provided) and executes the given JavaScript code inside the specified Docker container. Handles both one-shot execution and long-running servers (with listenOnPort). Detects and reports file changes in the workspace.
    export default async function runJs({
      container_id,
      code,
      dependencies = [],
      listenOnPort,
    }: {
      container_id: string;
      code: string;
      dependencies?: DependenciesArray;
      listenOnPort?: number;
    }): Promise<McpResponse> {
      if (!isDockerRunning()) {
        return { content: [textContent(DOCKER_NOT_RUNNING_ERROR)] };
      }
    
      const telemetry: Record<string, unknown> = {};
      const dependenciesRecord: Record<string, string> = Object.fromEntries(
        dependencies.map(({ name, version }) => [name, version])
      );
    
      // Create workspace in container
      const localWorkspace = await prepareWorkspace({ code, dependenciesRecord });
      execSync(`docker cp ${localWorkspace.name}/. ${container_id}:/workspace`);
    
      let rawOutput: string = '';
    
      // Generate snapshot of the workspace
      const snapshotStartTime = Date.now();
      const snapshot = await getSnapshot(getMountPointDir());
    
      if (listenOnPort) {
        if (dependencies.length > 0) {
          const installStart = Date.now();
          const installOutput = execSync(
            `docker exec ${container_id} /bin/sh -c ${JSON.stringify(
              `npm install --omit=dev --prefer-offline --no-audit --loglevel=error`
            )}`,
            { encoding: 'utf8' }
          );
          telemetry.installTimeMs = Date.now() - installStart;
          telemetry.installOutput = installOutput;
        } else {
          telemetry.installTimeMs = 0;
          telemetry.installOutput = 'Skipped npm install (no dependencies)';
        }
    
        const { error, duration } = safeExecNodeInContainer({
          containerId: container_id,
          command: `nohup node index.js > output.log 2>&1 &`,
        });
        telemetry.runTimeMs = duration;
        if (error) return getContentFromError(error, telemetry);
    
        await waitForPortHttp(listenOnPort);
        rawOutput = `Server started in background; logs at /output.log`;
      } else {
        if (dependencies.length > 0) {
          const installStart = Date.now();
          const fullCmd = `npm install --omit=dev --prefer-offline --no-audit --loglevel=error`;
          const installOutput = execSync(
            `docker exec ${container_id} /bin/sh -c ${JSON.stringify(fullCmd)}`,
            { encoding: 'utf8' }
          );
          telemetry.installTimeMs = Date.now() - installStart;
          telemetry.installOutput = installOutput;
        } else {
          telemetry.installTimeMs = 0;
          telemetry.installOutput = 'Skipped npm install (no dependencies)';
        }
    
        const { output, error, duration } = safeExecNodeInContainer({
          containerId: container_id,
        });
    
        if (output) rawOutput = output;
        telemetry.runTimeMs = duration;
        if (error) return getContentFromError(error, telemetry);
      }
    
      // Detect the file changed during the execution of the tool in the mounted workspace
      // and report the changes to the user
      const changes = await detectChanges(
        snapshot,
        getMountPointDir(),
        snapshotStartTime
      );
    
      const extractedContents = await changesToMcpContent(changes);
      localWorkspace.removeCallback();
    
      return {
        content: [
          textContent(`Node.js process output:\n${rawOutput}`),
          ...extractedContents,
          textContent(`Telemetry:\n${JSON.stringify(telemetry, null, 2)}`),
        ],
      };
    }
  • Zod schema defining the input parameters for the run_js tool: container_id, dependencies (array of {name,version}), code, and optional listenOnPort.
    export const argSchema = {
      container_id: z.string().describe('Docker container identifier'),
      // We use an array of { name, version } items instead of a record
      // because the OpenAI function-calling schema doesn’t reliably support arbitrary
      // object keys. An explicit array ensures each dependency has a clear, uniform
      // structure the model can populate.
      // Schema for a single dependency item
      dependencies: z
        .array(NodeDependency)
        .default([])
        .describe(
          'A list of npm dependencies to install before running the code. ' +
            'Each item must have a `name` (package) and `version` (range). ' +
            'If none, returns an empty array.'
        ),
      code: z.string().describe('JavaScript code to run inside the container.'),
      listenOnPort: z
        .number()
        .optional()
        .describe(
          'If set, leaves the process running and exposes this port to the host.'
        ),
    };
  • src/server.ts:66-73 (registration)
    Registration of the 'run_js' tool on the MCP server using server.tool(), providing name, long description, input schema, and handler function.
      'run_js',
      `Install npm dependencies and run JavaScript code inside a running sandbox container.
      After running, you must manually stop the sandbox to free resources.
      The code must be valid ESModules (import/export syntax). Best for complex workflows where you want to reuse the environment across multiple executions.
      When reading and writing from the Node.js processes, you always need to read from and write to the "./files" directory to ensure persistence on the mounted volume.`,
      runJsSchema,
      runJs
    );
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden and adds significant behavioral context beyond the input schema. It discloses that resources must be manually freed after running, specifies ESModules requirement, explains persistence via the './files' directory, and hints at environment reuse. It doesn't mention error handling or output format, but covers key operational traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded with the core purpose. Every sentence adds value: installation/running, manual cleanup, ESModules requirement, use case, and file I/O guidance. It could be slightly more structured but avoids redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (sandbox execution with dependencies) and lack of annotations/output schema, the description does well to cover key aspects: purpose, usage context, behavioral constraints, and file persistence. It doesn't detail error responses or output structure, but provides enough for basic agent understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds minimal parameter-specific semantics: it implies 'dependencies' are npm packages and 'code' is JavaScript, but doesn't elaborate beyond what the schema already documents. No contradictions or significant enhancements are present.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('Install npm dependencies and run JavaScript code') and resource ('inside a running sandbox container'). It distinguishes from sibling tools like 'run_js_ephemeral' by emphasizing reusability across multiple executions and the need to manually stop the sandbox.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance: 'Best for complex workflows where you want to reuse the environment across multiple executions.' It implicitly contrasts with ephemeral alternatives by noting the need to manually stop the sandbox, and it specifies prerequisites like valid ESModules syntax and file I/O requirements.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mozicim/node-code-sandbox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server