Browsa
OfficialRelated Servers
Alternatives to Browsa
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables real browser automation as tools in Cursor, Claude Desktop, Windsurf, and any MCP-compatible client, allowing AI agents to interact with web pages through natural language.14 npmMIT
- AlicenseAqualityBmaintenanceEnables assistants such as Claude Code, Codex, and Gemini CLI to drive a real browser over MCP — navigating, clicking, typing, and reading live pages from plain-English instructions. Supports optional proxy routing, persistent profiles for surviving logins, and reproducible browser identities via seeds.181632,523MIT
- AlicenseNot gradedqualityCmaintenanceGives ChatGPT, Claude and other AI assistants a real Chrome browser running in the cloud, so they can navigate, read page content, click, type, run scripts and take screenshots, with saved sessions, live viewing or takeover via remote desktop, and CAPTCHA detection.MIT
- AlicenseNot gradedqualityBmaintenanceTurns YAML-defined browser flows into typed MCP tools that Claude, Cursor, VS Code and other MCP clients can call, letting agents run repeatable tasks like logins, form fills, report downloads, price checks and data extraction without letting them wander the page freely. Each call returns JSON output, downloaded files or screenshots, and failures report the step, error, page URL and a screenshot.19 npmMIT

HumanBrowserofficial
AlicenseNot gradedqualityCmaintenanceCloud Chromium for AI agents — stealth, residential proxies, captcha solving, A2A 1.0 endpoint. The MCP server lets Claude Desktop, Cursor, and Cline drive a real browser via three tools (humanbrowser_run, humanbrowser_stream, humanbrowser_viewer_url).21Apache 2.0- AlicenseNot gradedqualityAmaintenanceExposes a localhost MCP endpoint that lets agents launch and drive isolated, persistent browser profiles — navigating, clicking, typing, extracting, screenshotting, evaluating JS, managing tabs and cookies, and sending raw CDP commands. Each profile keeps its own cookies, login state, fingerprint, and proxy across sessions, enabling real authenticated workflows from Cursor, Claude Desktop, or any MCP client.MIT
TDQS
Scored across 20 tools
The surface is split into clearly distinct clusters (managed jobs, self-driven browsers, identities, webhooks, schedules, billing), and descriptions explicitly contrast run_task vs start_browser and get_job vs list_job_files. Minor overlap remains between list_identities and list_browsers, and between create_schedule and run_task, but the descriptions resolve the boundaries well.
Most names follow a clean snake_case verb_noun pattern (get_job, run_task, cancel_job, list_webhooks, create_webhook, delete_webhook, start_browser, stop_browser). A few outliers break the pattern: bare verbs observe and act, plus the noun phrases credits and proxy_network.
At 20 tools this sits at the upper edge, but each tool maps to a genuinely distinct capability across jobs, browsers, schedules, webhooks and account data. Nothing looks duplicated or padded, though a couple of read-only helpers (list_models, credits, proxy_network) could plausibly be consolidated.
Core job lifecycle is well covered (run, poll, cancel, respond, list files) and browsers have start/stop/list. However there are real gaps: no tool to fetch the contents of files returned by list_job_files, no delete/get/update for schedules (only create and list), and webhooks lack a get/update operation.