Ritoko
Related Servers
Alternatives to Ritoko
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityFmaintenanceEnables creation of reusable browser automation skills through demonstration by recording user actions in a browser while narrating, then converting those workflows into executable skills that can be invoked through natural language.1-
- AlicenseNot gradedqualityAmaintenanceEnables governed browser automation for AI agents with human-in-the-loop approval, audit logging, and read-only replay, supporting both ASK and AUTO autonomy modes.MIT
- AlicenseBqualityDmaintenanceEnables AI-driven browser automation with advanced form testing, batch operations, and intelligent element extraction for MCP-compatible applications.1413 npmMIT
- AlicenseCqualityAmaintenanceConnects to the Firefox or Chromium browser you already use, on desktop or Android, so agents can navigate sites, read pages, click and fill forms, take screenshots, and extract structured data. It keeps session credentials inside the browser rather than copying them into agent configuration.49MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to author, validate, and execute browser/API test plans with parallel drivers, assertions, and captured evidence such as screenshots and network logs.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform deterministic Windows desktop and browser automation through MCP, using pre-validated UI Automation and DOM locators for fast, stable execution of ERP and business workflows.1MIT
TDQS
Scored across 20 tools
Tools are well-differentiated by clear verb_noun naming (browser_open vs browser_snapshot, run_start vs run_resume vs run_cancel, host_start vs host_next). Minor overlap exists between run_resolve and run_reconcile (both handle review items) and between run_cancel and run_resume (both alter run state), but descriptions explain the boundaries well. An agent can reliably pick the right tool.
Consistent snake_case with predictable domain prefixes: browser_*, run_*, workflow_*, host_*, plus single verbs document_image, recording, doctor, step_repair. The pattern is readable and groups tools by lifecycle area.
20 tools is on the heavier side but justified by a genuinely broad domain: browser automation, workflow authoring, direct runs, host runs, and diagnostics. Each tool maps to a distinct lifecycle stage; nothing feels redundant, though the surface is near the upper bound of comfortable scoping.
Full lifecycle coverage across every sub-domain: recording (browser_open, browser_act, recording), authoring (workflow_save/get/list), execution (run_start, run_resume, run_cancel, host_start, host_next), recovery (step_repair, run_reconcile, run_resolve, run_adopt), inspection (run_report, run_list, doctor, document_image). No obvious dead ends for the stated purpose.