yuzi-ska/DSH-Chrome-devtools
Real Chrome browser control for DeepSeek Harness agents, powered by Chrome DevTo
dsh-chrome-devtools gives DeepSeek Harness agents control over a real Chrome browser via chrome-devtools-mcp: navigation, clicking, typing, screenshots, DOM snapshots, console, network requests, performance traces, and cookies. It registers each MCP tool on ctx.tools as mcpchrome-devtools<tool> (28 tools in the current version across Pages, Snapshots, Interaction, Scripting, Emulation, Console, Network, Performance, Auditing, and Other families -- e.g. navigate_page, take_snapshot, take_screenshot, click, fill_form, evaluate_script, list_console_messages, get_network_request, performance_start_trace, lighthouse_audit). One shared Chrome instance auto-launches; each tool call may run up to 120 seconds (configurable). The MCP row is built into the plugin's cordis.patch.yml, so it is reconciled into the profile's patch-layer stack automatically with zero manual config.
Install
dsh plugin --profile web add github:yuzi-ska/DSH-Chrome-devtoolsThe README states the only install path is the official one-command dsh plugin install: dsh plugin --profile web add github:yuzi-ska/DSH-Chrome-devtools (replace web with your profile name). The repository root is itself an official bundle plugin (package.json declares dsh.bundle and cordis.patch.yml is the patch layer), so the MCP server row is built in and it is ready to use right after install -- no extra components and no MCP configuration to write. Then restart the host (dsh web); every session (including child agents) sees the mcpchrome-devtools* tools. A repo installer script for local/development setups is also documented. No npm registry package is claimed.
Compatibility
Requires DeepSeek Harness (which ships @deepseek-ai/dsh-mcp-client, the bridge plugin), Node.js >= 20 with npx on PATH, pnpm (the package manager behind dsh plugin), and Chrome / Chromium / Edge installed locally (pick one via --channel in the plugin args). Windows / macOS / Linux. Bundle plugins load at startup, so a host restart is required. The server runs via npx -y chrome-devtools-mcp@latest (first use downloads it in about 30-60s; afterwards the npx cache starts it in about a second). One profile mounts one resident server shared by all sessions; the dsh-mcp-client supervisor reconnects a crashed server with exponential backoff and unregisters the tools after 10 consecutive failures.
Details
- Repo: yuzi-ska/DSH-Chrome-devtools
- Category: Agent Capabilities
- Stars: 1
- Version: GitHub source install (no npm registry package claimed); MIT (license not auto-detected by the GitHub API -- repo has no LICENSE file on 2026-09-30)
- Last push: 2026-08-13
- First seen: 2026-08-13
Recent updates
The README documents the requirements table, the install/uninstall steps, the repo installer script options (--check/--uninstall/--profile/--dsh-home/--harness/--plugin-spec/--package-name), the architecture diagram, the tool-capability table, the MCP row config (serverName, command/args, toolCallTimeoutMs, failOnStartupError, env/cwd, reconnect backoff), the chrome-devtools-mcp server options (--headless, --channel, --browserUrl, --isolated, --viewport, --proxy-server, --user-data-dir, --keepAlive), sharing semantics, security notes, a troubleshooting table, and development notes.
FAQ
- How do I install dsh-chrome-devtools?
- Per the README the only install path is the official one-command install: dsh plugin --profile web add github:yuzi-ska/DSH-Chrome-devtools, then restart the host. The repository root is itself an official bundle plugin, so the MCP server is ready right after install with no extra configuration.
- Do I have to install chrome-devtools-mcp separately?
- No -- the README says the server runs via npx -y chrome-devtools-mcp@latest (the same convention Claude Code / Cursor use), so the first use downloads it automatically (about 30-60s) and later starts come from the npx cache in about a second.
- Is it safe to give an agent browser control?
- The README warns browser capability is shell-level trust (it can read/write cookies, issue arbitrary requests, and reach internal networks), so use it only with trusted sessions; page content (DOM snapshots, console, response bodies) also enters the model context and session logs.
Alternatives
Clizo1209/dsh-playwright-browser · egnmosk/dsh-browser-bridge · ben7am1n/dsh-mcp-proxy