Skip to main content
Glama

Related Servers

Alternatives to Flick

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to drive a real browser toward stated outcomes, where the calling model supplies goals and candidate values while Jev (Typesafe System One) resolves each step's target, action, value, and done/blocked/irreversible status. Exposes tools for navigation, acting, yes/no checks, choosing among options, page reading, snapshots, screenshots, and calling page-registered WebMCP tools.
      889 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to automate browser tasks by describing desired outcomes and candidate values, while Jev selects elements/actions and returns statuses, with direct tools for navigation, checks, reading, acting, snapshots, screenshots, and WebMCP calls.
      889 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to delegate complex web browsing goals to a real Chrome instance driven by Jev, completing tasks end-to-end in ~300ms per decision and returning only the final result.
      11
      15 npm
      4
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Lets any MCP agent control your signed-in Chrome with full login state, offering normal browser tools and an optional Fast JEV mode for bounded-speed typed decisions on the same profile.
      24
      489 npm
      34
      MIT

    TDQS

    A3.5/5.0

    Scored across 15 tools

    Disambiguation2/5

    Multiple tools start automation tasks (computer_run, computer_execute, computer_workflow) with subtle differences that are difficult to distinguish, and computer_inspect/computer_status with includeObservation both return interface state. computer_screenshot and computer_copy_image also overlap in image capture, so boundaries between tools are not always clear.

    Naming Consistency3/5

    All tools share the consistent 'computer_' prefix, but suffixes mix nouns (health, sessions, apps, status, workflow, screenshot) and verbs (open, inspect, act, run, execute, continue, cancel, close). This is readable and predictable at the prefix level, but it lacks a uniform verb_noun convention.

    Tool Count4/5

    At 15 tools, the set sits at the upper edge of the typical well-scoped range, and the broad computer-automation domain justifies much of its size. However, the overlapping task-launching tools could be consolidated without losing coverage.

    Completeness4/5

    The core lifecycle is well covered: open, inspect, act, run, status, cancel, continue, and close, plus support utilities like screenshots, sessions, and app listing. Minor gaps exist, such as lack of fine-grained configuration or session management controls, but common workflows should not hit dead ends.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing