Skip to main content
Glama
DB-25

arc-control-mcp

by DB-25
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to arc-control-mcp

No user-submitted related servers found.

    Related Servers

    • Arc Browser MCP

      jasoncronje
      A
      license
      A
      quality
      C
      maintenance
      Enables inspection and control of Arc Browser spaces and tabs on macOS, including reading sidebar/history data and performing actions like focusing spaces, creating and closing tabs.
      13
      1
      MIT

    • arc-mcp

      andrewgazelka
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables semantic browser automation for the Arc browser, allowing users to perform web tasks like searching, shopping, and data extraction through natural language commands.
      1
      -

    • chromium-sidecar

      nextster
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local AI agents to operate the user's existing browser session via a Manifest V3 extension and native messaging, supporting tabs, DOM snapshots, clicks, form input, JavaScript, screenshots, cookies, network capture, and Arc Spaces.
      32 npm
      MIT

    • arc-cdp-mcp

      chmodami
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code to control the Arc browser over CDP, including navigation, clicking, form filling, screenshots, and reading console and network traffic.
      11
      MIT

    • mcp-macos-cua

      bradthebeeble
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to control macOS desktop apps via screenshots, mouse clicks, keyboard input, accessibility queries, and AppleScript.
      11
      8 npm
      MIT
    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

    A3.9/5.0

    Scored across 26 tools

    Disambiguation5/5

    Each tool targets a distinct action or data type: tab lifecycle, page reading, element interaction, waiting, and spaces are cleanly separated. Potentially similar readers (get_page_content, get_html, query_elements, get_links, get_page_info) are explicitly differentiated by what they return.

    Naming Consistency4/5

    The vast majority follow a consistent verb_noun snake_case pattern (list_tabs, close_tab, wait_for_load, focus_space). Minor exceptions like arc_status and batch are understandable but break the otherwise uniform verb-first convention.

    Tool Count2/5

    At 26 tools, the surface is heavier than needed and crosses the threshold where the count starts working against usability. Several helpers like wait_for_load, execute_javascript, and batch could be consolidated or made optional, though the tools themselves are individually purposeful.

    Completeness4/5

    The set covers tab lifecycle, navigation, page reading, element interaction, waiting, spaces, and scripted fallback via execute_javascript. Minor gaps exist—no screenshot, hover, or space creation—but agents can usually work around them with JavaScript or the provided primitives.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources