home / mcp / mcp debugger mcp server
Provides multi-language debugging tools and adapters via MCP to enable AI agents to debug Python, JavaScript, and Rust code.
Configuration
View docs{
"mcpServers": {
"debugmcp-mcp-debugger": {
"command": "node",
"args": [
"C:/path/to/mcp-debugger/dist/index.js",
"--log-level",
"debug",
"--log-file",
"C:/path/to/logs/debug-mcp-server.log"
]
}
}
}mcp-debugger is an MCP server that exposes debugging operations as structured API calls to empower AI agents with multi-language debugging capabilities. It supports Python, JavaScript, and Rust debugging through language-specific adapters, enabling step-by-step debugging workflows that integrate with your AI workflows across languages.
You can use mcp-debugger with an MCP client to create and manage debugging sessions, set breakpoints, start and control debugging, and fetch variables and stack traces. Use it to orchestrate debugging across languages from your AI agent, with clear, machine-readable responses that you can parse and react to.
Prerequisites: you need Node.js installed on your system. You can verify with node -v and npm -v.
npm install -g @debugmcp/mcp-debuggerYou can run the server directly or interact via the command line to see available options.
mcp-debugger --helpConfigure your MCP client to launch the server as a stdio process. Use the following example configuration to start a debugging session for a client that can communicate via JSON-RPC over stdio.
{
"mcpServers": {
"mcp-debugger": {
"type": "stdio",
"command": "node",
"args": ["C:/path/to/mcp-debugger/dist/index.js", "--log-level", "debug", "--log-file", "C:/path/to/logs/debug-mcp-server.log"]
}
}
}Create a debug session, set breakpoints, and start debugging a script to verify the server is functioning correctly.
Create a new debugging session for a chosen language and session name.
List all active debugging sessions.
Set a breakpoint in a specified file at a given line.
Start debugging a specified script within an active session.
Retrieve the current stack trace for the active frame.
Get variable scopes for a specific stack frame.
Fetch variables within a given scope.
Step over the current line of code.
Step into a function call.
Step out of the current function.
Continue running the program until the next event or breakpoint.
Close and clean up a debugging session.
Pause the currently running program.
Evaluate an arbitrary expression in the current context.
Get the source code context around the current execution point.