Model Context Protocol

Every CLI command,
an agent tool

Give any MCP-aware agent the whole platform as typed tools — no wrappers, no glue code. Run it locally from the CLI for the fastest setup, or connect to the hosted remote server with no install at all.

dodil mcp
✓ listening · stdio0 config
# any MCP agent auto-discovers every command as a typed tool
ignite_app_deployk3_bucket_getvbase_db_listscriptum_runignite_models_chatk3_table_query+42 more
✓ Claude Code connected48 tools
Two ways to connect

Local from the CLI, or remote over HTTP

Same tools, same JSON output. Run MCP on your machine straight from the CLI for the fastest setup, or point your agent at the hosted endpoint with nothing to install.

Local MCP · via the CLI
Fastest to set up

Install the CLI and run dodil mcp. The server runs on your machine over stdio and reuses the login you already have — nothing to host, no keys to mint. Ideal for terminal and editor agents that run locally and can launch a process.

Best for
Claude CodeCodexCursorCopilot
$dodil mcp
Wire it into Claude Code:
$claude mcp add dodil -- dodil mcp
Install the CLI
Remote MCP · mcp.dodil.io
No install

Point any MCP client straight at the hosted endpoint — no CLI, no local process. Ideal for cloud assistants that can’t spawn a local binary. Authenticate with a service account you mint from IAM in the dashboard, then grant it the roles your agent needs.

Best for
Claude · claude.aiChatGPT
$https://mcp.dodil.io
Mint a service account (id + secret) under IAM, then set it as the client’s credentials.
Mint a service account in IAM
Code mode (--enable-exec) adds a single dodil_exec tool that runs a bash script with the CLI on PATH — off by default, and refused over the remote HTTP server unless explicitly allowed.
How it works

Connect once, agents auto-detect

1 · Connect it

Locally with dodil mcp over stdio, or remotely at mcp.dodil.io — no daemon, no ports, no config file either way.

2 · Agent speaks MCP

Your agent talks to the server over the Model Context Protocol. Claude Code, Cursor, and VS Code Copilot work out of the box.

3 · Tools auto-detected

Every CLI command — ignite_app_deploy, k3_bucket_get, scriptum_run — appears as a typed tool with JSON output. Nothing to wire up.

Point your agent

Wire it into any MCP client

Local — via the CLI
Claude Code
$claude mcp add dodil -- dodil mcp
Cursor / VS Code (mcp.json)
$"dodil": { "command": "dodil", "args": ["mcp"] }
Remote — mcp.dodil.io
Claude Code
$claude mcp add --transport http dodil https://mcp.dodil.io
Cursor / VS Code (mcp.json)
$"dodil": { "url": "https://mcp.dodil.io" }
Authenticate with a service account minted in IAM and pass its id and secret as the client credentials.
FAQ

Common questions

What is the Dodil MCP server?

A Model Context Protocol (MCP) server that exposes every Dodil command — across Ignite, K3, Scriptum, and models — as a typed tool with JSON output. Any MCP-aware agent connects to it and gets the whole platform, no glue code.

What's the difference between local and remote MCP?

Local MCP runs on your machine straight from the CLI (dodil mcp, over stdio) and reuses your existing login — it's the fastest way to get started and nothing to host. Remote MCP is the hosted server at https://mcp.dodil.io: no install, connect from anywhere, authenticated with a service account. Both expose the same tools.

Which agents and editors work with it?

Any MCP client. Claude Code, Cursor, and VS Code Copilot work out of the box with either the local or remote server — the tools are auto-detected with no extra glue code.

How do I connect the remote server at mcp.dodil.io?

Point your MCP client at https://mcp.dodil.io and authenticate with a service account. Mint one under Organization → Members → Service accounts in the dashboard, grant it the roles your agent needs, and pass its id and secret as the client credentials.

How do I connect Claude Code?

Local: run `claude mcp add dodil -- dodil mcp`. Remote: run `claude mcp add --transport http dodil https://mcp.dodil.io` and provide your service-account credentials. For Cursor or VS Code, add an mcp.json entry — { "command": "dodil", "args": ["mcp"] } for local, or { "url": "https://mcp.dodil.io" } for remote.

Is it safe to expose the CLI as tools?

The server exposes commands as typed tools. Code mode (--enable-exec), which runs an arbitrary bash script with the CLI on PATH, is off by default and refused over the remote HTTP server unless explicitly allowed.

Regions
UKLiveEULiveMiddle EastSoonAfricaSoon
Compliance
SOC 2In progressISO 27001In progressGDPR-readyData residencyEnforced
© 2026 Circle Technologies Pte Ltd. All rights reserved.