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 Rust, TypeScript, Lua.
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 — embedded-debugger-mcp, inspector, cheatengine-mcp-bridge — have earned an average of 730 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 Rust; 4) Quality score — Agent Skills Hub's composite score evaluates code quality, documentation completeness, and maintenance activity. Our recommendation: start with embedded-debugger-mcp — it ranks highest in both star count and quality score.
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
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, debugger and 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.
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.
Gift your VS Code agent a real debugger: breakpoints, stepping, inspection.
Sega Master System / Game Gear / SG-1000 emulator, debugger and embedded MCP server for macOS, Windows, Linux, BSD and RetroArch.
MCP server plugin for x64dbg debugger - enables AI agents and external tools to control debugging via JSON-RPC 2.0 over HTTP/SSE
Local execution trees for TypeScript AI agents. agent-inspect helps you understand what happened inside an AI agent run — locally. It turns manual steps, tool calls, LLM calls, structured logs, failures, durations, and run metadata into readable execution trees you can inspect from the terminal. It is built for TypeScript/Node.js developers..
| Tool | Stars | Language | License | Score |
|---|---|---|---|---|
| embedded-debugger-mcp | ★ 141 | Rust | MIT | 74 |
| inspector | ★ 2.1k | TypeScript | — | 72 |
| cheatengine-mcp-bridge | ★ 1.2k | Lua | MIT | 78 |
| Gearboy | ★ 1.2k | C++ | GPL-3.0 | 70 |
| embeddedskills | ★ 551 | Python | MIT | 76 |
| bug-hunter | ★ 487 | JavaScript | MIT | 75 |
| DebugMCP | ★ 471 | TypeScript | MIT | 75 |
| Gearsystem | ★ 384 | C++ | GPL-3.0 | 67 |
| x64dbg-mcp | ★ 361 | C++ | MIT | 69 |
| agent-inspect | ★ 342 | TypeScript | MIT | 68 |
The top debugging tools in 2026 are embedded-debugger-mcp, inspector, cheatengine-mcp-bridge. 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.
embedded-debugger-mcp (141 stars) is the most adopted choice for general debugging workflows, written in Rust. inspector (2.1k stars) is a strong alternative and uses TypeScript instead. Pick by your existing stack: match the language and runtime your team already uses to minimize integration cost. If unsure, start with embedded-debugger-mcp — 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. embedded-debugger-mcp has 141 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.
