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Β