Single exec tool running caller Python in a network-isolated locked-down sandbox.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like Exec Sandbox.
{
"MCP_EXEC_TRANSPORT": "stdio",
"MCP_EXEC_DEFAULT_TIMEOUT_S": "30",
"MCP_EXEC_MAX_TIMEOUT_S": "300",
"MCP_EXEC_MAX_OUTPUT_BYTES": "1048576",
"MCP_EXEC_MAX_STDIN_BYTES": "1048576",
"MCP_EXEC_AUTH_TOKEN": "YOUR_SECRET_VALUE"
}Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-inhuman-mcp-exec": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-io-github-inhuman-mcp-exec"
],
"env": {
"MCP_EXEC_TRANSPORT": "stdio",
"MCP_EXEC_DEFAULT_TIMEOUT_S": "30",
"MCP_EXEC_MAX_TIMEOUT_S": "300",
"MCP_EXEC_MAX_OUTPUT_BYTES": "1048576",
"MCP_EXEC_MAX_STDIN_BYTES": "1048576",
"MCP_EXEC_AUTH_TOKEN": "YOUR_SECRET_VALUE"
}
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Exec Sandbox is an MCP server for Single exec tool running caller Python in a network-isolated locked-down sandbox.. It supports STDIO transport.
Use the client-specific config in Install and add it to your MCP-compatible client.
Choose the Claude Desktop tab in Install and copy the config into Claude Desktop's MCP server settings.
Choose the Claude Code tab in Install and copy the config into Claude Code's MCP server settings.
Choose the Codex tab in Install and copy the config into Codex's MCP server settings.
Choose the Cursor or VS Code tab in Install and copy the config into Cursor or VS Code's MCP server settings.
Exec Sandbox uses STDIO transport. Use the package or command config in Install.
Exec Sandbox inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
Exec Sandbox does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
docker.io/idconstruct/mcp-exec:v0.5.4stdio | oci | Not captured | Env: MCP_EXEC_TRANSPORT Env: MCP_EXEC_DEFAULT_TIMEOUT_S Env: MCP_EXEC_MAX_TIMEOUT_S Env: MCP_EXEC_MAX_OUTPUT_BYTES Env: MCP_EXEC_MAX_STDIN_BYTES Env: MCP_EXEC_AUTH_TOKEN secret |