ASP.NET Core Debugger — For AI Agents MCP Server

MCP server giving AI agents interactive .NET / ASP.NET Core debugging via netcoredbg + DAP.

Local serverstdio

What is the ASP.NET Core Debugger — For AI Agents MCP Server?

MCP server giving AI agents interactive .NET / ASP.NET Core debugging via netcoredbg + DAP.

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

Setup and compatibility

This listing has no verified copy-paste launch configuration. Use the project documentation to confirm the entry point, runtime and authentication before registering it in your MCP client. A package name or repository alone is not a runnable configuration.

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Example prompts to try

  • “Use ASP.NET Core Debugger — For AI Agents to Category.”
  • “Use ASP.NET Core Debugger — For AI Agents to Session.”
  • “Use ASP.NET Core Debugger — For AI Agents to Execution.”

Frequently asked questions

MCP server giving AI agents interactive .NET / ASP.NET Core debugging via netcoredbg + DAP. Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.