Java MCP DebuggerJava MCP Debugger is a VS Code extension that exposes Java debugging as Model Context Protocol (MCP) tools so coding agents can work with live runtime state, not only static sources and traces. Today's agents often investigate bugs through static analysis: source, logs, and stack dumps. That helps, but inference about execution flow is fragile because the model cannot reliably see what actually happened at runtime: real variable values, object mutations, thread interactions, branching paths, or framework/runtime internals. Complex issues still push developers back to the debugger to step execution, inspect state, verify hypotheses and then return to the agent with findings. This extension closes that loop. It lets an agent drive an ordinary Java debug session (the same adapters and workflows you already use in the editor):
Implementation-wise, it reuses VS Code debugger APIs together with the Java debug adapter not a reinvented JVM debugger so capability stays aligned with the ecosystem you rely on today. Prerequisites
Connect MCPThe extension listens for MCP Streamable HTTP at CursorCreate or edit
Reload the window and confirm the java-debugger server appears in your MCP list. VS CodeIf your build supports MCP via workspace JSON, create
Other VS Code MCP layouts may vary; wherever HTTP servers are declared, point them at Check the Output channel “Java MCP Debugger” for confirmation that the server is listening. Using it with your agent
AuthorMazen Aissa For questions, bug reports, or anything else related to this extension:
|