MCP server exposing Chrome DevTools Protocol debugging capabilities
MCP server exposing Chrome DevTools Protocol debugging capabilities. Exposed over MCP by the mcp js debugger mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
An MCP (Model Context Protocol) server that exposes Chrome DevTools Protocol debugging capabilities, enabling AI assistants to debug JavaScript and TypeScript applications.
Everything the assistant can do here goes through one of these:
connect_debugger — Connect to a CDP endpoint via WebSocket URLdisconnect_debugger — Disconnect from a debugging sessionset_breakpoint — Set a breakpoint by URL and line numberremove_breakpoint — Remove a breakpoint by IDlist_breakpoints — List all breakpoints in a sessionresume_execution — Resume execution after pausestep_over — Step over the current statementstep_into — Step into a function callstep_out — Step out of the current functionpause_execution — Pause running executionget_call_stack — Get the current call stack with source locationsevaluate_expression — Evaluate a JavaScript expressionThe server ships on npm as mcp-js-debugger, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Js Debugger's toolset — connect_debugger, disconnect_debugger, set_breakpoint and 11 more — is a fair guide to whether it matches your workflow. It is maintained by johngrimes; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| connect_debugger | Connect to a CDP endpoint via WebSocket URL |
| disconnect_debugger | Disconnect from a debugging session |
| set_breakpoint | Set a breakpoint by URL and line number |
| remove_breakpoint | Remove a breakpoint by ID |
| list_breakpoints | List all breakpoints in a session |
| resume_execution | Resume execution after pause |
| step_over | Step over the current statement |
| step_into | Step into a function call |
| step_out | Step out of the current function |
| pause_execution | Pause running execution |
| get_call_stack | Get the current call stack with source locations |
| evaluate_expression | Evaluate a JavaScript expression |
| get_scope_variables | Get variables in a scope |
| set_variable_value | Modify a variable's value |
Or add to `.mcp.json`:
```json
{
"mcpServers": {
"mcp-js-debugger": {
"command": "npx",
"args": ["mcp-js-debugger"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.