Openchrome MCP vs Hronaut Browser MCP
A side-by-side look at the Openchrome MCP and Hronaut Browser MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
O
Openchrome MCPBrowser Automation · Local subprocess (stdio)Open-source browser automation MCP server. Control your real Chrome from any AI agent.51GoodAuth: not declaredVerdict: choose Openchrome MCP for browser automation work as a local process; choose Hronaut Browser MCP for browser automation over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
OChoose Openchrome MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
Choose Hronaut Browser MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | O Openchrome MCP | |
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 51/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 236 | 6 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Openchrome MCP | View Hronaut Browser MCP |
Tools & capabilities
Openchrome MCP tools
No tool names declared yet. Check the project README from the listing page.
Hronaut Browser MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Openchrome MCP
{
"mcpServers": {
"openchrome-mcp": {
"command": "npx",
"args": [
"-y",
"-p",
"openchrome-mcp",
"openchrome"
]
}
}
}
Hronaut Browser MCP
{
"mcpServers": {
"hronaut-browser-mcp": {
"url": "http://YOUR-HRONAUT-COMPUTER-LAN-IP:47812/mcp"
}
}
}
Frequently asked questions
Openchrome MCP is categorized under Browser Automation and uses a local stdio subprocess. Hronaut Browser MCP belongs to Browser Automation and uses a remote HTTP/SSE transport. Pick Openchrome MCP for browser automation work and Hronaut Browser MCP for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Openchrome MCP has no declared pricing — check the project's own site. Hronaut Browser MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add openchrome-mcp and hronaut-browser-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Openchrome MCP has a quality signal of 51/100 (Good) with 0 views, 0 installs and 236 GitHub stars. Hronaut Browser MCP has 41/100 (Fair) with 0 views, 0 installs and 6 GitHub stars.
