Editor and CLI · stdio MCP · setup guide 08

Cline
connects locally.

Set up the local Agent Decision Kit MCP server in Cline CLI or the IDE extension, preserve tool approval prompts, and verify the live server configuration.

01 / Build once

Prepare the source checkout

npm install
npm run build

Keep the absolute checkout path ready. The published npm package is not available yet; when it ships, this setup will be shorter.

02 / Add the server

Cline CLI wizard or MCP Servers → Configure in the IDE

cline mcp install agent-decision-kit -- node /absolute/path/to/agent-decision-kit/dist/cli.js mcp
cline mcp
cline config mcp --json

Cline can auto-approve individual MCP tools. Leave autoApprove empty so an approval-required browser action is still reviewed in the client. The CLI resolver currently places its default MCP settings under ~/.cline/data/settings/.

Configuration option

Source-checkout server entry

{
  "mcpServers": {
    "agent-decision-kit": {
      "command": "node",
      "args": [
        "/absolute/path/to/agent-decision-kit/dist/cli.js",
        "mcp"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}

03 / Verify

Check the connection

Run `cline config mcp --json` and confirm the server is enabled, or inspect it in the MCP Servers panel. Ask Cline to call model_route on a simple prompt.

04 / Try a real workflow

Start with sample data

Use context_prune with an exact error line in retain. Compare the returned substring character for character.

Client setup reference: Cline CLI MCP setup ↗ · Cline's current MCP settings path resolver ↗

← Browse all agent guides

Clineconnects locally.