Local server — dodil mcp
The dodil CLI is the Dodil Model Context Protocol server. Running dodil mcp lets local AI agents (Claude Code, Cursor, VS Code Copilot, …) call Dodil operations as structured tools, across every product.
Prefer not to install anything, or using an assistant that runs in a browser? Use the hosted remote server instead — same tools, no install. Not sure which you want? See the comparison.
- Tools mirror the CLI. Every command is exposed as a tool named after its path —
ignite_app_list,k3_bucket_get,git_repo_list,scriptum_thread_run— with typed parameters and JSON output. Flags become named parameters; positional arguments go in anargsarray. - Auth and config are shared with the CLI: the server inherits your login from the CLI config, so there’s nothing extra to set up once you’ve authenticated with
dodil auth login. - Transports —
stdio(default, for a single local agent) or--transport http(--addr,--path, default/mcp) for remote/shared access. - Code mode (
--enable-exec) adds onedodil_exectool that runs a Bash script withdodilonPATH, letting an agent chain many calls in a single step.
Install & run
With the dodil CLI
The dodil CLI is also the MCP server — once it’s installed, dodil mcp runs it. The CLI installer registers it for supported agents automatically; to run or register it yourself:
dodil mcp # stdio transport (default) — the agent launches thisdodil mcp --enable-exec # stdio + code-mode exec tool
dodil mcp --transport http --addr :9000 # remote, served at http://:9000/mcpRegister it with an agent
- Claude Code —
claude mcp add dodil -- dodil mcp; see Connect Claude Code. - Cursor, VS Code Copilot and other editors — the
{"mcpServers": …}config schema; see Other clients.
With npx
Coming soon — a standalone npx-based server, for agents that prefer a Node entry point with no binary to install.
Code mode
Code mode (--enable-exec) adds one dodil_exec tool that runs a Bash script with dodil on PATH, letting an agent chain many calls in a single step instead of one tool call at a time.
It is arbitrary code execution, so it is off by default and refused over HTTP unless you also pass --allow-exec-http. For the same reason the hosted remote server never offers it — code mode is a local-machine feature.
Per-product MCP servers
Each product’s docs cover its own MCP tools in depth:
- Ignite — MCP server
- K3 — MCP server
- Scriptum — docs
- Git — docs
- Registry — docs