ironclaw — Claude Code MCP server: what it does, how to install
ironclaw runs agent commands inside a gVisor container. Use it when a command should run without direct access to the host system.
claude mcp add --env IRONCLAW_CONTROLPLANE_URL=<IRONCLAW_CONTROLPLANE_URL> --env IRONCLAW_API_TOKEN=<IRONCLAW_API_TOKEN> --transport stdio ironclaw -- docker run -i --rm -e IRONCLAW_CONTROLPLANE_URL -e IRONCLAW_API_TOKEN ghcr.io/ironsecco/ironclaw-mcp:v0.1.557What ironclaw does
ironclaw exposes command execution to an MCP client through a gVisor container. The project describes the sandbox as using network=none; model traffic goes through a host proxy, and the agent cannot alter its own configuration.
To connect it to Claude Code, the install command starts the ghcr.io/ironsecco/ironclaw-mcp:v0.1.557 Docker image and passes IRONCLAW_CONTROLPLANE_URL and IRONCLAW_API_TOKEN. Docker, a control-plane URL, and a token are required. The project is alpha software, and its flags and storage format may change, so avoid relying on it for data you cannot afford to lose.
What it helps with
- run an agent command inside a gVisor container
- limit an agent command's access to the host
- connect command execution to an MCP client through a control plane
Example prompts for the agent
- Run this untrusted command in the isolated container:
... - Try the command in the sandbox and check whether it can read the host filesystem.
- Run this agent command through ironclaw without giving the container network access.
How to install ironclaw
Platform CLI
claude mcp add --env IRONCLAW_CONTROLPLANE_URL=<IRONCLAW_CONTROLPLANE_URL> --env IRONCLAW_API_TOKEN=<IRONCLAW_API_TOKEN> --transport stdio ironclaw -- docker run -i --rm -e IRONCLAW_CONTROLPLANE_URL -e IRONCLAW_API_TOKEN ghcr.io/ironsecco/ironclaw-mcp:v0.1.557Replace <…> with your own values
Platform CLI
codex mcp add ironclaw --env IRONCLAW_CONTROLPLANE_URL=<IRONCLAW_CONTROLPLANE_URL> --env IRONCLAW_API_TOKEN=<IRONCLAW_API_TOKEN> -- docker run -i --rm -e IRONCLAW_CONTROLPLANE_URL -e IRONCLAW_API_TOKEN ghcr.io/ironsecco/ironclaw-mcp:v0.1.557Replace <…> with your own values
Config file
{
"mcpServers": {
"ironclaw": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"IRONCLAW_CONTROLPLANE_URL",
"-e",
"IRONCLAW_API_TOKEN",
"ghcr.io/ironsecco/ironclaw-mcp:v0.1.557"
],
"env": {
"IRONCLAW_CONTROLPLANE_URL": "<IRONCLAW_CONTROLPLANE_URL>",
"IRONCLAW_API_TOKEN": "<IRONCLAW_API_TOKEN>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"ironclaw": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"IRONCLAW_CONTROLPLANE_URL",
"-e",
"IRONCLAW_API_TOKEN",
"ghcr.io/ironsecco/ironclaw-mcp:v0.1.557"
],
"env": {
"IRONCLAW_CONTROLPLANE_URL": "<IRONCLAW_CONTROLPLANE_URL>",
"IRONCLAW_API_TOKEN": "<IRONCLAW_API_TOKEN>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e IRONCLAW_CONTROLPLANE_URL=<IRONCLAW_CONTROLPLANE_URL> -e IRONCLAW_API_TOKEN=<IRONCLAW_API_TOKEN> ironclaw docker run -i --rm -e IRONCLAW_CONTROLPLANE_URL -e IRONCLAW_API_TOKEN ghcr.io/ironsecco/ironclaw-mcp:v0.1.557Replace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about ironclaw
How do I install ironclaw in Claude Code?
Run `claude mcp add --env IRONCLAW_CONTROLPLANE_URL=<IRONCLAW_CONTROLPLANE_URL> --env IRONCLAW_API_TOKEN=<IRONCLAW_API_TOKEN> --transport stdio ironclaw -- docker run -i --rm -e IRONCLAW_CONTROLPLANE_URL -e IRONCLAW_API_TOKEN ghcr.io/ironsecco/ironclaw-mcp:v0.1.557`. You need Docker, a control-plane URL, and an API token.
What does ironclaw do?
It lets an MCP client run commands in a gVisor container. The project describes the container network as network=none.
What does ironclaw need to run?
For Claude Code, you need Docker, IRONCLAW_CONTROLPLANE_URL, and IRONCLAW_API_TOKEN. The project is alpha software, and its flags and storage format can change.
