Your code map, drift, and version-correct docs are only useful to an AI assistant if the assistant can reach them. vg install wires Vibgrate AI Context into your assistant in one step. This article explains what it sets up and which assistants it supports.
Overview
vg install adds Vibgrate AI Context to your AI assistant by installing a skill, the MCP wiring that connects the assistant to the local context server, and an advisory nudge that encourages the assistant to use it. The operation is idempotent — safe to run repeatedly — and repo-local, so it applies to the project you run it in.
Supported assistants
vg install supports Claude, Cursor, Windsurf, VS Code, Codex, and Gemini.
Prerequisites
Work inside your project. Building a code map first means the assistant has something to query immediately:
vg build
Install the integration
vg install
Because it is idempotent, you can re-run it any time — after updating the CLI, switching assistants, or onboarding a teammate — without creating duplicates.
Pair with the context server
vg install connects your assistant to Vibgrate AI Context, the local offline MCP server. Start the server so the assistant can read your code map, drift, and version-correct library docs:
vg serve
No account is required and nothing is uploaded.
What your assistant gains
Once wired up, your assistant can ask the code map structural questions, pull facts about nodes, and read version-correct docs pinned to your lockfile — grounding its suggestions in your actual code rather than guesses.
Related
- Start the context server with
vg serve. - Generate node facts with
vg facts. - Access version-correct docs with
vg lib.
The integration is repo-local and works offline once set up.