Visual Studio · Beta

Save Visual Studio Copilot agent chat history

VibeHub connects its MCP server to Visual Studio 2022 (17.14+) Copilot agent mode, so the agent can store conversation transcripts in VibeHub and attach them to commits. Setup is a single .mcp.json file.

Set it up

Save as <solution dir>\.mcp.json (or %USERPROFILE%\.mcp.json)

{
  "servers": {
    "vibehub": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "vibehub-mcp"],
      "env": {
        "VIBEHUB_API_URL": "https://vibehub.co",
        "VIBEHUB_TOKEN": "vbh_REPLACE_ME"
      }
    }
  }
}

What gets captured

  • Copilot agent-mode conversation transcripts, as VibeHub sessions
  • Links between those transcripts and your git commits

How it works

Generate a token in the VibeHub dashboard (Settings → API tokens) and replace vbh_REPLACE_ME with it.

Open the solution, switch Copilot Chat to Agent mode, and approve the vibehub server when prompted. Its tools appear under the tools picker.

Ask the agent to “save this conversation to VibeHub” or “capture this commit with the transcript” and it calls the vibehub_* tools.

Visual Studio + VibeHub FAQ

Should I use a per-solution or global .mcp.json?
Per-solution (<solution dir>\.mcp.json) is recommended: commit it without the token and let each developer fill in VIBEHUB_TOKEN. Use %USERPROFILE%\.mcp.json to apply it to all solutions.
What are the requirements?
Visual Studio 2022 17.14 or later, and Node.js 18+ on your PATH — the server runs via npx -y vibehub-mcp.

Other integrations

Claude CodeVS CodeCursorWindsurfReplitZedAll integrations →

Version the whole vibe.

The vb CLI, public vibes, and GitHub mirroring are free forever.

Get started freeRead the quickstart