The chrome-debugger-mcp is an MCP server designed for breakpoint-driven debugging of Chrome applications, allowing AI agents to interact with real Chrome tabs for runtime inspection and execution control.
From the registry: Chrome breakpoint debugging MCP server for inspecting runtime values and stepping through code

Please install the `chrome-debugger-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Google Chrome** — Chrome must be installed locally (https://www.google.com/chrome/)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","chrome-debugger-mcp"]
Note: Breakpoint-driven Chrome debugging via CDP. Tools for set_breakpoint, getScopeVariables, evaluate, step, etc. Uses dedicated Chrome profile at ~/.chrome-debug-profile, port 9222.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
Validate oh-my-posh configurations and segment snippets against the official schema.