Ultra Debugger

by alfi-j

261 downloads Not rated yet

GitHub

About

# Ultra Debugger A robust Model Context Protocol (MCP) debugger for JavaScript, TypeScript, JSX, and TSX files. This tool leverages industry-standard tools like ESLint, TypeScript ESLint, and React ESLint plugins to provide comprehensive analysis and debugging capabilities for AI-generated code. ## Key Features -…

Explore

- MCP Integration: Works with AI assistants that support the Model Context Protocol
- Multi-language Support: Analyzes JavaScript, TypeScript, JSX, and TSX files
- ESLint Powered: Uses ESLint with recommended rules for accurate code analysis
- TypeScript Support: Leverages @typescript-eslint for TypeScript-specific rules
- React Support: Uses eslint-plugin-react for JSX/React-specific rules
- Real-time Analysis: Identifies syntax errors, potential bugs, and code quality issues
- Enhanced Fix Suggestions: Provides detailed, context-aware suggestions for resolving issues
- Multi-file Support: Analyze single files or entire projects at once
- Live Analysis: Real-time monitoring of code changes with instant feedback
- Fallback Analysis: Uses custom analysis when ESLint is not available

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name Ultra Debugger

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

From the repository


To use this tool with mcp.so or other MCP registries, you need a proper configuration file. The tool expects an mcp.config.json file with the following format:

json { "mcpServers": { "ultra-debugger": { "command": "node", "args": ["src/mcp/ultra-debugger-mcp.js"], "env": {} } } } ``



This configuration file is included in the repository as

mcp.config.json

.
npm install



javascript

const { analyzeFile, analyzeMultipleFiles } = require('./src/mcp/ultra-debugger-mcp.js');



// Analyze a single file

analyzeFile('path/to/your/file.tsx')

  .then(result => {

    console.log('Analysis result:', result);

  })

  .catch(error => {

    console.error('Analysis failed:', error);

  });



// Analyze multiple files

analyzeMultipleFiles(['app.js', 'component.tsx', 'utils.jsx'])

  .then(results => {

    console.log('Multi-file analysis results:', results);

  })

  .catch(error => {

    console.error('Analysis failed:', error);

  });

`path`

(string): Path to the file or directory to watch

`watch_id`

(string): Unique identifier for this watch session

When running as an MCP server, the Ultra Debugger exposes the following tools:

1. analyze_file - Analyze a JavaScript/TypeScript/JSX/TSX file
- Parameters: file_path (string)

2. analyze_multiple_files - Analyze multiple files
- Parameters: file_paths (array of strings)

3. watch_file - Start live analysis of a file or directory
- Parameters:
- path (string): Path to the file or directory to watch
- watch_id (string): Unique identifier for this watch session

4. unwatch_file - Stop live analysis of a previously watched file or directory
- Parameters: watch_id (string): Unique identifier for the watch session to stop

5. list_watch_sessions - List all active watch sessions
- No parameters

6. get_analysis_report - Get the detailed report from the last analysis operation
- No parameters

7. get_fix_suggestions - Get suggestions for fixing issues found in the last analysis
- No parameters

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "ultra debugger": {
            "ultra-debugger": {
                "command": "node",
                "args": [
                    "src/mcp/ultra-debugger-mcp.js"
                ],
                "env": []
            }
        }
    }
}

McpServers

{
    "ultra-debugger": {
        "command": "node",
        "args": [
            "src/mcp/ultra-debugger-mcp.js"
        ],
        "env": []
    }
}

A robust Model Context Protocol (MCP) debugger for JavaScript, TypeScript, JSX, and TSX files. This tool leverages industry-standard tools like ESLint, TypeScript ESLint, and React ESLint plugins to provide comprehensive analysis and debugging capabilities for AI-generated code.

Key Features

- MCP Integration: Works with AI assistants that support the Model Context Protocol - Multi-language Support: Analyzes JavaScript, TypeScript, JSX, and TSX files - ESLint Powered: Uses ESLint with recommended rules for accurate code analysis - TypeScript Support: Leverages @typescript-eslint for TypeScript-specific rules - React Support: Uses eslint-plugin-react for JSX/React-specific rules - Real-time Analysis: Identifies syntax errors, potential bugs, and code quality issues - Enhanced Fix Suggestions: Provides detailed, context-aware suggestions for resolving issues - Multi-file Support: Analyze single files or entire projects at once - Live Analysis: Real-time monitoring of code changes with instant feedback - Fallback Analysis: Uses custom analysis when ESLint is not available

How It Works

The Ultra Debugger analyzes code using multiple approaches: 1. JavaScript Analysis: Uses ESLint with a comprehensive set of rules to detect: - Syntax errors - Potential bugs - Code quality issues - Best practices violations 2. TypeScript Analysis: Uses @typescript-eslint to detect TypeScript-specific issues: - Type errors - Unused variables - Explicit any usage - Other TypeScript best practices 3. React/JSX Analysis: Uses eslint-plugin-react to detect React-specific issues: - Component structure problems - Prop validation issues - React best practices 4. Live Analysis: Uses file system watchers to monitor code changes in real-time: - Instant feedback on code modifications - Automatic re-analysis when files change - Continuous monitoring of project directories 5. Enhanced Fix Suggestions: Provides context-aware, detailed suggestions: - Generic JavaScript fixes - TypeScript-specific recommendations - React/JSX best practices - Framework-specific guidance 6. Fallback Analysis: When ESLint is not available, uses custom pattern matching to detect: - Debugger statements - Unreachable code - Common coding issues

MCP Configuration

To use this tool with mcp.so or other MCP registries, you need a proper configuration file. The tool expects an mcp.config.json file with the following format: ``

json
{
  "mcpServers": {
    "ultra-debugger": {
      "command": "node",
      "args": ["src/mcp/ultra-debugger-mcp.js"],
      "env": {}
    }
  }
}



This configuration file is included in the repository as

mcp.config.json

.

MCP Tools


When running as an MCP server, the Ultra Debugger exposes the following tools:

1. analyze_file - Analyze a JavaScript/TypeScript/JSX/TSX file
   - Parameters:

file_path

 (string)

2. analyze_multiple_files - Analyze multiple files
   - Parameters:

file_paths

 (array of strings)

3. watch_file - Start live analysis of a file or directory
   - Parameters: 
     -

path

 (string): Path to the file or directory to watch
     -

watch_id

 (string): Unique identifier for this watch session

4. unwatch_file - Stop live analysis of a previously watched file or directory
   - Parameters:

watch_id

 (string): Unique identifier for the watch session to stop

5. list_watch_sessions - List all active watch sessions
   - No parameters

6. get_analysis_report - Get the detailed report from the last analysis operation
   - No parameters

7. get_fix_suggestions - Get suggestions for fixing issues found in the last analysis
   - No parameters

Installation

``bash

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Explore

Setting up with Highlight

From the repository

path

watch_id

Claude Desktop / Cursor

McpServers

Key Features

How It Works

MCP Configuration

MCP Tools

Installation

More like this

Sequential Thinking

Sentry

Github

Filesystem

`path`

`watch_id`