Skip to content
mcp/harbor
Grok

Exec Sandbox for Grok

io.github.inhuman/mcp-exec

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

client:Grok transport:stdio runtime:oci

Install Exec Sandbox in Grok

.mcp.json (in your project root)

Held in this page only — never stored, logged, or sent anywhere but back to your screen. 

{
  "mcpServers": {
    "mcp-exec": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "docker.io/idconstruct/mcp-exec:v0.5.4"
      ],
      "env": {
        "MCP_EXEC_TRANSPORT": "<MCP_EXEC_TRANSPORT>",
        "MCP_EXEC_DEFAULT_TIMEOUT_S": "<MCP_EXEC_DEFAULT_TIMEOUT_S>",
        "MCP_EXEC_MAX_TIMEOUT_S": "<MCP_EXEC_MAX_TIMEOUT_S>",
        "MCP_EXEC_MAX_OUTPUT_BYTES": "<MCP_EXEC_MAX_OUTPUT_BYTES>",
        "MCP_EXEC_MAX_STDIN_BYTES": "<MCP_EXEC_MAX_STDIN_BYTES>",
        "MCP_EXEC_AUTH_TOKEN": "<MCP_EXEC_AUTH_TOKEN>"
      }
    }
  }
}

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Exec Sandbox in other clients

Exec Sandbox MCP server