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.
Pick your path
Section titled “Pick your path”Claude Code — install the plugin once and it applies to every project:
/plugin marketplace add trevarix/claude-marketplace/plugin install agentic-vc@trevarixClaude 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:
avc init --skills claude-code,cursor,windsurfNo further setup needed — open your editor, the agent finds AVC automatically.
Pages in this section
Section titled “Pages in this section”How agents use AVC
Section titled “How agents use AVC”A typical agent workflow with AVC:
- Snapshot the current state before any non-trivial change (
avc_snapshot) - Branch if the work is uncertain or experimental (
avc_branch_create) - Make changes inside the workspace
- Snapshot the result
- Diff against the baseline to summarize what changed (
avc_diff) - 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.
Custom integrations
Section titled “Custom integrations”If your agent framework isn’t covered by --skills, use the generic preset:
avc init --skills genericThis 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.