misha-browser
Related Servers
Alternatives to misha-browser
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables remote AI agents to control a local, authenticated desktop browser over MCP through an outbound WebSocket bridge and Chrome extension, supporting tab management, navigation, page reading, clicking, typing, scrolling, screenshots, and JavaScript evaluation.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables compatible AI clients to drive independent browser sessions, run durable command jobs, and read/write files through a shared local worker, with an embedded live preview and owner-controlled approvals. Supports optional desktop, Android, and outbound relay routes for remote clients.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to observe and act on live browser pages through screenshots, bounded actions, responsive captures, console and network inspection, tab operations, and session management over local stdio or authenticated HTTP.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables Claude Agent SDK agents to safely operate a remote user machine via a WebSocket tunnel, providing six client__* MCP tools with path fencing and phase-switch adjudication.MIT
- AlicenseNot gradedqualityCmaintenanceEnables authorized remote MCP clients to securely reach local Mac or Windows tools over OAuth, including shell commands, file read/write, background jobs, screenshots, UI control, and clipboard access. It can also expose configured Desktop MCP servers and optional Claude Code task delegation.MIT
- AlicenseBqualityBmaintenanceGive local (stdio) and cloud/web (Streamable HTTP + OAuth 2.0 PKCE + WSS) AI agents safe control over the Chrome or Edge browser you are already signed into, with in-page interactive element filtering, multi-PC active-window routing, and read-only remote defaults.29328 npm9Apache 2.0
TDQS
Scored across 26 tools
Nearly every tool targets a distinct action, and the descriptions actively steer between the risky pairs (tab_click vs macos_mouse_click, tab_drag vs macos_mouse_drag, tab_type vs tab_fill vs macos_keyboard_type) by telling the agent to prefer the tab_* tools inside a page. The remaining overlap is structural rather than confusing: a broad browser layer and a generic macOS layer necessarily duplicate input primitives. A couple of fine-grained distinctions (tab_press vs tab_type without a ref, tab_find vs tab_wait) still need the description text to sort out.
Names are uniformly snake_case with two clean namespaces, tab_* and macos_*, which is easy to scan and predict. The ordering convention differs slightly between them (tab_ verbs lead, e.g. tab_read/tab_click, while macos_ tools put the object first, e.g. macos_mouse_move, macos_keyboard_press), but each namespace is internally consistent. tab_screenshot and tab_network are noun-style outliers inside an otherwise verb-led prefix.
Twenty-six tools is above the comfortable band, but the server spans two genuinely large surfaces (browser tab automation plus macOS desktop input), so most tools earn their place. Only a few look like thin helpers, notably macos_mouse_current_position, which exists mainly to verify a prior move. It is slightly over-scoped rather than bloated.
The browser surface covers the full perceive-act loop (list/read/find/wait/screenshot plus click, type, fill, select, press, scroll, drag) and the macOS surface covers app focus, mouse, keyboard and screen capture, so core workflows have no dead ends. Gaps are real but workable: no back/forward/reload navigation, no file upload, no clipboard access, and network responses cannot be read, only requests. Those are minor omissions an agent can route around rather than blocking failures.