Skip to main content
Glama
yzanbo

arc-browser-control

by yzanbo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to arc-browser-control

No user-submitted related servers found.

    Related Servers

    • arc-mcp

      happylinks
      F
      license
      A
      quality
      D
      maintenance
      An MCP server for the Arc browser that enables programmatic management of spaces and tabs. It supports actions like listing, creating, and deleting spaces and tabs, as well as focusing spaces and opening URLs via AppleScript.
      9
      9 npm
      6
      -

    • arc-lite-mcp

      yzanbo
      F
      license
      A
      quality
      D
      maintenance
      A lightweight MCP server to control Arc Browser on macOS, optimized for frontend development with 30 tools including DOM operations, debugging, and network monitoring.
      30
      -
    • agentify-desktop by agentify-sh

      agentify-desktopofficial

      agentify-sh
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI tools to control local browser sessions for ChatGPT, Claude, and other AI services, supporting querying, navigation, file uploads, and artifact management.
      28 npm
      558
      Mozilla Public 2.0

    • macos-mcp

      CursorTouch
      A
      license
      Not graded
      quality
      A
      maintenance
      A lightweight MCP server that bridges AI agents and macOS, enabling automation of file navigation, application control, UI interaction, browser automation, and system operations.
      176
      MIT

    • browser-use-relay-mcp

      mlnima
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables remote observation and control of a Chromium browser via a WebSocket relay, supporting DOM, CDP, and native OS automation for local or LAN-based AI agents.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 76 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource, with detailed descriptions that clearly differentiate them. Even similar tools like arc_get_page_content and arc_get_page_html are distinguished by their specific output (text vs. HTML).

    Naming Consistency5/5

    All tools follow the consistent pattern 'arc_verb_noun' using imperative verbs and descriptive nouns. The naming is uniform across the entire set, making it easy to predict tool actions.

    Tool Count3/5

    With 76 tools, the set is large but covers the extensive scope of browser automation. While some consolidation could be possible, the number is justified for a comprehensive browser control server, though it borders on excessive.

    Completeness4/5

    The tool surface covers most core browser automation tasks: navigation, interaction, storage, network, performance, and tab/window management. Minor gaps exist, such as missing scroll or element attribute tools, but agents can work around them.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources