Debug MCP Server

Debug MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. debug-mcp is a Model Context Protocol server that exposes .NET debugging capabilities as structured API tools. It allows AI assistants like Claude, GPT, or Copilot to:.

Setting it up

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

What the assistant can call

Once Debug MCP is connected, these are the calls the assistant has available:

• Category — Tools
• Session — debug_launch, debug_attach, debug_disconnect, debug_state
• Execution — debug_continue, debug_pause, debug_step
• Breakpoints — breakpoint_set, breakpoint_remove, breakpoint_list, breakpoint_enable, breakpoint_wait
• Tracepoints — tracepoint_set
• Inspection — threads_list, stacktrace_get, variables_get, evaluate
• Memory — object_inspect, memory_read, layout_get, references_get, members_get
• Modules — modules_list, modules_search, types_get
• Requirements — The Requirements tool exposed by this server

Configuration and credentials

• .NET 10 SDK or later - Linux (Windows and macOS support planned)

Before you rely on it

• 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.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Debug MCP.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the debug mcp mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Debug MCP's toolset — Category, Session, Execution and 6 more — is a fair guide to whether it matches your workflow. It is maintained by jkolo; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Debug MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.