Ironclaw

Ironclaw runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/ironsecco/ironclaw-mcp:v0.1.535. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm -e IRONCLAW_CONTROLPLANE_URL -e IRONCLAW_API_TOKEN ghcr.io/ironsecco/ironclaw-mcp:v0.1.535. It reads these environment variables: IRONCLAW_CONTROLPLANE_URL (required) and IRONCLAW_API_TOKEN (required, secret); set them in the client's configuration for this server. Required arguments: -e and -e.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "ironclaw": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "IRONCLAW_CONTROLPLANE_URL",
        "-e",
        "IRONCLAW_API_TOKEN",
        "ghcr.io/ironsecco/ironclaw-mcp:v0.1.535"
      ],
      "env": {
        "IRONCLAW_CONTROLPLANE_URL": "<value>",
        "IRONCLAW_API_TOKEN": "<secret>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect