Chromium Browser

Operate the configured Chrome DevTools MCP against the existing shared browser without disrupting unrelated tabs or authenticated state.

Environment Contract

Treat ~/.local/libexec/mcp/chrome-devtools and the tools exposed in the current session as authoritative. The wrapper owns server versioning, flags, logging, and browser attachment; do not run the MCP package directly.
The MCP attaches to an existing remote-debugging browser. Never launch a fallback browser or create another profile when attachment fails.
Treat the browser as shared, authenticated, and concurrently used by the user and other agents. Inspect only pages relevant to the task and do not surface unrelated tab titles or content.
Trust the live tool inventory over remembered server features. An absent tool is unavailable in this session; do not advise editing client MCP configuration as a troubleshooting shortcut.