arc-browser-mcp
Related Servers
Alternatives to arc-browser-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables Claude Code to control the Arc browser over CDP, including navigation, clicking, form filling, screenshots, and reading console and network traffic.11MIT
- AlicenseAqualityDmaintenanceA bridge to launch Chrome on Windows from WSL2 and proxy Chrome DevTools MCP tools. It enables browser automation via Claude Code in WSL2 by managing Chrome's lifecycle and exposing debugging capabilities.24 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables natural-language CAD geometry creation in Autodesk Fusion 360 by connecting an LLM running in WSL via OpenCode to Fusion on the Windows host.-
- FlicenseNot gradedqualityDmaintenanceExposes VS Code's integrated browser to external agents (Claude Code, scripts, curl) via a local HTTP API and MCP server.1-
- FlicenseNot gradedqualityCmaintenanceLets Claude Desktop on Windows execute shell commands, read and write files, and run git/npm/node/python directly inside WSL (Ubuntu), while isolating the Windows host filesystem by default.-
- FlicenseNot gradedqualityCmaintenanceEnables AI coding agents like Claude to read Windows clipboard contents (text and images) from within WSL environments, providing seamless cross-platform clipboard access through the Model Context Protocol.5-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one checks browser availability, and the other performs navigation. There is no overlap or ambiguity between them.
Both tools use the arc_ prefix and snake_case style. arc_navigate is an action verb while arc_browser_status is noun-style, so the pattern is mostly consistent but not perfectly uniform.
Two tools is minimal and only covers availability checking plus navigation. For a browser-related MCP this feels slightly thin, though the narrow scope keeps it from being unreasonable.
The core status-then-navigate workflow is present, but the server lacks any way to read tabs, URLs, or page content. This leaves notable gaps for agent workflows that need to inspect browser state.