1C Debug MCP
Related Servers
Alternatives to 1C Debug MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables any MCP client to debug programs through the Debug Adapter Protocol, supporting launch/attach, breakpoints, stepping, variable inspection, evaluation, and memory operations via a single debug tool.17 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables launching and controlling a debugpy debug session through MCP, including setting breakpoints, stepping, evaluating expressions, and observing debugger state and events.MIT
- AlicenseAqualityAmaintenanceEnables coding agents to connect to Debug Adapter Protocol debuggers over MCP, allowing them to launch or attach to native targets, control execution, set breakpoints and watchpoints, inspect stacks, variables, memory, and exceptions, and capture agent-friendly debugger snapshots.18125 npm3Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to debug Node.js applications using Chrome DevTools Protocol. Provides comprehensive debugging capabilities including breakpoints, stepping, variable inspection, expression evaluation, and console monitoring.1,441 npm350MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to debug .NET programs by launching or attaching to processes, setting breakpoints, stepping through code, inspecting variables, evaluating C# expressions, and handling exceptions, with support for multiple processes and .NET MAUI apps.7MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to perform interactive Python debugging with breakpoints, step execution, and variable inspection using the Debug Adapter Protocol (DAP) through an MCP server interface.81MIT
TDQS
Scored across 15 tools
Each tool targets a distinct phase of the 1C debugging workflow: connection, target management, execution control, inspection, and source mapping. Even similar actions like check_debug_server vs connect_debugger are clearly separated by whether a debugger UI is registered.
All tool names follow a consistent snake_case verb_noun pattern, such as list_debug_targets, attach_targets, set_breakpoints, and continue_or_step. This makes the toolset highly predictable and easy to navigate.
15 tools is at the upper boundary of the well-scoped range, but every tool earns its place in a debugger lifecycle: connect, list, attach, breakpoint, poll, inspect, evaluate, step, suspend, detach. The count matches the complexity of the domain without redundancy.
The toolset covers the full debugging workflow from connecting to a debug server and resolving source modules, through attaching targets, setting breakpoints, polling events, inspecting state, controlling execution, and detaching. There are no obvious dead ends or missing critical debugger operations.