Connect Cline to Semlith over MCP

How to connect Cline to Semlith over MCP, the command or file that adds it, and how to check the connection works.

Every stanza writes ${SEMLITH_BIN} where the binary goes, the path which semlith prints. Set up your agent client explains it and the HTTP form.

Cline — ~/.cline/data/settings/cline_mcp_settings.json, the one file both the VS Code extension (4.x) and the CLI (3.x) read, and the one the MCP Servers panel’s Configure button opens. It is the same path under your home on macOS, Linux and Windows, it moves with CLINE_DIR when that is set, and Cline creates it as {"mcpServers": {}} on first activation. CLINE_DATA_DIR and CLINE_MCP_SETTINGS_PATH also move it, and take precedence; with either set, paste the stanza into the file they name. semlith setup --register-all writes the entry below, which covers the extension and the CLI at once (https://docs.cline.bot/mcp/mcp-overview).

~/.cline/data/settings/cline_mcp_settings.json

{
  "mcpServers": {
    "semlith": {
      "command": "${SEMLITH_BIN}",
      "args": ["mcp"]
    }
  }
}

Or against a daemon on another machine, over HTTP. The transport is streamableHttp in camel case; anything else falls back to SSE and the endpoint answers 405:

{
  "mcpServers": {
    "semlith": {
      "type": "streamableHttp",
      "url": "http://127.0.0.1:7365/mcp",
      "headers": { "Authorization": "Bearer ${SEMLITH_AGENT_KEY}" },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Its user-level instructions file, read on every session, to which semlith setup --register-all appends the rule block — see https://docs.cline.bot/customization/cline-rules.

~/Documents/Cline/Rules/semlith.md

${SEMLITH_RULES}