Orion Browser
Related Servers
Alternatives to Orion Browser
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA local Streamable HTTP MCP server that lets several AI agents drive your real, logged-in Chrome at once, each isolated in its own background tab group without stealing focus. It exposes browser tools for navigating, reading pages, filling forms, signing in via Bitwarden, and handing steps back to the user.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to run Playwright-compatible browser automation over stdio or Streamable HTTP, covering research, testing, persistent login profiles, Chrome extensions, proxy matching, and humanized interactions. It ships as npm and Docker packages for cross-platform deployments.280 npmMIT
- AlicenseNot gradedqualityBmaintenanceA stdio MCP server that lets a calling agent drive an existing Chrome session through a native browser extension bridge on Linux, WSL, and Windows. Goals and text are supplied by the agent while a decision model selects and performs the individual browser actions.1MIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server that lets AI agents and human operators drive isolated Chromium profiles with their own cookies, fingerprints, and proxies, exposing tools for navigation, clicking, typing, extraction, screenshots, JavaScript evaluation, tabs, cookies, and waits. Because session and login state persist per profile, agents can carry out real authenticated workflows across sessions.MIT

chromaphore-mcpofficial
AlicenseBqualityBmaintenanceMCP server (also a Claude Code plugin) that drives the Chromaphore browser, a Chromium build for AI agents: page listings with element ids, human-timed input, tabs, profiles and HAR recording. Runs locally over stdio with Node 20+; the browser is Windows-only for now.281Apache 2.0- AlicenseNot gradedqualityBmaintenancePolicy-gated MCP server for local-first browser automation, enabling agents to drive isolated Chromium sessions via snapshots, revision-bound refs, typed actuation, scripts, and telemetry receipts.Apache 2.0
TDQS
Scored across 3 tools
Lease (acquire/renew), release (return), and status (health/list) are logically distinct operations with clear descriptions. There is slight potential to confuse 'lease' and 'release' since they are opposites in the same lifecycle, but the descriptions make the direction clear.
All three names are single lowercase words, which is internally consistent. They do not follow a verb_noun pattern (release is a verb, status a noun), but there is no chaotic mixing of styles and each name is readable.
Three tools exactly cover the acquire/use/release lifecycle plus health inspection. Each tool earns its place, and the surface is not padded or artificially thin for a focused browser-lease service.
Lease, release, and status cover the core lifecycle; status also lists all browsers with state, holder, and expiry. Minor gaps like an explicit force-release or lease-configuration query are unlikely to block normal agent workflows.