MCP Mode
Conceptual overview of Vaner's MCP integration and current tool surface.
Vaner ships an MCP server so MCP-aware IDEs and agents can pull Prepared Work and evidence-backed context without putting Vaner in the model hot path.
Start the server
vaner mcp --path .The server speaks stdio by default. Clients invoke vaner mcp --path . as a
subprocess and communicate over their own stdin/stdout.
Recommended client behavior
Normal clients should call vaner.prepared_work.dashboard first. It returns a
small list of UI-safe cards and hides internal lifecycle, self-evaluation, and
raw ranking fields.
When the user inspects a card, call the action returned by that card. Do not infer allowed actions from type alone. Server-authoritative actions are what keep virtual diffs and exports non-mutating by default.
Tools exposed
Prepared Work
| Tool | Purpose |
|---|---|
vaner.prepared_work.dashboard | Unified Prepared Work dashboard for UI-safe cards. |
vaner.work_products.list | Diagnostic list of prepared artifacts. |
vaner.work_products.inspect | Inspect body, evidence, warnings, and allowed actions. |
vaner.work_products.export | Export ready content or patch payload without applying it. |
vaner.work_products.dismiss | Hide a prepared artifact from normal feeds. |
vaner.work_products.feedback | Record usefulness feedback. |
Resolve and navigation
| Tool | Purpose |
|---|---|
vaner.status | Health and readiness smoke test. |
vaner.resolve | Resolve a prompt into prepared briefing, evidence, and optional draft. |
vaner.suggest | Likely next prompts or work directions. |
vaner.search | Search Vaner's scenario graph. |
vaner.expand | Deepen precompute around a scenario or target. |
vaner.inspect | Inspect one scenario/evidence record. |
vaner.explain | Human-readable rationale for a resolution. |
vaner.feedback | Feedback for resolution/scenario flows. |
vaner.warm | Hint Vaner to precompute around selected targets. |
vaner.debug.trace | Diagnostic trace data. |
Predictions and workspace goals
Predictions remain available for diagnostic and advanced clients, but Prepared Work is the normal user-facing surface.
| Tool | Purpose |
|---|---|
vaner.predictions.active | List ready/drafting predictions. |
vaner.predictions.adopt | Adopt a specific prediction as the current intent. |
vaner.predictions.dashboard | Diagnostic prediction dashboard. |
vaner.goals.list | List workspace goals. |
vaner.goals.declare | Declare a new user-authoritative goal. |
vaner.goals.update_status | Move a goal between active, paused, abandoned, and achieved. |
vaner.goals.delete | Delete a goal. |
Setup, policy, sources, artifacts, and Deep-Run
| Tool family | Purpose |
|---|---|
vaner.setup.* | Setup questions, recommendations, apply flow, and setup status. |
vaner.policy.show | Current policy bundle and posture. |
vaner.artefacts.* | List/inspect/status/influence controls for stored artifacts. |
vaner.sources.status | Source health/status. |
vaner.deep_run.* | Start, stop, inspect, list, and default Deep-Run sessions. |
All tools are scoped to the --path Vaner was started with.
Want to wire it up?
- Connect your AI client, one command per client, picker for manual setup.
- Backends, pick the LLM Vaner ponders with.
When to use MCP vs other modes
- MCP mode: your IDE orchestrates model calls and needs Vaner-provided Prepared Work/context. Recommended default.
- Proxy mode: tools that only speak the OpenAI
/v1/chat/completionsshape. - Context-only mode: frameworks that call
/v1/contextdirectly. - Python SDK: custom scripts.