MCP servers · 37 tools · version 1.9.0
Visual Studio bridge
Build, test and debug in Visual Studio from Claude.
A Visual Studio extension that runs an MCP server inside each Visual Studio window, and a bridge that Claude talks to. Claude builds and follows the build log while it compiles, reads the Error List and Output panes, runs tests and drives the debugger.
Free for 30 days on each computer, every tool, no sign-up. Then a key: personal use is paid after the trial. Setup also installs the MCZ MCP Manager, which shows every MCZ MCP server's licence and buys or installs keys in one click.
Several sessions at once, without tripping over each other
The Visual Studio bridge is a bridge: it controls access for every AI connection on the PC, gives each chat its own Visual Studio window and keeps the other chats out of it, so several AIs work at the same time without getting in each other's way. One bridge serves every AI session on the PC and routes each session to the Visual Studio window whose solution is in the session's working folder, starting Visual Studio on that solution if no window has it. One session per solution; leases are handled for you, and vs_session shows or changes which window a session uses.
- Up to 25 Visual Studio windows at once, each driven by its own chat
- Each chat goes to the window whose solution is in its folder; the bridge starts Visual Studio on that solution if no window has it
- One chat per solution, so two chats never edit the same code
What it does
- Build the solution or a project and read the log while it builds
- Error List and Output panes, unsaved documents
- Run tests (MSTest, xUnit, NUnit, C++)
- Debugger: start or attach, break, step, call stack and threads, locals, evaluate, breakpoints, exception settings
- Open or switch solutions, configuration and startup project
Manual: Visual Studio bridge manual (also as PDF) · Getting started with the MCP servers
Requirements
- Visual Studio 2022 or 2026 (any edition) on Windows
- Per-user setup, no administrator rights; close Visual Studio while it installs
- An MCP client: Claude Desktop (set up for you), Claude Code or any other client that speaks MCP
Set up
Setup installs the extension into every Visual Studio and registers "visualstudio" in Claude Desktop (and in Claude Code's user config when it exists). Restart Claude Desktop afterwards and ask Claude to use it; license_status shows the trial days left.
Licence
A computer joined to a domain or Entra ID counts as commercial. Each key is tied to the computer's Machine ID, which
license_status and the MCZ MCP Manager show. Install a key with license_install from Claude, in the MCZ MCP
Manager, or with the server's --license command. Licence terms. Several computers: order with a list of Machine IDs.