IntegrationsPer-client guides
VS Code (Copilot) + Vaner (MCP)
Connect VS Code (Copilot) to Vaner over MCP for predictive, repo-grounded context.
VS Code (Copilot) supports the
Model Context Protocol out of the box.
Point it at vaner mcp and Vaner will serve scenario-ranked context to your
agent before every prompt.
Install
If you haven't installed Vaner yet:
curl -fsSL --proto '=https' --tlsv1.2 https://vaner.ai/install.sh | bash
vaner init --path .Connect VS Code (Copilot)
Path: ~/.config/Code/User/mcp.json
{ "servers": { "vaner": { "type": "stdio", "command": "uvx", "args": ["--from","vaner[mcp]","vaner","mcp","--path","${workspaceFolder}"] } }}Verify
Reload the VS Code window. In the Copilot chat view, pick the `vaner` MCP server from the tools menu and call `list_scenarios`.
Upstream docs
https://code.visualstudio.com/docs/copilot/chat/mcp-servers
Verify
Reload the VS Code window. In the Copilot chat view, pick the vaner MCP server from the tools menu and call list_scenarios.
If VS Code (Copilot) reports the server as failed, run vaner mcp --path .
manually in a terminal and read the error. The most common failure is a
missing backend API key — confirm with vaner config show.
What this unlocks
- Use
@vanerin Copilot Chat to pull in scenario-ranked context before generating a diff. - Share the workspace config via
.vscode/mcp.jsonso teammates pick it up on clone. - Combine with GitHub Copilot Workspace for repo-wide refactors.
See also
- The full Connect your client guide.
- Backends for picking the model Vaner ponders with.
- Upstream docs: https://code.visualstudio.com/docs/copilot/chat/mcp-servers.