Connect Cavaridge to Cline

Cline is a VS Code extension that supports MCP. Cavaridge’s per-product servers slot in via Cline’s MCP settings.

Prerequisites

• VS Code with the Cline extension installed
• Cavaridge tenant + account

Configure

In VS Code, open the Cline panel → MCP Servers → Add Server. Cline asks for a JSON entry similar to Cursor’s:

{
  "name": "cavaridge-aegis",
  "url": "https://mcp.cavaridge.app/aegis",
  "auth": {
    "type": "oauth2_pkce",
    "authorize_url": "https://auth.cavaridge.app/oauth/authorize",
    "token_url": "https://auth.cavaridge.app/oauth/token",
    "scopes": ["aegis.scans.read"]
  }
}

Cline opens the OAuth consent in your default browser. Approve.

Repeat for any other Cavaridge product surface:

• mcp.cavaridge.app/forge — Cavaridge AI
• mcp.cavaridge.app/cavalier — Cavaridge Operations
• mcp.cavaridge.app/reclaim — Cavaridge Reclaim
• (full list at mcp.cavaridge.app)

Verify

In a Cline chat:

Tell me about open AEGIS findings on ContosoCare

Cline picks the right tool from the catalog (aegis.list_findings) and invokes it.

Code-context use cases

Cline shines when the AI is acting in your codebase. Common Cavaridge flows that pair well:

• Drafting a Cavaridge SoW based on an architecture doc you have open in the editor (cavalier.create_quote — destructive, confirms).
• Asking for AEGIS context before implementing a security control in your app (aegis.list_findings).
• Drafting a Reclaim recovery policy from a natural-language description of what to recover (reclaim.draft_policy).

Where to manage connections

• api.cavaridge.app/mcp — audit + revoke
• Tool catalogs: GET https://mcp.cavaridge.app/{product}/list_tools

Trust contract

Same shape as the other clients. Cline surfaces destructive-tool confirmation prompts inside the editor; clicking through re-invokes with confirmed: true. Revocation from the Cavaridge API portal is immediate.