Debugium
Let your coding agent drive live breakpoints and inspection across polyglot apps while you fix bugs before release.
Overview
Debugium is a MCP server for the Ship phase that bridges AI agents to live debugging for Python, JS, TS, Rust, Java, and C/C++.
What is this MCP server?
- MCP bridge for six runtimes: Python, JavaScript, TypeScript, Rust, Java, and C/C++
- stdio npm package @algiras/debugium (registry v0.1.2) for Claude Code, Cursor, and other MCP clients
- AI-driven live debugger sessions instead of copy-pasting stack traces into chat
- GitHub-hosted server io.github.Algiras/debugium v1.0.0 on the official MCP schema
- Supports 6 language families: Python, JS, TS, Rust, Java, C/C++
- Published MCP server schema version 1.0.0; npm package @algiras/debugium v0.1.2
- Transport: stdio via npm registryType
Community signal: 4 GitHub stars.
What problem does it solve?
You waste cycles pasting stack traces into chat while the real bug only shows up under breakpoints and live variables.
Who is it for?
Indie builders debugging polyglot backends or native extensions who already use Claude Code or Cursor with MCP stdio servers.
Skip if: Teams that only need linting or unit tests, or projects in languages Debugium does not list.
What do I get? / Deliverables
Your agent can drive live debug sessions in supported runtimes so you confirm fixes faster before you ship.
- Agent-callable live debug control wired into your MCP client
- Faster reproduction and fix verification across supported runtimes
- Fewer log-only debugging loops during Ship testing
Recommended MCP Servers
Journey fit
Interactive debugging sits in the Ship phase because it validates behavior and defects immediately before you call a release done. Testing is the canonical shelf for debugger tooling that reproduces failures, steps through code, and confirms fixes under agent control.
How it compares
Live-debug MCP integration, not a static code-review skill or test runner.
Common Questions / FAQ
Who is Debugium for?
Solo and small-team developers who want their AI agent to operate a real debugger during Ship-phase testing across six supported languages.
When should I use Debugium?
Use it when a defect needs live inspection, stepping, or runtime state you cannot capture from logs alone, right before or during release testing.
How do I add Debugium to my agent?
Add the @algiras/debugium npm MCP server with stdio transport to your client’s MCP config, install dependencies for your target language, then restart the agent so debug tools appear in the session.