Skip to content

Agent Integration

AVC integrates with AI agent frameworks via the Model Context Protocol — every CLI command is exposed as a tool that agents can call directly.

Claude Code — install the plugin once and it applies to every project:

/plugin marketplace add trevarix/claude-marketplace
/plugin install agentic-vc@trevarix

Claude Desktop — install the .mcpb extension; it carries the avc binary, so there is nothing else to set up. See Claude Desktop.

Cursor, Windsurf, or a single project — write the config and instruction files into the project:

Terminal window
avc init --skills claude-code,cursor,windsurf

No further setup needed — open your editor, the agent finds AVC automatically.

A typical agent workflow with AVC:

  1. Snapshot the current state before any non-trivial change (avc_snapshot)
  2. Branch if the work is uncertain or experimental (avc_branch_create)
  3. Make changes inside the workspace
  4. Snapshot the result
  5. Diff against the baseline to summarize what changed (avc_diff)
  6. Restore or merge based on user approval

The skill / rules files written by avc init --skills instruct the agent on when to use each tool.

If your agent framework isn’t covered by --skills, use the generic preset:

Terminal window
avc init --skills generic

This writes AGENT_INSTRUCTIONS.md — a framework-neutral document you can include in any agent prompt.

For MCP-aware frameworks, the minimal config is:

{
"mcpServers": {
"avc": {
"command": "avc",
"args": ["mcp", "serve", "--compact"]
}
}
}

See MCP Server for the full tool catalog and protocol details.