Find AI-powered debugging tools that help identify, diagnose, and fix bugs in your code automatically.
Debugging tools are AI-powered software designed to help developers and teams tackle debugging-related tasks more efficiently. These tools are typically published as open-source projects on GitHub and can be integrated into existing workflows via MCP (Model Context Protocol), Claude Skills, or standalone agent frameworks. On Agent Skills Hub, we index 10 quality-scored debugging tools across languages including TypeScript, Rust, C++.
In 2026, the AI agent ecosystem is maturing rapidly. Debugging tools can significantly boost development efficiency by automating repetitive tasks, reducing human error, and providing intelligent suggestions. The top 3 tools — agent-inspect, embedded-debugger-mcp, MemWhale — have earned an average of 693 GitHub stars, reflecting strong community validation. 9 of the listed tools come with clear open-source licenses, ensuring freedom to use and modify.
When choosing a debugging tool, consider these factors: 1) Community activity — GitHub stars and recent commit frequency indicate reliability; 2) Integration method — check if it supports MCP, Claude, or your preferred agent framework; 3) Language compatibility — the most common language in this list is TypeScript; 4) Quality score — Agent Skills Hub's composite score evaluates code quality, documentation completeness, and maintenance activity. Our recommendation: start with agent-inspect — it ranks highest in both star count and quality score.
Local evidence debugger and trajectory-test toolkit for TypeScript AI agents: inspect causal runs, catch wrong tool paths in CI, and share safe offline evidence.
MCP server + CLI + Codex/Claude skill for embedded debugging via probe-rs or OpenOCD — ARM Cortex-M, RISC-V, and Xtensa (ESP32), with AI crash diagnosis
Persistent, local memory for developers and their coding agents. Records commands, output, errors, and the fixes that worked into SQLite and serves them over MCP.
disassembler, decompiler and debugger in one, with a built-in mcp server: point an ai at a binary and it can debug it, not just read it. ida-style listing, pseudocode (f5), x64dbg-style debugger (windows and linux), binary diff, lua plugins. reads pe, elf and mach-o. runs on windows, linux and macos.
Testing and evaluation platform to chat, inspect, and debug MCP servers, MCP apps, and ChatGPT apps.
Connect Cursor, Copilot & Claude AI directly to Cheat Engine via MCP. Automate reverse engineering, pointer scanning, and memory analysis using natural language.
Game Boy / Game Boy Color / Super Game Boy emulator and debugger with embedded MCP server for macOS, Windows, Linux, BSD and RetroArch.
An open-source collection of embedded development and debugging skills for Claude Code, Copilot, TRAE, and other AI coding assistants that support the Skill protocol. Once installed, the AI assistant can directly operate compilers, debuggers, and communication buses, automating the full workflow from code generation to hardware verification.
Gift your VS Code agent a real debugger: breakpoints, stepping, inspection.
Adversarial AI bug hunter with auto-fix skill for Claude Code, Cursor, Codex CLI, GitHub Copilot CLI, Kiro CLI, Opencode, Pi Coding Agent, and more. Multi-agent pipeline finds security vulnerabilities, logic errors, and runtime bugs — then fixes them autonomously on a safe branch.
| Tool | Stars | Language | License | Score |
|---|---|---|---|---|
| agent-inspect | ★ 233 | TypeScript | MIT | 67 |
| embedded-debugger-mcp | ★ 141 | Rust | MIT | 74 |
| MemWhale | ★ 131 | Rust | MIT | 62 |
| ceasta | ★ 110 | C++ | GPL-3.0 | 66 |
| inspector | ★ 2.2k | TypeScript | — | 72 |
| cheatengine-mcp-bridge | ★ 1.2k | Lua | MIT | 78 |
| Gearboy | ★ 1.2k | C++ | GPL-3.0 | 70 |
| embeddedskills | ★ 619 | Python | MIT | 75 |
| DebugMCP | ★ 539 | TypeScript | MIT | 76 |
| bug-hunter | ★ 487 | JavaScript | MIT | 75 |
The top debugging tools in 2026 are agent-inspect, embedded-debugger-mcp, MemWhale. Agent Skills Hub ranks 10 options by GitHub stars, quality score (6 dimensions including completeness, examples, and agent readiness), and recent activity. The list is rebuilt every 8 hours from live GitHub data.
agent-inspect (233 stars) is the most adopted choice for general debugging workflows, written in TypeScript. embedded-debugger-mcp (141 stars) is a strong alternative and uses Rust instead. Pick by your existing stack: match the language and runtime your team already uses to minimize integration cost. If unsure, start with agent-inspect — it has the deepest community and the most examples online.
Avoid pre-built debugging tools when (1) your use case requires deep customization that the tool's plugin system doesn't support, (2) you have strict compliance requirements that ban third-party dependencies, (3) the tool's maintenance is inactive (last commit >6 months ago), or (4) your data volume is small enough that a 50-line custom script is cheaper than learning the tool. For most production workflows above 100 requests/day, the time savings from a maintained tool outweigh the customization loss.
Debugging focuses specifically on find ai-powered debugging tools that help identify, diagnose, and fix bugs in your code automatically. Code Review is a related but distinct category — see https://agentskillshub.top/best/code-review/ for those tools. The two often appear in the same agent pipeline but solve different problems: choose debugging when your primary goal is the specific task, and code review when the workflow is broader.
For most teams, yes. agent-inspect has 233 stars worth of community testing, handles edge cases you haven't thought of, and ships with documentation. Build your own only when (1) your requirements are deeply non-standard, (2) you have a security/compliance reason to avoid OSS dependencies, or (3) the maintenance burden is small enough (<200 lines of code) that you'll save time long-term. The break-even point is usually around 2-3 weeks of dev time saved.
Most debugging tools listed are open source under permissive licenses (MIT, Apache 2.0). A handful offer paid managed/cloud versions on top of free self-hosted core. Always check the LICENSE file on each tool's GitHub repository before commercial use — some use AGPL or non-commercial restrictions that may not fit your deployment model.
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy, covering 11 red-flag categories including credential harvesting, data exfiltration, and curl | sh installers. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible:
