Pointbreak
by Kevin Swiber
Glass-box debugging for AI assistants — real debugger access through MCP
See https://withpointbreak.com
Features
- Breakpoint Management — Set breakpoints via natural language, visible in IDE UI
- Variable Inspection — Inspect actual values, object properties, and call stacks at runtime
- Execution Control — Step through, step into, step over, pause, resume, continue to next breakpoint
- IDE Integration — Native VS Code debugger integration via Debug Adapter Protocol (DAP)
- Multi-Language — Python (debugpy), JavaScript/TypeScript (Node Debug), Rust/C/C++ (CodeLLDB), Go (Delve)
- Multi-AI — Works with GitHub Copilot, Cursor, Claude Code, Windsurf, Goose, and any MCP-compatible tool
Superpowers
Pointbreak transforms AI debugging from “guess and print statements” to real runtime analysis. AI assistants can now set breakpoints, step through code, and inspect actual program state — the same capabilities developers use manually.
Who it’s for: Developers using AI coding assistants who want their AI to debug, not just generate code.
Key benefit: AI can identify root causes by observing actual execution, not simulating or guessing.
Zero-config for Copilot/Cursor — MCP server auto-registers. External assistants (Claude Code, etc.) require manual MCP configuration.
Pricing
Free to use. Proprietary software (not open source).
Limitations
- Requires language-specific debug adapter installed
- VS Code-compatible editors only (VS Code, Cursor, Windsurf)
- External AI assistants require manual MCP server registration
Related
- Model Context Protocol — Underlying protocol
- Debug Adapter Protocol — IDE debugging standard
- MCP Inspector — Debugs MCP servers themselves (different purpose)