Ultra Debugger

What is Ultra Debugger?

Ultra Debugger is a Model Context Protocol (MCP) server that provides static code analysis for JavaScript, TypeScript, JSX, and TSX files. It uses ESLint, @typescript‑eslint, and eslint‑plugin‑react to detect syntax errors, potential bugs, code quality issues, and best‑practice violations, and is designed to help AI assistants debug and improve AI‑generated code.

How to use Ultra Debugger?

Clone the repository, run npm install, then start the MCP server with npm start. The server exposes MCP tools such as analyze_file, analyze_multiple_files, watch_file, and unwatch_file. Integrate it by adding an mcp.config.json pointing to src/mcp/ultra-debugger-mcp.js.

Key features of Ultra Debugger

• MCP integration for AI‑assisted code analysis
• Supports JavaScript, TypeScript, JSX, and TSX
• ESLint‑powered with recommended rules
• TypeScript‑specific rules via @typescript‑eslint
• React/JSX‑specific rules via eslint‑plugin‑react
• Real‑time live analysis with file watching
• Enhanced, context‑aware fix suggestions
• Multi‑file analysis and project‑wide scanning
• Fallback analysis when ESLint is unavailable

Use cases of Ultra Debugger

• Automatically analyze code generated by an AI assistant (JavaScript, TypeScript, React)
• Identify and fix syntax errors, potential bugs, and code quality issues
• Provide real‑time feedback on code changes during development
• Offer detailed, framework‑specific fix recommendations

FAQ from Ultra Debugger

What makes Ultra Debugger different from running ESLint directly?

Ultra Debugger is specifically built for MCP‑enabled AI assistants, exposing tools (analyze_file, watch_file, etc.) that can be called programmatically. It also includes enhanced, context‑aware fix suggestions and fallback analysis when ESLint is not installed.

What are the runtime/dependency requirements?

Node.js is required. Install dependencies via npm install. ESLint, @typescript‑eslint, and eslint‑plugin‑react are used, but the tool includes a fallback when they are unavailable.

Where does analysis data live?

Analysis results are returned directly via MCP tool responses and printed to the server console. No external storage or server is involved — all analysis is performed locally.

Are there any known limits?

Ultra Debugger performs static analysis only—it does not execute code. When ESLint is not available, its rules are limited. Live analysis reports to the console, not through MCP tools directly. Proper file extensions are required to detect the file type.

What transports and authentication does it use?

Ultra Debugger runs as an MCP server using standard stdio transport (configured via mcp.config.json). No authentication is documented — it is designed for local or trusted environments.