GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Sandboxed shell exec for MCP clients: run untrusted agent commands in a gVisor container.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
IRONCLAW_CONTROLPLANE_URL, IRONCLAW_API_TOKENValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"ironclaw": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"IRONCLAW_CONTROLPLANE_URL",
"-e",
"IRONCLAW_API_TOKEN",
"ghcr.io/ironsecco/ironclaw-mcp:v0.1.569"
],
"env": {
"IRONCLAW_CONTROLPLANE_URL": "your-value",
"IRONCLAW_API_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add ironclaw --env IRONCLAW_CONTROLPLANE_URL=your-value --env IRONCLAW_API_TOKEN=your-value -- docker run -i --rm -e IRONCLAW_CONTROLPLANE_URL -e IRONCLAW_API_TOKEN ghcr.io/ironsecco/ironclaw-mcp:v0.1.569Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ironclaw": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"IRONCLAW_CONTROLPLANE_URL",
"-e",
"IRONCLAW_API_TOKEN",
"ghcr.io/ironsecco/ironclaw-mcp:v0.1.569"
],
"env": {
"IRONCLAW_CONTROLPLANE_URL": "your-value",
"IRONCLAW_API_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"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.569"
],
"env": {
"IRONCLAW_CONTROLPLANE_URL": "your-value",
"IRONCLAW_API_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account IronSecCo, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: IRONCLAW_CONTROLPLANE_URL, IRONCLAW_API_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.569) reached the registry 6 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Each one runs sealed in a sandbox that provably cannot phone home, read your host, or rewrite its own rules.
IronClaw runs autonomous AI agents on infrastructure you control, reached through the chat apps you already use. Each agent can read, write, schedule, and reply like any assistant, but it lives inside a sealed sandbox with network=none: it reaches the model only through a host proxy, and it cannot change its own configuration. It is for anyone who wants what agents can do without handing an autonomous program the keys to their machine.
Now on the GitHub Marketplace. The
ironctl scancontainment grader ships as a
GitHub Action: drop one
line into a workflow and every pull request gets a 0 to 100 sandbox isolation scorecard as
a sticky comment. Local, read-only, credential-free.
`yaml
# .github/workflows/scan.yml
- uses: IronSecCo/ironclaw@v1
with:
target: my-container # a container, compose service, or k8s manifest
`
Report-only by default; set
min-score: 90to gate merges. See scan in CI.
Watch it catch a real escape. A fully-jailbroken agent inside a real sandbox tries to phone home, read the host filesystem, and seize the host through the Docker socket. Each attempt is denied at the isolation boundary, then a containment summary prints. One command, zero credentials, reduced-motion friendly. examples/live-containment/run.sh
⭐ Like the idea of agents you do not have to trust? [Star the repo](https://github.com/IronSecCo/ironclaw) so it is one click to follow along and easier for the next person to find. Then run the exact demo above in 30 seconds, no signup and no API key.
Make sure the Docker daemon is running (start Docker Desktop, or sudo systemctl start docker on Linux), then paste one block:
git clone https://github.com/IronSecCo/ironclaw.git && cd ironclaw
examples/live-containment/run.sh # builds the sandbox once, engages a real sandbox, proves it holds
That single command runs the whole secured path on your laptop: it starts the offline mock-agent control-plane (no API key), engages a real per-session sandbox, lets a jailbroken agent try to break out, and prints the containment summary you saw above. Want to chat with an agent in a browser first? Run hello-ironclaw or the zero-credential quickstart. Production seals each sandbox with gVisor and network=none.
[!WARNING]
Alpha software, work in progress. Please read before relying on it.
- It's an alpha. Flags, the on-disk format, and the HTTP/contract surfaces can still change without notice or a migration path. Don't point it at anything you can't afford to lose.
- Not every feature is tested end-to-end. The control-plane, gateway, and encrypted-queue core have real coverage (800+ Go tests plus a black-box parity suite); channel adapters, some tools, multi-provider routing, and a live sandbox launch are exercised more lightly. Treat anything outside the tested core as experimental.
macOS gets a weaker sandbox boundary than Linux+gVisor, and native Windows can't run the agent sandbox at all (use WSL2). See Platform support.
The security model, in one line: each sandboxed agent runs with
network=none, reaches the
model only through a host proxy, and cannot change its own configuration. Every capability
change is held at a gateway for a human decision. The full design is in the
architecture overview and the threat model.
Zero credentials, one command. The offline mock-agent runs the full chat to per-session sandbox to reply path with no API key. Production seals each sandbox with gVisor and network=none . Quickstart
Zero-cred demo, connect a real provider, first approved task. The one credential step keeps the key host-side; every agent change is held at the gateway for a human, then written to the append-only audit log. Animation freezes on the final frame under prefers-reduced-motion . Quickstart
One command installs the two host binaries (ironctl + ironclaw-controlplane); in dev mode the control-plane serves its API at `http://127.0.0.1:8787`. From a cold machine, you'll have a capability change waiting at the security gateway in under two minutes:
# 1. Install — detects your OS/arch and verifies the SHA-256 checksum before installing
curl -fsSL https://raw.githubusercontent.com/IronSecCo/ironclaw/main/scripts/install.sh | sh
export IRONCLAW_API_TOKEN=$(openssl rand -hex 32) ironclaw-controlplane --dev --api-addr 127.0.0.1:8787 &
ironctl change submit --kind persona --group dev-agent --by you ironctl change pending # see it waiting ironctl change approve --by you # apply it
On Windows, irm https://raw.githubusercontent.com/IronSecCo/ironclaw/main/scripts/install.ps1 | iex installs the host binaries (ironclaw-controlplane.exe + ironctl.exe) and --dev runs, but the agent sandbox needs WSL2 or Linux — see Windows via WSL2. Version pinning, system-wide installs, and building from source are all in Installation.
Run the hardened control-plane on a PaaS in ~2 minutes with zero local tooling — the approval gateway, encrypted per-session queues, host-side credential custody, and the web console:
These PaaS paths run the control-plane only — a single container has no gVisor and
no Docker socket, so agent sandboxes don't launch there (same boundary as the
hardened Compose path). For full agent isolation use
a gVisor host or k8s node. Details + env in the
deployment guide (Path D).
This is a feature, not a missing dashboard. Every capability is a documented HTTP endpoint and an ironctl subcommand, so IronClaw is scriptable, auditable, and CI-frien
Only the beginning is shown; read the rest in the repo