Wheelhouse documentation

Wheelhouse connects Claude Code to a running Visual Studio, in two parts that work together.

The panel

Open it from View › Wheelhouse. It runs Claude Code sessions inside Visual Studio, with the MCP servers you have configured for Claude Code: start a new conversation or pick up an earlier one (grouped by the Git branch you are on), attach files and screenshots, answer permission prompts and Claude's questions with buttons, and review changes in Visual Studio's diff viewer before they are made. It signs Claude Code in for you when needed, and its settings cover the editor, the session, your licence, MCP servers, text size and the versions you are running. See using the panel.

The MCP server

An MCP server called vs-claude-mcp gives Claude its Visual Studio tools. Sessions in the panel get them automatically. Claude Code sessions in a terminal get them because Wheelhouse registers the server with Claude Code on its first start, and a terminal session binds to the Visual Studio it is running inside.

Most tools are answered from inside Visual Studio, which is what makes them fast and exact: diagnostics from the live Roslyn workspace rather than a build, references resolved semantically rather than by text search, tests run through Test Explorer, and pictures of Visual Studio and of the app you are debugging. See what Claude can do.

Where to start