agent-browser
Related Servers
Alternatives to agent-browser
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to drive a live, persistent self-hosted Chromium session over MCP, running browser actions via Playwright/CDP, capturing page snapshots, screenshots and videos, and managing uploads and downloads in the same tabs and signed-in accounts a human user can take over at any time.18 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to drive a real, logged-in Chrome browser for web automation tasks like navigation, clicking, typing, and screenshotting.2 npmMIT
- AlicenseBqualityCmaintenanceEnables MCP clients to drive a real Chromium browser for automation, including navigation, JavaScript execution, CDP commands, network capture, and multi-tab control.7GPL 3.0
- AlicenseAqualityBmaintenanceEnables MCP clients to drive a real cloud Chrome browser to read blocked pages, fill forms, take screenshots, and hand off control to a person for logins or CAPTCHAs.16MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to control and interact with the user's real Chrome browser session, leveraging existing logins, cookies, and extensions for AI-driven automation.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-driven browser automation from any MCP client by pairing with a Chrome extension, translating tool calls into WebSocket commands to drive Chrome without an Electron host.3,989 npmMIT
TDQS
Scored across 9 tools
Each tool has a distinct purpose, but browser_open and browser_navigate could be confused since both initiate a session and navigate to a URL. The descriptions clarify the difference (open creates/reuses session, navigate goes to URL), but an agent might still misfire.
All tool names follow a consistent snake_case verb_noun pattern with the 'browser_' prefix. This is predictable and readable.
Nine tools is well-scoped for a browser automation server, covering essential actions like open, navigate, read, click, type, press, scroll, status, and close. No obvious bloat or missing core operations.
The surface covers the full browser lifecycle and common interactions (open, navigate, read, click, type, press, scroll, status, close). Minor gaps include no explicit wait or screenshot tool (though read can return an image), and no form submission or download handling, but these are workaroundable.