No red flags found in any of the 11 categories — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against the SlowMist agent-security taxonomy, refreshed every 8 hours. Full audit →
by szymdzum · MCP Server · ★ 148
Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h
🔒 Is browser-debugger-cli safe to install? View the security audit →
Browser Debugger CLI Chrome DevTools Protocol in your terminal. Opens a persistent connection to Chrome where commands can be executed sequentially via Unix pipes. Designed for AI agents and developers who want direct browser control without framework overhead. Why bdg? Raw CDP access - All 644 protocol methods available directly Token efficient - No overhead from MCP tool definitions; progressive discovery loads only what's needed Self-correcting - Errors clearly exposed with semantic exit codes and suggestions Composable - Unix philosophy: pipes, jq, shell scripts work naturally When to use alternatives: Puppeteer/Playwright: Complex multi-step scripts, mature testing ecosystem Chrome DevTools MCP: Already invested in MCP infrastructure Built for agents:
| Stars | 148 |
| Forks | 9 |
| Language | TypeScript |
| Category | MCP Server |
| License | MIT |
| Quality Score | 73.5112464935635/100 |
| Open Issues | 32 |
| Last Updated | 2026-06-28 |
| Created | 2025-10-31 |
| Platforms | browser, claude-code, cli, mcp, node |
| Est. Tokens | ~1259k |
These tools work well together with browser-debugger-cli for enhanced workflows:
Looking for a browser-debugger-cli alternative? If you're comparing browser-debugger-cli with other mcp server tools, these 6 projects are the closest alternatives on Agent Skills Hub — ranked by topic overlap, star count, and community traction.
One command for every interface—search, run, and inspect real software across APIs, browsers, desktops, local
Web tasks that compile. Other browser tools tell your AI agent the click worked. chrome-agent reads the page b
🔮 Platform-neutral Browser Use for AI agents: real Chrome automation with a CLI + SDKs, no lock-in, dead simp
Multi-runtime automation infrastructure for AI agents. Native CDP browser control, metadata-driven Recipe syst
Sync MCP servers, Skills, Agents & Commands across Claude Code, Cursor, OpenCode, Codex. One config, all tools
The missing linter and lsp for AI coding assistants. Validate CLAUDE.md, AGENTS.md, SKILL.md, hooks, MCP. Plug
Explore other popular mcp server tools:
browser-debugger-cli is CLI tool for agents to quickly access browser telemetry (DOM, network, console) via Chrome DevTools Protocol.. It is categorized as a MCP Server with 148 GitHub stars.
browser-debugger-cli is primarily written in TypeScript. It covers topics such as ai-agents, ai-tools, automation.
You can find installation instructions and usage details in the browser-debugger-cli GitHub repository at github.com/szymdzum/browser-debugger-cli. The project has 148 stars and 9 forks, indicating an active community.
browser-debugger-cli is released under the MIT license, making it free to use and modify according to the license terms.
The top alternatives to browser-debugger-cli on Agent Skills Hub include Uni-CLI, chrome-agent, open-browser-use. Each offers a different approach to the same problem space — compare them side-by-side by stars, quality score, and community activity.
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy, covering 11 red-flag categories including credential harvesting, data exfiltration, and curl | sh installers. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible: