Skip to main content
Glama
vKongv

Chrome Browser Control

by vKongv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Chrome Browser Control

No user-submitted related servers found.

    Related Servers

    • browser-use-mcp

      ShunL12324
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      1,791 npm
      MIT

    • Real Browser MCP

      ton-to-ton
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables browser automation over MCP using a real Chrome browser with existing profile, supporting real tabs, downloads, cookies, and RPA workflows.
      107 npm
      MIT

    • browserpilot-mcp

      Fire162
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables remote AI agents to control a local, authenticated desktop browser over MCP through an outbound WebSocket bridge and Chrome extension, supporting tab management, navigation, page reading, clicking, typing, scrolling, screenshots, and JavaScript evaluation.
      1
      MIT

    • OpenCode in Chrome

      Mukller
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local opencode agents to control a live Chrome browser via MCP tools, including tab management, JavaScript execution, clicking, form filling, page reading, screenshots, and console log retrieval.
      MIT

    • zcode-for-chrome

      fortil
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables ZCode to control a real Chrome browser, including tabs, navigation, page content, clicks, form filling, keyboard input, scrolling, screenshots, and JavaScript evaluation through a local MCP bridge.
      MIT

    • browser-bridge

      jeffkit
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables remote agents to control a local Chrome/Edge browser via MCP, supporting navigation, snapshots, clicks, typing, screenshots, and script execution.
      56 npm
      ISC
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    B3.2/5.0

    Scored across 30 tools

    Disambiguation2/5

    Several tools overlap significantly: snapshot, visible_snapshot, query_elements, extract_elements, and page_status all provide ways to inspect page content/state; click, click_at, and perform_actions (with click steps) overlap in interaction; browser_status and page_status both report status but with different focus. The descriptions are detailed but the high-level purposes blur together.

    Naming Consistency3/5

    Tool names are predominantly verb_noun (e.g., list_tabs, navigate, click_at), but there is inconsistency in verb style: some use explicit verbs like 'browser_status' (noun-only), 'cdp_attach' (abbreviation), 'snapshot' (noun-only), and 'keypress' (verb-noun but single word). Also 'extract_feed_posts' is more domain-specific than the rest.

    Tool Count2/5

    30 tools is on the high end for a browser control server. While the domain is complex, many tools feel like slight variations of each other (e.g., snapshot vs visible_snapshot), making the count feel bloated. The server could be consolidated to around 20 tools without losing functionality.

    Completeness4/5

    The tool set covers well the lifecycle of controlling a browser: claiming tabs, navigating, interacting, snapshotting, waiting, extracting, and CDP network inspection. Missing basic operations like page reload, back/forward, or download management are minor gaps that agents can work around.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources