Chronos Browser
Related Servers
Alternatives to Chronos Browser
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables AI agents and MCP clients to drive real Chrome, Edge, Brave, and Firefox browsers through native automation protocols. It exposes tools for navigation, page snapshots, form filling, clicks, screenshots, console/network inspection, and tab management.23MIT
- AlicenseNot gradedqualityCmaintenanceProvides a headless Chromium browser through MCP, enabling AI agents to browse JavaScript-rendered pages, search the web, capture screenshots, extract tables and data, and run stateful multi-step interactions like clicking, typing, and form submission.2,634,490 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI agents to navigate, interact with, and automate the web through an anti-detection browser toolset, supporting multi-tab workflows, session persistence, downloads, extraction, and token-efficient accessibility snapshots.549 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control a real browser via MCP tools for web navigation, interaction, page inspection, tabs, forms, files, sessions, and browser automation.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI agents to navigate, interact with, and automate websites through an anti-detection browser backend, offering 47 tools for tabs, navigation, interaction, observation, search, downloads, sessions, profile reuse, and batch workflows.549 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to control your installed Google Chrome through MCP or HTTP using compact text snapshots, exact pixel coordinates, and a visible cursor. It provides browser tools for navigation, clicking, typing, scrolling, tabs, forms, waiting, recording, and human handoff.35160 npm3MIT
TDQS
Scored across 20 tools
Most tools map to a distinct browser action (navigate, click, type, scroll, screenshot, etc.), and the descriptions differentiate the tricky pair browser_evaluate (JS in page context) vs browser_run_code (Python in the daemon). Minor overlaps remain: browser_status also reports active tabs, browser_tabs lists them, and browser_focus vs browser_launch(focus=True) can be confused with browser_batch abstracting over multiple actions.
Every tool uses the same browser_ prefix followed by a concise snake_case verb or verb_noun (browser_navigate, browser_new_tab, browser_close_tab). There are no camelCase or style deviations, making the set highly predictable.
20 tools is on the heavy side, but for a full browser automation daemon each tool covers a real capability (lifecycle, navigation, input, extraction, tab management, waiting, plus batch/JS/Python escape hatches). It is slightly over the comfortable 3-15 band but not gratuitously bloated.
Core lifecycle, navigation, interaction, extraction, screenshotting, tab management, and waiting are all covered, with evaluate/run_code/batch acting as powerful escape hatches. Gaps exist for history actions (back/forward/reload), hover/select/file-upload, and cookie/storage management, but most are workaroundable via browser_evaluate.