Skip to content

Cline

Connect Cline (VS Code extension) to LatchGate so every tool call goes through the execution security kernel.

  • LatchGate running (latchgate up or production deployment)
  • latchgate-mcp binary on PATH (from GitHub Releases or brew install latchgate-ai/tap/latchgate)
  • Cline VS Code extension installed
Terminal window
latchgate-mcp install --ide cline

This writes the MCP server entry to Cline’s settings file:

  • macOS: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
  • Linux: ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
  • Windows: %APPDATA%/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

Restart VS Code to pick up the configuration.

Preview first without writing:

Terminal window
latchgate-mcp install --ide cline --dry-run

Add to your cline_mcp_settings.json:

{
"mcpServers": {
"latchgate": {
"command": "/usr/local/bin/latchgate-mcp",
"args": ["serve", "--gate-url", "http://localhost:3000"],
"env": {
"LATCHGATE_AGENT_ID": "cline",
"RUST_LOG": "warn"
}
}
}
}

Adjust the binary path if installed elsewhere. Use which latchgate-mcp to find it.

  1. Start LatchGate: latchgate up
  2. Install config: latchgate-mcp install --ide cline
  3. Restart VS Code.
  4. Open Cline and ask the agent to perform an HTTP request.
  5. Verify the audit trail: latchgate audit --limit 5
  6. Confirm the full pipeline: lease => policy => WASM sandbox => receipt.

Replace --gate-url with UDS + public base URL for production:

{
"mcpServers": {
"latchgate": {
"command": "/usr/local/bin/latchgate-mcp",
"args": ["serve", "--public-base-url", "http://localhost:3000"],
"env": {
"LATCHGATE_AGENT_ID": "cline",
"RUST_LOG": "warn"
}
}
}
}

This connects via /run/latchgate/gate.sock (default) — no TCP exposure.

For production hardening with UDS transport, see Deployment.