dolphin-anty-mcp
Related Servers
Alternatives to dolphin-anty-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceAn MCP server that provides an antidetect browser with persistent profiles, proxy support, and page control tools (16 tools) for agents, enabling identity-stable browsing sessions across runs.12MIT- FlicenseNot gradedqualityNot gradedmaintenanceSelf-hosted MCP server for browser automation with stealth patches, offering 50 tools for navigation, scraping, and session configuration. Runs via Docker and supports remote control from any MCP client.-
- AlicenseNot gradedqualityBmaintenanceA high-performance MCP server for browser automation via Chrome DevTools Protocol, enabling fast, low-cost, and anti-bot web interactions.23 npmMIT
- -licenseNot gradedqualityNot gradedmaintenanceUndetectable browser automation server for MCP-compatible AI agents, offering 225 tools across 32 sections to navigate, extract, clone pages, and bypass antibot systems like Cloudflare.1-

ZennoBrowser MCP Serverofficial
AlicenseCqualityBmaintenanceMCP server for the ZennoBrowser antidetect browser: create and manage browser profiles, proxies, cookies, threads and browser instances from AI agents.26380 npm2MIT- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for interacting with Chrome through its DevTools Protocol, enabling remote control of Chrome tabs to execute JavaScript, capture screenshots, monitor network traffic, and more.96 npm52MIT
TDQS
Scored across 71 tools
Each tool targets a distinct resource/action, with detailed descriptions that clarify edge cases (e.g., list_profiles vs list_profiles_cursor, export_cookies vs export_cookies_local). The main risk is the sheer number of similarly named tools, but the descriptions resolve most ambiguity.
The dominant pattern is verb_noun (list_, create_, update_, delete_, get_, start_, stop_, browser_), which is predictable. Minor deviations exist: plural forms (delete_profiles, create_profiles_bulk), the suffix in list_profiles_cursor, and the catch-all dolphin_request, but these do not obscure the convention.
At 71 tools, this is far above the 25+ threshold for 'too many' and will be heavy for an agent to navigate. While the tools cover a wide range of the Dolphin{anty} product's features, the sheer volume makes the server feel like a kitchen sink rather than a focused toolset; splitting into modular servers would improve coherence.
The surface is remarkably complete: CRUD for profiles, proxies, folders, statuses, bookmarks, homepages, extensions, and team members, plus fingerprint generation, cookie sync, and browser automation. Minor gaps like a dedicated get_proxy are covered by list endpoints, so there are no functional dead ends.