configure

/arcane:configure — Tool filter setup

Use this slash command to trim which Arcane MCP tools are exposed to Claude Code. The full server registers 180 tools; surfacing all of them in tools/list bloats the context window. This command writes a tools block to ~/.arcane/config.json that selects a preset, module allowlist, and per-tool overrides. The Arcane MCP server picks up changes live when its config watcher is attached.

Workflow

1. Ask the user to pick a preset with AskUserQuestion, single-select:

   • commonly-used — containers, images, projects (stacks), volumes, networks (~52 tools) (recommended default)
   • read-only — every *_list / *_get / *_inspect / *_stats / *_status / *_summary tool (~60 tools)
   • minimal — dashboard + container list/get/counts (5 tools)
   • deploy — project, gitops, template, registry, environment, build (~40 tools)
   • full — all 180 tools (current default if the user has never configured this)
   • custom — fine-tune modules and individual tools

2. If the user picks custom (or says they want to fine-tune after picking another preset):

   • Ask which modules to enable via AskUserQuestion multi-select. The 25 module names: auth, build, container, dashboard, environment, event, gitops, image, image-update, job, network, network-topology, notification, port, project, registry, settings, swarm, system, template, updater, user, volume, vulnerability, webhook.
   • Optionally ask if they want per-tool adjustments. If yes, iterate module-by-module (never more than ~10 options per AskUserQuestion step) showing each module's tools so they can add/remove individual entries.

3. Build the tools block — only include the fields that are non-empty:

   {
     "tools": {
       "preset": "<chosen>",
       "modules": ["<optional allowlist>"],
       "enabled": ["<optional additions>"],
       "disabled": ["<optional subtractions>"]
     }
   }