Arcane Docker and Compose management over MCP and CLI with authenticated stdio and HTTP.
It exposes one MCP tool, arcane, plus the rarcane CLI. Agents can inspect
Arcane environments, manage compose projects, containers, images, networks,
volumes, registries, GitOps syncs, image updates, vulnerability findings, and
system operations through stdio MCP, Streamable HTTP MCP, or direct shell
commands.
Rust MCP server and CLI for Arcane Docker and container management.
30-second path: set RARCANE_API_URL and RARCANE_API_KEY, then run
npx -y @dinglebear/rarcane status -> start loopback HTTP with
RARCANE_MCP_HOST=127.0.0.1 npx -y @dinglebear/rarcane serve -> call tools/call with
{"action":"status"}.
Status: operational RMCP upstream-client server. Write-capable; destructive
Docker and Arcane operations require explicit confirmation. HTTP MCP supports
loopback dev mode, static bearer tokens, and Google OAuth through lab-auth.
Not for: replacing Arcane, bypassing Docker or Arcane authorization,
running arbitrary shell commands, storing registry or Git credentials,
multi-tenant isolation, or passing Arcane API keys through MCP tool arguments.
RARCANE_*, RARCANE_MCP_*, RARCANE_RMCP_* for npm launcher controls
The repo and npm package use the upstream service name, while the shipped
binary keeps the historical Rust CLI name rarcane. The MCP server may be
registered as rarcane, but the tool clients call is arcane.
Capabilities And Boundaries
Read Arcane status plus Docker environment, project, container, image,
network, volume, registry, GitOps, update, vulnerability, and system state.
Create, update, start, stop, restart, delete, prune, deploy, sync, scan, and
back up supported Arcane resources through action/subaction dispatch.
Enforce action scopes and destructive-operation confirmation before forwarding
write operations to Arcane.
Expose the quick_start prompt and rarcane://schema/mcp-tool resource for
client-side discovery.
Provide setup, doctor, and watch commands for local plugin/runtime checks.
Do not put RARCANE_API_KEY, registry credentials, Git credentials, OAuth
secrets, SSH keys, passwords, or upstream bearer tokens in MCP tool arguments.
Use env, config files, or the MCP client's secret storage.
MCP callers never provide credentials, tokens, keys, or secrets as action
arguments.
Runtime Surfaces
Surface
Status
Entry point
Purpose
MCP stdio
Supported
rarcane mcp, npx -y @dinglebear/rarcane mcp
Local child-process MCP clients.
MCP HTTP
Supported
rarcane serve, POST /mcp
Streamable HTTP MCP for local or shared server deployments.
CLI
Supported
rarcane <command>
Scriptable parity and debugging.
Prompt
Supported
quick_start
Guides a client through status and public help.
Resource
Supported
rarcane://schema/mcp-tool
JSON schema for the arcane tool.
REST API
Not shipped
N/A
Arcane already owns the REST API.
Web UI
Not shipped
N/A
Arcane already owns the web UI.
MCP Tool Reference
One MCP tool is exposed: arcane. Pass the required action argument and, for
most domains, a required subaction.
rarcane exposes the same service layer as the MCP tool:
rarcane status
rarcane help --domain container
rarcane call --action container --subaction list --env-id default
rarcane call --action system --subaction docker-info --env-id default
rarcane call --action container --subaction stop --env-id default --id my-container --confirm
rarcane doctor --json
rarcane watch --url http://127.0.0.1:40110
rarcane setup check
rarcane setup repair
--params-json accepts action-specific JSON payloads. Do not use it to pass
credentials.
Configuration
Host installs read ~/.rarcane/.env, ~/.rarcane/config.toml, and process env.
Containers read /data/.env, /data/config.toml, and process env.
Variable
Default
Purpose
RARCANE_API_URL
unset
Arcane API base URL.
RARCANE_API_KEY
unset
Arcane API key or bearer token.
RARCANE_MCP_HOST
127.0.0.1
HTTP bind host.
RARCANE_MCP_PORT
40110
HTTP bind port.
RARCANE_MCP_SERVER_NAME
arcane-rmcp
Advertised MCP server name.
RARCANE_MCP_TOKEN
unset
Static bearer token for HTTP MCP.
RARCANE_MCP_NO_AUTH
false
Disable auth only for loopback development.
RARCANE_NOAUTH
false
Trust an upstream gateway to enforce auth.
RARCANE_MCP_ALLOWED_HOSTS
unset
Extra accepted Host header values.
RARCANE_MCP_ALLOWED_ORIGINS
unset
Extra accepted CORS origins.
RARCANE_MCP_PUBLIC_URL
unset
Public base URL for OAuth issuer metadata.
RARCANE_MCP_AUTH_MODE
bearer
bearer or oauth.
RARCANE_MCP_ALLOW_DESTRUCTIVE
false
Bypass the per-call destructive confirmation gate. Do not set in shared deployments.
RARCANE_HOME
~/.rarcane
Config/appdata root override.
RUST_LOG
info
Log filter.
Authentication
Stdio MCP runs as a local trusted child process and does not use HTTP auth.
HTTP MCP auth policy:
State
Condition
Behavior
Loopback dev
Bound to 127.0.0.1, localhost, or [::1]
Local unauthenticated development is allowed.
Mounted bearer
Non-loopback with RARCANE_MCP_TOKEN
Requires Authorization: Bearer <token> and action scopes.
Mounted OAuth
RARCANE_MCP_AUTH_MODE=oauth
Uses Google OAuth/JWT through lab-auth; static bearer remains supported.
Trusted gateway
RARCANE_NOAUTH=true
Assumes a reverse proxy or gateway already enforced auth.
OAuth mode uses the RARCANE_MCP_* Google OAuth variables documented in
docs/CONFIG.md.
OAuth mode is single-replica: client/session state and signing keys are local to
one host. Do not run multiple OAuth replicas until those stores are externalized
or safely shared.
Safety And Trust Model
Arcane API credentials are loaded from config/env only.
MCP callers select actions and payloads, not upstream credentials.
Destructive subactions reject unless params.confirm=true or CLI
--confirm is present.
Unknown actions, unknown subactions, missing environment IDs, missing IDs, and
unsafe volume paths are rejected before upstream calls.
Non-loopback HTTP deployments must use bearer auth, OAuth, or a trusted
authenticated gateway.
This bridge does not sandbox Arcane itself. Arcane remains responsible for
Docker authorization and the effects of Docker operations.
Architecture
ArcaneClient (src/arcane.rs) HTTP transport and redacted errors
|
ArcaneService (src/app.rs) action validation, confirmation, response normalization
|
MCP shim (src/mcp/tools.rs) JSON args -> service -> Value
CLI shim (src/cli.rs) argv -> service -> stdout
Distribution Contract
Cargo.toml, Cargo.lock, packages/arcane-rmcp/package.json,
.release-please-manifest.json, and server.json must agree on the released
version.
GitHub Releases publish the rarcane binary consumed by the npm launcher.
The npm package name is @dinglebear/rarcane; the installed binary alias is
rarcane.
When binding to a non-loopback address, configure RARCANE_MCP_TOKEN,
RARCANE_MCP_AUTH_MODE=oauth, or RARCANE_NOAUTH=true behind an authenticated
gateway.
Troubleshooting
Symptom
Check
RARCANE_API_URL is required
Set RARCANE_API_URL in env or ~/.rarcane/.env.
Arcane calls return unauthorized
Refresh RARCANE_API_KEY in Arcane and restart the bridge.
HTTP /mcp returns unauthorized
Set RARCANE_MCP_TOKEN and send Authorization: Bearer <token>.
Stdio client hangs or logs JSON errors
Ensure client config runs arcane-rmcp mcp, not the default HTTP server mode.
Destructive action is rejected
Add CLI --confirm or MCP params.confirm=true after verifying the target.
Port conflict
Set RARCANE_MCP_PORT or stop the process already using 40110.
Related Servers
soma - RMCP runtime for provider-backed MCP servers.
docs/API.md is the curated action-contract overview.
docs/CONFIG.md is the curated configuration and auth reference.
docs/QUICKSTART.md is the curated smoke-test guide.
docs/MCP_SCHEMA.md is the generated/schema-drift contract for actions,
resources, prompts, and validation rules.
plugins/rarcane/skills/rarcane/SKILL.md is the agent usage guide.
License
Original Dinglebear-authored portions of this project are licensed under AGPL-3.0-only. Separate commercial licensing is available for organizations that need terms outside the AGPL. Third-party material remains under its original license. See LICENSING.md.
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich Arcane RMCP?
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt Arcane RMCP einen API-Schlüssel?
Der Herausgeber nennt diese Umgebungsvariablen: RARCANE_API_URL, RARCANE_API_KEY, ARCANE_RMCP_VERSION, ARCANE_RMCP_REPO, ARCANE_RMCP_RELEASE_BASE_URL, RUST_LOG.
Welchen Transport verwendet Arcane RMCP?
Arcane RMCP läuft lokal über stdio.
Wann wurde Arcane RMCP zuletzt geprüft?
Zuletzt geprüft: 2026-11-07. Rust MCP server and CLI for Arcane Docker and container management.