Bherbruck Mcp Debugger
bherbruck-mcp-debugger is a Claude Code plugin for the Operate phase that registers an MCP multilanguage debugger so your agent can investigate JavaScript/TypeScript and Python runtime issues.
by bherbruck · github.com/bherbruck/mcp-debugger
Attach a multilanguage MCP debugger so Claude Code can break, inspect, and step through Python and JavaScript/TypeScript while you fix bugs.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install bherbruck-mcp-debugger@bherbruck/mcp-debuggerBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:bherbruck/mcp-debugger") and the paste-ready config with skillselion.get_install_config("plugin:bherbruck/mcp-debugger").
What it does
bherbruck-mcp-debugger is a one-plugin Claude Code marketplace that registers an MCP-oriented debugging integration for multilanguage codebases. Solo builders who ship with agents often stall when reproduction requires a real debugger instead of printf guesses; exposing debugger capabilities over MCP lets Claude Code set breakpoints, inspect variables, and walk execution in JavaScript/TypeScript and Python without leaving the chat. The listing is lightweight on marketing copy but clearly positions around debug, debugger, debugging, MCP, and multilanguage keywords, which maps to Operate errors work and overlapping Ship testing sessions. Install it when you want structured agent access to runtime inspection rather than ad-hoc log reading. Expect to wire the MCP server locally, match your language runtime, and treat this as a development integration—not a hosted observability product. Confidence is moderate because SKILL-level invoke rules are not in the catalog excerpt.
Highlights
- MCP server focused on debugger workflows for agent-driven troubleshooting
- Multilanguage coverage aligned with JavaScript/TypeScript and Python stacks
- Single-plugin bundle (1 plugin) from the bherbruck/mcp-debugger repo
- Keyword taxonomy spans debug, debugger, debugging, and MCP integration
- Community-listed marketplace entry discoverable in Skillselion plugin browse
Why builders use it
Agent-assisted coding breaks down when you cannot attach a real debugger to stepping, locals, and breakpoints across JS/TS and Python.
After you add the marketplace plugin and configure the MCP debugger, Claude Code can drive interactive debugging sessions instead of guessing from static code alone.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is bherbruck-mcp-debugger for?
Solo and small-team builders using Claude Code who want MCP-exposed debugger tools for multilanguage local development.
When should I use bherbruck-mcp-debugger?
Use it when failures need breakpoints, stack inspection, or stepped reproduction in Python or JavaScript/TypeScript during build, ship, or operate debugging.
How do I add bherbruck-mcp-debugger to my agent?
Register the bherbruck/mcp-debugger Claude Code plugin marketplace in Claude Code, then configure the MCP debugger server per the repo README and enable it for your workspace.
Comments
Share how you use bherbruck-mcp-debugger, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.