Developer · Local MCP server
Chrome Debugger MCP
Chrome breakpoint debugging MCP server for inspecting runtime values and stepping through code.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.BitePro/chrome-debugger-mcp- Version
- 1.0.4
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-03-16
- Updated
- 2026-03-16
- Publisher
- BitePro (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/BitePro) · how
- Repository
- github.com/BitePro/chrome-debugger-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | chrome-debugger-mcp | 1.0.4 | stdio |
How to connect Chrome Debugger MCP
Chrome Debugger MCP runs locally from a Node.js package published to the npm registry: chrome-debugger-mcp version 1.0.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y chrome-debugger-mcp@1.0.4.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"chrome-debugger-mcp": {
"command": "npx",
"args": [
"-y",
"chrome-debugger-mcp@1.0.4"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| ChippBuild and manage Chipp AI apps: prompts, knowledge, custom actions, and chat with your apps. | Remote · HTTPLive check: sign-in required |
| ChipzenAI poker arena for agents. Play rated poker on chipzen.ai against LLM bots and human-built bots. | Local · stdio |
| ChirpStackManage and live-debug LoRaWAN devices on a ChirpStack v4 network server over its gRPC API. | Local · stdio |
| ChromaDB Remote MCP ServerRemote ChromaDB vector database MCP server with streamable HTTP transport. | Remote & Local · HTTPLive check: ✗ no handshake |
| Chromedevtoolsmcp MCPA paid remote MCP for AI agent browser DevTools MCP, built to return verdicts, receipts, usage logs,. | Remote · HTTPLive check: ✗ no handshake |
| Chromium BridgeMCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code: browser automation. | Local · stdio |
| ChronTimestamped audit log for every AI conversation - stored locally in SQLite, owned by you. | Local · stdio |
| Chronicle MCPLocal MCP server to sync, clean, and index AI chat logs locally. Saves up to 40% context tokens. | Local · stdio |