Skip to content
MCP server

Exec Sandbox

Single exec tool running caller Python in a network-isolated locked-down sandbox.

Runs locallyStatus and history
Install
Pricing
Open source
Runs
Locally
Version
0.5.4
Listing updated
6 days ago

About Exec Sandbox

Exec Sandbox is an open-source MCP server. It runs locally on your machine and is started by your AI client.

Install

Run in a terminal

claude mcp add mcp-exec --env MCP_EXEC_AUTH_TOKEN='<MCP_EXEC_AUTH_TOKEN>' -- docker run -i --rm -e MCP_EXEC_AUTH_TOKEN docker.io/idconstruct/mcp-exec:v0.5.4

Add to claude_desktop_config.json

{
  "mcpServers": {
    "mcp-exec": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_EXEC_AUTH_TOKEN",
        "docker.io/idconstruct/mcp-exec:v0.5.4"
      ],
      "env": {
        "MCP_EXEC_AUTH_TOKEN": "<MCP_EXEC_AUTH_TOKEN>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "mcp-exec": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_EXEC_AUTH_TOKEN",
        "docker.io/idconstruct/mcp-exec:v0.5.4"
      ],
      "env": {
        "MCP_EXEC_AUTH_TOKEN": "<MCP_EXEC_AUTH_TOKEN>"
      }
    }
  }
}

Add to .vscode/mcp.json

{
  "servers": {
    "mcp-exec": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_EXEC_AUTH_TOKEN",
        "docker.io/idconstruct/mcp-exec:v0.5.4"
      ],
      "env": {
        "MCP_EXEC_AUTH_TOKEN": "<MCP_EXEC_AUTH_TOKEN>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "mcp-exec": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_EXEC_AUTH_TOKEN",
        "docker.io/idconstruct/mcp-exec:v0.5.4"
      ],
      "env": {
        "MCP_EXEC_AUTH_TOKEN": "<MCP_EXEC_AUTH_TOKEN>"
      }
    }
  }
}

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "mcp-exec": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_EXEC_AUTH_TOKEN",
        "docker.io/idconstruct/mcp-exec:v0.5.4"
      ],
      "env": {
        "MCP_EXEC_AUTH_TOKEN": "<MCP_EXEC_AUTH_TOKEN>"
      }
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

Configuration

  • MCP_EXEC_TRANSPORTMCP transport. Must be 'stdio' for direct docker/stdio use.
  • MCP_EXEC_DEFAULT_TIMEOUT_SDefault wall-clock timeout per exec, seconds.
  • MCP_EXEC_MAX_TIMEOUT_SMaximum wall-clock timeout a caller may request, seconds.
  • MCP_EXEC_MAX_OUTPUT_BYTESCap on combined stdout/stderr before truncation.
  • MCP_EXEC_MAX_STDIN_BYTESCap on stdin passed to the sandboxed code.
  • MCP_EXEC_AUTH_TOKENOptional X-MCP-AUTH token (http/sse transports only).

Pricing

Open source

Exec Sandbox FAQ

Is Exec Sandbox free?

Yes. Exec Sandbox is open source, so you can use and self-host it for free.

How do I add Exec Sandbox to Claude Code?

Run this command in your terminal: claude mcp add mcp-exec --env MCP_EXEC_AUTH_TOKEN='<MCP_EXEC_AUTH_TOKEN>' -- docker run -i --rm -e MCP_EXEC_AUTH_TOKEN docker.io/idconstruct/mcp-exec:v0.5.4

Where this comes from

  • Description: from the official MCP Registry entry.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers