Integration: Cline

Coverage status

Path	Status	Notes
MCP server	✅ Supported	Cline’s MCP client (Settings → MCP Servers)
Harness	✅ Supported	Proxy via custom API base URL
Extension	—	Cline runs inside VS Code; use MCP instead

Confidence: High. Cline’s MCP support is mature. Pick whichever path fits your workflow — they’re equivalent in coverage.

Setup: MCP path

1. Start the MemStrata MCP server

memstrata serve --port 8080

2. Register in Cline

Open VS Code → Cline extension panel → Settings (gear icon) → MCP Servers → Add:

{
  "memstrata": {
    "url": "http://localhost:8080/mcp",
    "disabled": false,
    "alwaysAllow": ["context_query", "index_status"]
  }
}

Or edit ~/.vscode/cline_mcp_settings.json directly.

3. Verify

In a Cline session, ask: “What’s my context efficiency?” MemStrata will respond with your current session stats.

Setup: Harness path

1. Start the harness

memstrata serve --port 8080

2. Configure Cline’s API base

In Cline settings → API Provider → Custom:

Base URL: http://localhost:8080/openai (for OpenAI) or http://localhost:8080/anthropic (for Anthropic)
API Key: your real provider key (still required; the harness forwards it)

What’s captured

Signal	Captured?	Notes
Cline task turns	✅ Yes	Full context compression
File read/write operations	✅ Yes	Tracked for 24h survival
Bash command outputs	✅ Yes	Included in context accounting
Plan mode vs. Act mode	✅ Yes	Both modes captured
Browser tool (if enabled)	⚠️ Partial	Browser content not compressed; Cline sends it as raw HTML

Troubleshooting

MCP tools show but don’t run
Check alwaysAllow includes the tools you need. Cline requires explicit tool permission.

Harness returning wrong model responses
Ensure Cline’s API base URL points to http://localhost:8080/anthropic for Claude models (not the OpenAI endpoint).