Skip to main content
Glama
Sign In
Ultra Debugger

Ultra Debugger

by alfi-j
OverviewSchemaRelated ServersDiscussionsAdmin
JavaScript
Local

Ultra Debugger CLI

Ultra Debugger is a command-line tool for debugging code and analyzing performance.

Prerequisites

  • Node.js version 18 or higher

Installation

npm install

Usage

# Debug a code snippet
node src/cli/ultra-debugger-cli.js debug "console.log('hello world');" javascript

# Analyze code performance
node src/cli/ultra-debugger-cli.js analyze "for(let i=0;i<1000000;i++){}"

# Debug a file
node src/cli/ultra-debugger-cli.js debug-file path/to/your/file.js

Or use the npm script:

npm start

Or:

npm run cli debug "console.log('hello world');"

CLI Commands

  • debug <code> [language] - Debug a code snippet

  • analyze <code> [metrics] - Analyze code performance

  • debug-file <file-path> [language] - Debug a file

Examples

# Debug JavaScript code
node src/cli/ultra-debugger-cli.js debug "function add(a,b){return a+b;}" javascript

# Analyze performance with specific metrics
node src/cli/ultra-debugger-cli.js analyze "for(let i=0;i<1000000;i++){}" memory cpu

# Debug a JavaScript file
node src/cli/ultra-debugger-cli.js debug-file example.js

Available Tools

4 tools
analyze_js_fileC

Analyze a JavaScript file for potential issues using ESLint

Inputs: file_path (required).

analyze_multiple_js_filesC

Analyze multiple JavaScript files for potential issues

Inputs: file_paths (required).

get_analysis_reportB

Get the detailed report from the last analysis operation

Inputs: no named parameters.

get_fix_suggestionsB

Get suggestions for fixing issues found in the last analysis operation

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools are mostly distinct, with clear separation between analysis operations and report/fix retrieval. However, 'analyze_js_file' and 'analyze_multiple_js_files' could potentially be confused as they serve very similar purposes, with the latter essentially being a batch version of the former. The descriptions help clarify this distinction.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case naming. The verbs 'analyze', 'get', and 'get' are appropriately used for their respective operations, creating a predictable and readable naming convention throughout the toolset.

    Tool Count5/5

    With 4 tools, this is a well-scoped set for a debugging/analysis server. Each tool earns its place by covering distinct aspects of the workflow: file analysis, batch analysis, report retrieval, and fix suggestions. The count is appropriate for the apparent purpose.

    Completeness3/5

    The toolset covers analysis and reporting well but has notable gaps. There's no way to apply fixes automatically or manage analysis configurations. The domain suggests a debugging workflow, but without tools to implement suggestions or customize analysis rules, agents may hit dead ends after identifying issues.

    Resources

    Related MCP Connectors

    Appeared in Searches