octobrowser-mcp
Related Servers
Alternatives to octobrowser-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceControls Octo Browser antidetect profiles and automates browser tasks through natural language, enabling profile lifecycle management, web scraping, and full browser automation via CDP.37MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to control Multilogin X anti-detect browser profiles via a streamable HTTP MCP interface. Supports profile management, session handling, and a broad catalog of browser actions such as navigation, clicking, typing, screenshots, and more.-
- FlicenseNot gradedqualityDmaintenanceExposes Playwright browser automation as MCP tools, enabling AI assistants to control a real browser tab-by-tab for form filling, navigation, and more, while preserving the user's active session.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to control and interact with a Chrome browser via MCP, providing tools for navigation, screenshots, clicking, form filling, content extraction, and tab management.-
- AlicenseNot gradedqualityAmaintenanceBrowser automation for AI agents: tabs, cookies, arbitrary JS execution (via CDP, bypasses CSP), screenshots, downloads, proxy switching, data cleanup. Chrome & Edge multi-browser, full permissions, zero configuration. 25+ MCP tools.1MIT
- AlicenseNot gradedqualityAmaintenanceProvides MCP tools to control real, logged-in Chrome or Brave browser profiles—tabs, navigation, clicks, and typing—with secure profile isolation and no network listener.MIT
TDQS
Scored across 37 tools
Most tools are clearly separated by resource and action, and the octo_/browser_ prefixes help organize the set. The only real confusion risk is among find_profile_by_name, search_profiles, and start_profile_by_name, though their descriptions do distinguish them.
The set mostly follows a verb_noun pattern with octo_ for profile management and browser_ for page automation. Minor deviations like octo_health_check and the overloaded behavior of browser_type keep it from being perfectly consistent.
37 tools is well beyond the typical well-scoped range and exceeds the 25+ threshold, making the surface heavy to reason about. The count is somewhat justified by combining profile management with browser automation, but as a single server it feels overgrown.
Browser automation is well covered with navigation, interaction, extraction, waiting, tabs, and JavaScript evaluation. Profile management, however, lacks create/update/delete for persistent profiles, and extensions/proxies/tags only support read or delete operations, leaving notable gaps.