ASP.NET Core Debugger — For AI Agents MCP Server

Connect ASP.NET Core Debugger — For AI Agents to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server giving AI agents interactive .NET / ASP.NET Core debugging via netcoredbg + DAP. The asp.net core debugger — for ai agents mcp server is what makes that connection.

What the server does

Instead of "I think the bug is around line 42, try this", the agent runs your code, pauses it, reads the actual runtime values, mutates state to test a fix, and answers grounded in what it actually saw.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Category — Tools
• Session — debug_launch, debug_attach, debug_disconnect, debug_state
• Execution — debug_continue, debug_pause, debug_step, breakpoint_wait
• Breakpoints — breakpoint_set, breakpoint_set_function, breakpoint_set_exception, breakpoint_set_data, breakpoint_remove, breakpoint_list
• Inspection — threads_list, stacktrace_get, variables_get, variables_set, evaluate, stack_explore
• Health — debugger_health

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. ASP.NET Core Debugger — For AI Agents's toolset — Category, Session, Execution and 3 more — is a fair guide to whether it matches your workflow. It is maintained by magna-nz; 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.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.