Vaner
Integrations

Integrations

MCP-first integration paths for IDEs, runtimes, and optional compatibility layers.

Ask ChatGPTAsk Claude

Default onboarding is MCP + cockpit (vaner mcp, vaner watch, vaner show). This section covers integration modes and tool-specific recipes.

Connect your AI client

One command per client (Claude Code, Cursor, Codex CLI, Cline, Continue, Zed, Windsurf, Roo, VS Code, Claude Desktop). Manual-setup picker if you'd rather paste it yourself.

MCP mode

Conceptual overview: how Vaner exposes Prepared Work and the vaner.* tool family to MCP-aware clients.

Client capability matrix

Per-client support for the four leverage layers, MCP, primer, skill, hooks.

Advanced and compatibility modes

Context-only mode

Call /v1/context directly from custom frameworks.

Python SDK

Use Vaner as a library inside scripts and automation.

Proxy mode

OpenAI-compatible /v1/chat/completions for clients that cannot use MCP.

Docker

Compose topology for local multi-service setups.

If your client supports MCP, prefer MCP mode first and only use advanced modes when needed.

Edit on GitHub

Auto Focus

How Vaner decides whether to work, where to work, and why.

Connect your AI client

One command per AI client (Claude Code, Cursor, Codex CLI, Cline, Continue, Zed, Windsurf, Roo, VS Code, Claude Desktop). Vaner installs every applicable layer.

On this page

Default integration (recommended)Advanced and compatibility modes