Ts Mcp Debugger
Drive breakpoints, profiling, and hang detection on Node/TypeScript processes through your agent instead of juggling separate debug UIs.
Overview
io.github.DigitalDefiance/ts-mcp-debugger is an MCP server for the Operate phase that provides 25+ Node.js/TypeScript debugging tools including breakpoints, profiling, and hang detection for agents.
What is this MCP server?
- 25+ debugging tools: breakpoints, profiling, hang detection per server description
- Enterprise-oriented Node.js and TypeScript debugging via MCP
- stdio npm package @ai-capabilities-suite/mcp-debugger-server
- Version 1.0.2 on MCP schema 2025-10-17
- Lets agents inspect live or local TS/Node processes without leaving the chat thread
- npm identifier @ai-capabilities-suite/mcp-debugger-server, stdio transport
- Repository: github.com/digitaldefiance/ai-capabilities-suite
What problem does it solve?
Node and TypeScript production issues force constant context switching between chat, debugger GUIs, and logs when you debug alone.
Who is it for?
Indie backend builders running TypeScript services who want agent-assisted deep debugging on stalls, leaks, and breakpoints.
Skip if: Frontend-only static sites, languages outside the Node/TS debugger scope, or teams forbidden from attaching debuggers to shared environments.
What do I get? / Deliverables
Your agent can set breakpoints, profile, and detect hangs on Node/TS processes through MCP instead of you hand-driving every debug step.
- Agent-driven breakpoint and step debugging on Node/TS runtimes
- Profiling and hang-detection signals surfaced inside the agent thread
- Consolidated debugger tool surface (25+ tools per vendor description) via MCP
Recommended MCP Servers
Journey fit
Production-adjacent debugging and hangs surface after ship; operate/errors is the canonical home for tooling that stabilizes running Node services. Errors covers intermittent failures, stalls, and performance cliffs—exactly where breakpoint and profiler MCP tools earn their keep.
How it compares
Live debugger MCP for Node/TS, not a static code-review skill or generic log tailer.
Common Questions / FAQ
Who is ts-mcp-debugger for?
Solo developers and small teams shipping Node.js or TypeScript backends who use MCP agents and need interactive debugging without leaving the agent session.
When should I use ts-mcp-debugger?
Use it in operate and errors when services hang, CPU spikes, or breakpoints are needed locally or in a controlled debug environment—not as a substitute for production APM alone.
How do I add ts-mcp-debugger to my agent?
Install @ai-capabilities-suite/mcp-debugger-server from npm, configure it as a stdio MCP server in your host, ensure the target Node/TS process is debuggable, then invoke the debugger tools from your agent.