Set up banish for Cline

banish runs as an MCP server. Register it in Cline and every command it runs through banish comes back compacted, so Cline spends far fewer tokens on verbose shell and tool output.

Prerequisites

• banish installed. See install and confirm with banish version.
• Cline, which supports MCP servers over stdio.

Register banish

In the Cline extension, open the MCP Servers panel, choose Configure, and add banish to the JSON:

{
  "mcpServers": {
    "banish": { "command": "banish", "args": ["serve"], "disabled": false, "autoApprove": [] }
  }
}

The Cline command-line build reads the same shape from ~/.cline/mcp.json. If Cline cannot find banish on your PATH, replace "banish" with the absolute path from which banish.

Verify

Open the MCP Servers panel and confirm banish is connected. banish exposes every verb in your extensions as an MCP tool - with the defaults you get 45-plus tools such as banish_gs, banish_dps, and banish_kpods.

What you get

Cline now reads compacted output through banish. See MCP server for how verbs become tools, the benchmarks for measured savings, and set up an agent for the general flow.

Other agents: Gemini CLI, OpenAI Codex, Windsurf, GitHub Copilot.