mcp-netcoredbg
Related Servers
Alternatives to mcp-netcoredbg
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that lets AI agents (Claude, Cursor) debug your .NET / ASP.NET Core app2714MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to control GDB debugging sessions, including breakpoint management, thread analysis, and variable inspection, using the GDB/MI protocol.221MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for AI-assisted Python debugging using debugpy and Debug Adapter Protocol, enabling AI agents to run tests, set breakpoints, and inspect variables via natural language.8MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server that bridges MCP and the Debug Adapter Protocol, enabling AI coding agents to launch and control debug sessions, set breakpoints, step through code, and inspect variables.17MIT
- FlicenseNot gradedqualityAmaintenanceAn MCP server and VS Code extension that enables AI clients to interactively debug code using breakpoints, execution control, and state inspection. It is language-agnostic and works with any debugger that supports VS Code's launch.json configurations.-
- AlicenseBqualityDmaintenanceMCP server for debugging Node.js programs through the V8 Inspector Protocol, allowing AI agents to set breakpoints, inspect variables, and step through code.117 npm5MIT
TDQS
Scored across 25 tools
Each tool has a clearly distinct purpose within the .NET debugging domain, with no significant overlap. For example, 'step_into', 'step_over', and 'step_out' are distinct stepping operations, while 'launch' and 'launch_watch' cover different startup modes. The descriptions reinforce these distinctions, making misselection unlikely.
Tool names follow a highly consistent snake_case pattern with clear verb_noun or verb-only structures, such as 'set_breakpoint', 'list_sessions', and 'continue'. There are no deviations in naming conventions, making the set predictable and easy to navigate for an agent.
With 25 tools, the count is on the higher side for a debugging server, which might feel heavy but is reasonable given the comprehensive coverage of debugging operations. It includes all essential actions like stepping, breakpoint management, and session control, though it borders on being extensive.
The tool set provides complete coverage of the .NET debugging lifecycle, including session management (launch, attach, terminate), execution control (continue, pause, step operations), breakpoint handling, variable inspection, and status monitoring. There are no obvious gaps, ensuring agents can handle all typical debugging workflows without dead ends.