Java Debug Adapter Protocol
MCP server that bridges AI assistants with Java debugging capabilities through the Debug Adapter Protocol (DAP), enabling remote debugging of Java applications by providing tools to attach to debug sessions, inspect thread states, examine stack traces and variable scopes, evaluate expressions in debugging contexts, and control execution flow. Built with Quarkus and Java 21, the implementation acts as a protocol translator between MCP's tool-based interface and DAP's debugging commands, allowing AI assistants to perform interactive debugging tasks like analyzing application state, inspecting variables, and stepping through code execution. Designed for developers who want AI assistance with debugging Java applications, troubleshooting runtime issues, and performing automated debugging workflows where programmatic access to debugging capabilities enhances the development process.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.
Scan details: Circle-IR · 2026-09-19 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- productivity
- Source
- PulseMCP
- Repository
- github.com/igorrhamon/mcp_debugger
- Author type
- human
- Last scanned
- 2026-09-19
- Updated
- 2026-09-19
Use via MCP
Resolve Java Debug Adapter Protocol from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.