omni-browser
Related Servers
Alternatives to omni-browser
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables MCP clients to drive a real Chromium browser for automation, including navigation, JavaScript execution, CDP commands, network capture, and multi-tab control.730 PyPIGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and clients to control a real Chromium browser through MCP tool calls, including navigation, clicking, typing, JavaScript evaluation, screenshots, and DOM snapshots. Supports multiple isolated sessions over authenticated HTTP with no disk writes.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to operate an isolated local Chromium browser through MCP, with semantic snapshots, ref-based actions, search, research, crawling, and CDP access.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables MCP clients to control a real local browser window for web automation tasks such as clicking, typing, scrolling, and taking screenshots.11 npm-
- AlicenseBqualityCmaintenanceEnables an LLM to control a hosted headless Chromium browser over HTTP, navigating pages, clicking, typing, and reading structured accessibility snapshots so any MCP client can perform browser automation without local installation.2310,630,264 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables local opencode agents to control a live Chrome browser via MCP tools, including tab management, JavaScript execution, clicking, form filling, page reading, screenshots, and console log retrieval.2MIT
TDQS
Scored across 13 tools
Each tool maps to a distinct browser action, and descriptions distinguish the trickier pairs reasonably well (snapshot = accessibility structure vs read = visible text). Residual overlap exists between browser_snapshot/browser_read and browser_tabs/browser_switch_tab, but the wording gives an agent enough to choose correctly.
All names use snake_case with a clear domain prefix (browser_ / github_) and verb-first construction. Minor deviation: browser_back and browser_snapshot lack a noun object, but the overall pattern is predictable.
13 tools is well within the ideal band and every tool corresponds to a concrete, non-redundant browser or GitHub-form operation. No filler tools are present.
Core browsing (open, read, interact, screenshot, back) is covered, but lifecycle gaps are notable: no forward navigation, no new-tab creation, no tab close, and no reload/wait. The GitHub portion only covers a two-step repo creation flow, which is a very narrow slice of that domain.