io.github.dashi96/chromium-bridge MCP Server
io.github.dashi96/chromium-bridge
What this kind of tool is for
- Automate a build, test, or deployment step you repeat by hand.
- Review or refactor code in an existing repository without leaving your agent.
- Bridge an internal service or CLI into the agent toolset.
How to compare servers like this
- Scope of control:
- Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
- Environment fit:
- Match the runtime it expects (Node, Python, a container) to what you actually run.
- Maintenance signal:
- Check the last-commit date — dev tooling that lags upstream breaks first.
- Config surface:
- Prefer tools whose environment-variable or config keys are documented plainly.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the io.github.dashi96/chromium-bridge MCP server?
MCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code: browser automation
How to install io.github.dashi96/chromium-bridge
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"chromium-bridge": {
"command": "npx",
"args": [
"-y",
"chromium-bridge"
]
}
}
}Related MCP servers
MCP server for dbatools — exposes SQL Server management commands as MCP tools

D'AUBE // BRIDGE²
Universal AI skill compiler and MCP bridge. Write once, run across agents.

UML Forge
Architecture intelligence, security analysis, and living docs. 14 Mermaid tools.

Shared records for AI agents: engineering decisions, bug history, rules, and work state through MCP.

Persistent memory for Claude Code, Cursor and Codex. Facts retire when they change.
View repository →
DataCharter
Local-first SQL workspace with contract-governed, PII-masked query access for AI agents.
