vibeview
OfficialRelated Servers
Alternatives to vibeview
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to list and boot iOS Simulators and Android Emulators, capture screenshots, drive device interactions through accessibility snapshots, and end sessions.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to control Android emulators and iOS Simulators with fast screenshots, UI tree reads, taps, typing, logs, crash reports, test capabilities, and resets for efficient build-run-check loops.11MIT
- AlicenseNot gradedqualityBmaintenanceEnables an MCP-connected agent to start and control real Android emulator and iOS Simulator sessions on GitHub Actions or locally, observe screens and UI trees, perform touch and text actions, and capture screenshots, recordings, logs, crashes, and evidence.Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to drive, test, and measure iOS and Android apps on simulators, emulators, and real phones by reading screens as elements, performing taps and gestures, sending pushes and deep links, and collecting performance and evidence.282MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to run, drive, and debug apps across Android emulators, Apple simulators, devices, and browsers from one tool, with token-lean UI snapshots, scripted flows, checks, and local service orchestration.12,577 npmMIT

optics-frameworkofficial
AlicenseNot gradedqualityBmaintenanceDrives Android, iOS, smart TV (Android TV, Tizen, webOS), web and Bluetooth (BLE) devices from an agent: start a session, tap, type, swipe and assert by XPath, visible text, OCR or image, then save the steps as a replayable CSV test suite.530 PyPI100Apache 2.0
TDQS
Scored across 38 tools
Most tools target a clearly distinct action+object: tap vs long_press vs drag vs type vs clear_text are unambiguous, and the descriptions actively separate the easily-confused trio swipe/scroll/scroll_to and find vs ui_tree. The remaining soft spots are dev_stop vs stop_session (overlap is explained in the text but still requires reading) and scroll vs swipe, which an agent could mix up without the descriptions. tap_focused vs focus vs tap on TV is handled well by explicit 'activates'/'without activating' wording.
Everything is lowercase snake_case with a consistent terse style, and the namespaced families (dev_*, list_*, *_test, run_*/get_run, set_*) are predictable. Deviations are minor: some names are bare verbs (tap, press, wait, find, focus, rotate, shake, alert) while others are verb_noun (open_url, clear_text, scroll_to, relaunch_app), and a few are noun-first (ui_tree, logs, screenshot). Still readable and guessable.
38 tools is a heavy surface, but the breadth is real: device interaction, device/system controls, session lifecycle, app/build catalogs, and the test runner are genuinely separate workflows. Individual tools each map to a distinct capability rather than padding, yet the set would benefit from tighter grouping or fewer near-duplicate scroll variants. Borderline over-scoped for a single MCP server.
Device control and inspection are well covered (input, gestures, rotation, posture, locale, location, logs, screenshot, tree, session start/stop/reload, app and build listing). The obvious gap is on the test surface: create_test/run_test/run_group/get_run exist but there is no list_tests, list_groups, update/delete_test, or run history listing, so an agent cannot discover existing tests or clean up. No session listing either — stop_session wants an id the server never helps you find.