rarcanelisted

# rarcane Use the `arcane` MCP tool for Arcane Docker management. Prefer read actions first. For destructive actions, explain the likely effect and pass `params.confirm=true` only after the user has clearly asked for the operation. ## Common Calls ```text mcp__rarcane__arcane(action="status") mcp__rarcane__arcane(action="elicit_name") mcp__rarcane__arcane(action="scaffold_intent") mcp__rarcane__arcane(action="container", subaction="list", envId="default") mcp__rarcane__arcane(action="project", subaction="list", envId="default") mcp__rarcane__arcane(action="system", subaction="docker-info", envId="default") mcp__rarcane__arcane(action="container", subaction="stop", envId="default", id="nginx", params={"confirm":true}) ``` ## Domains `elicit_name` and `scaffold_intent` are MCP-only elicitation workflows. The latter returns a side-effect-free planning contract; it does not grant file mutation permission. | Domain | Typical Read Actions | Typical Write Actions | |---|---|---| | `environment` | `list`, `get`, `test` | `create`, `update`, `delete` | | `project` | `list`, `get` | `create`, `up`, `down`, `restart`, `pull`, `destroy`, `redeploy`, `build` | | `container` | `list`, `get`, `stats` | `create`, `start`, `stop`, `restart`, `update`, `delete` | | `image` | `list`, `get` | `pull`, `delete`, `prune`, `scan` | | `network` | `list`, `get` | `create`, `delete`, `prune` | | `volume` | `list`, `get`, `browse`, `list-backups` | `create`, `delete`, `prune`, backup and restore a