A
licenseA
qualityB
maintenanceEnables 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
20 npm
5
MIT
Flick
by bgivenb
Related Servers
Alternatives to Flick
No user-submitted related servers found.
Related Servers
- FlicenseCqualityAmaintenanceEnables MCP-compatible AI agents to make decisions using JEV, execute local skills, and list available skills through MCP tools.51-
- AlicenseNot gradedqualityAmaintenanceLets 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.462 npm5MIT
- AlicenseAqualityBmaintenanceEnables agents to delegate browser exploration to Jev by providing natural-language objectives, receiving compact evidence and source context, and continuing the same live browser session through supervisor handoffs.6Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to control a persistent Chrome browser through a local daemon, with Jev performing routine actions and the host agent handling reasoning, text, and verification.25 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables agent harnesses to make fast, confidence-aware tool selections using Jev, with planner fallback, hierarchical routing, and optional MCTS lookahead, exposed natively over MCP stdio.22MIT
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
ActivityMaintained
ResponsivenessNo issues