A
licenseNot graded
qualityC
maintenanceMCP 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.
8
MIT
agentic-debugger
by iarmankhan
Related Servers
Alternatives to agentic-debugger
No user-submitted related servers found.
Related Servers
- 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.-
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server designed to easily dump your codebase context into Large Language Models (LLMs).13 npm3Apache 2.0
- AlicenseNot gradedqualityAmaintenanceMCP server that lets AI coding tools control and observe a running Node.js process through the chrome devtools protocol (CDP), via a lightweight Debug Adapter Protocol (DAP) bridge.14 npm2MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides VSCode context and filesystem operations for AI assistants.9-
TDQS
A3.7/5.0
Scored across 7 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap: adding, listing, and removing instruments; starting and stopping debug sessions; and reading and clearing logs. The descriptions make it easy to differentiate between them, such as distinguishing 'add_instrument' from 'remove_instruments' and 'read_debug_logs' from 'clear_debug_logs'.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using snake_case, such as 'add_instrument', 'clear_debug_logs', and 'start_debug_session'. There are no deviations in naming conventions, making the set predictable and easy to understand.
Tool Count5/5
With 7 tools, the count is well-scoped for a debugger server, covering core operations like instrument management, session control, and log handling. Each tool earns its place without feeling excessive or insufficient for the domain.
Completeness5/5
The tool set provides complete coverage for a debugger's lifecycle: it includes CRUD operations for instruments (add, list, remove), session management (start, stop), and log handling (read, clear). There are no obvious gaps, as all essential workflows are supported without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues