Debugium MCP Server

AI-driven live debugger with MCP bridge for Python, JS, TS, Rust, Java, C/C++

Local serverstdioPython

What is the Debugium MCP server?

Most knowledge and memory work still happens through a UI a human drives. Debugium MCP server moves it into the conversation instead. AI-driven live debugger with MCP bridge for Python, JS, TS, Rust, Java, C/C++.

The short version

Debug Python, JavaScript, TypeScript, C, C++, Rust, Java, Scala, and WebAssembly programs from your browser — with AI-driven analysis through the Model Context Protocol.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • Flag — Default
  • Category — Tools
  • Orient — get_debug_context ★ (paused location + locals + stack + source in one call)
  • Breakpoints — set_breakpoint, set_breakpoints, set_logpoint, list_breakpoints, clear_breakpoints, set_function_breakpoints, set_exception_breakpoints
  • Execution — continue_execution, step_over, step_in, step_out, pause, goto, disconnect, terminate, restart
  • Inspection — get_stack_trace, get_scopes, get_variables, evaluate, get_threads, get_source, get_capabilities, loaded_sources, source_by_reference, step_in_targets
  • Mutation — set_variable, set_expression
  • Output — get_console_output, wait_for_output (with from_line to avoid stale matches)
  • Memory — read_memory, write_memory, disassemble (native debugging)
  • History — get_timeline, get_variable_history, compare_snapshots, find_first_change
  • Annotations — annotate, get_annotations, add_finding, get_findings
  • Watches — add_watch, remove_watch, get_watches

What it needs from you

cargo install wasm-pack

Getting it running

The server ships on PyPI as debugpy, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Debugium's toolset — Flag, Category, Orient and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Algiras; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Debugium.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
FlagDefault
CategoryTools
Orientget_debug_context ★ (paused location + locals + stack + source in one call)
Breakpointsset_breakpoint, set_breakpoints, set_logpoint, list_breakpoints, clear_breakpoints, set_function_breakpoints, set_exception_breakpoints, set_data_breakpoint, list_data_breakpoints, clear_data_breakpoints, breakpoint_loca
Executioncontinue_execution, step_over, step_in, step_out, pause, goto, disconnect, terminate, restart
Inspectionget_stack_trace, get_scopes, get_variables, evaluate, get_threads, get_source, get_capabilities, loaded_sources, source_by_reference, step_in_targets
Mutationset_variable, set_expression
Outputget_console_output, wait_for_output (with from_line to avoid stale matches)
Memoryread_memory, write_memory, disassemble (native debugging)
Historyget_timeline, get_variable_history, compare_snapshots, find_first_change
Annotationsannotate, get_annotations, add_finding, get_findings
Watchesadd_watch, remove_watch, get_watches
Compoundstep_until, step_until_change, continue_until, run_until_exception, explain_exception, get_call_tree, restart_frame
Sessionget_sessions, list_sessions, launch_session, attach_session, stop_session, export_session, import_session

How to install the Debugium MCP server

{
  "mcpServers": {
    "debugium": {
      "command": "debugium",
      "args": ["mcp"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

cargo install wasm-pack

Example prompts to try

  • Use Debugium to Flag.
  • Use Debugium to Category.
  • Use Debugium to Orient.

Frequently asked questions

It connects Debugium to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Flag, Category, Orient, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Debugium directly.