The first and only Visual Studio extension that gives AI assistants access to the C# compiler (Roslyn) and the Visual Studio Debugger through the
Most developer tooling work still happens through a UI a human drives. MCP Ai Server Visual Studio MCP server moves it into the conversation instead. The first and only Visual Studio extension that gives AI assistants access to the C# compiler (Roslyn) and the Visual Studio Debugger through the Model Context Protocol. 41 tools. 13 powered by Roslyn. 19 debugging tools (Preview).
Built by Ladislav Sopko — 30 years of software development, from assembler to enterprise .NET.
The server publishes 14 tools. What each one is for:
debug_start — Start debugging (F5). Fire-and-forgetdebug_stop — Stop debugging sessiondebug_get_mode — Current mode: Design, Running, or Breakdebug_break — Pause the running applicationdebug_continue — Resume executiondebug_step — Step over/into/outimmediate_execute — Execute expression with side effectsdebug_list_transports — List transports (Default, Docker, WSL, SSH...)debug_list_processes — List processes on a transportdebug_attach — Attach to a running processdebug_get_callstack — Call stack of current threaddebug_get_locals — Local variables (tree-navigable)Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Ai Server Visual Studio's toolset — debug_start, debug_stop, debug_get_mode and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ladislavsopko; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| debug_start | Start debugging (F5). Fire-and-forget |
| debug_stop | Stop debugging session |
| debug_get_mode | Current mode: Design, Running, or Break |
| debug_break | Pause the running application |
| debug_continue | Resume execution |
| debug_step | Step over/into/out |
| immediate_execute | Execute expression with side effects |
| debug_list_transports | List transports (Default, Docker, WSL, SSH...) |
| debug_list_processes | List processes on a transport |
| debug_attach | Attach to a running process |
| debug_get_callstack | Call stack of current thread |
| debug_get_locals | Local variables (tree-navigable) |
| debug_evaluate | Evaluate expression / drill into variable tree |
| output_read | Read VS Output window (Build, Debug, Tests) |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.