vibeview
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIBEVIEW_API_TOKEN | No |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
VibeView runs your app on a cloud iOS simulator, Android emulator, Apple TV, Android TV or Roku device you control with these tools. Loop: dev_start (platform, app from list_apps; add standalone: true for a release or CI build that needs no Metro) -> ui_tree -> act with refs (tap @e5, type, swipe, press) and read the change each action reports -> dev_stop when done. Foldables: pick one by model in dev_start (list_device_models marks them foldable, with free/busy counts), then set_posture and rotate. set_location sets the simulated GPS position (phones and tablets) for location-based flows. screenshot writes a PNG and returns its path; pass inline: true to see the image. logs reads the app output after a crash or blank screen. Tests: create_test, then run_test (or run_group) and get_run. With session_id a run uses the session you hold; without it, a run starts its own new device (never your dev_start session). A session stopped elsewhere is reported as ended; call dev_start again for a new one. A session nobody uses ends after the idle timeout. A result that ends with "Session … ends in N s for inactivity" means act (tap, type, swipe, press) to keep it, or dev_stop if you are done; ui_tree, screenshot, logs, find and wait do not count as use. If VibeView itself gets in your way (an error you cannot explain, a missing capability, confusing output), offer the user to send it with send_feedback.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ui_treeB | Fetch the ref-annotated UI tree for the current screen. |
| logsA | Read recent app logs from the device — JS console output, native errors, and crash messages from the app under test (not full system logs). Check after a crash, a frozen screen, or an unexpected blank tree, and to confirm an expected log line fired. Pass the previous response's cursor as since to get only lines that arrived after it. |
| screenshotA | Capture a screenshot of the current screen. Use it to check how something LOOKS — the UI tree carries no colour, contrast, or stacking information, so a screen can pass every check the tree can express and still be visibly broken. Saved to disk; over MCP, pass inline: true to receive the image itself. On a phone or tablet its pixels are the coordinates |
| tapB | Tap an element by ref (e.g. @e5), or raw coordinates (e.g. 100,200). |
| long_pressB | Long-press (touch and hold) an element by its ref. |
| swipeB | Perform a scrollbar-semantic swipe gesture in one of four directions. |
| scroll_toB | Scroll until an element matching the given text becomes visible. |
| dragB | Drag between two points, each an element ref (@e5) or raw coordinates (100,200). |
| alertA | Inspect or respond to a visible system alert on iOS or Apple TV (get, accept, or dismiss). |
| scrollA | Scroll the current view up, down, left, or right using a gesture preset. |
| typeA | Type text into the currently focused input field. |
| clear_textB | Clear the text in the currently focused input field. |
| pressB | Press a device button or perform a system gesture (home, back, d-pad, etc). |
| open_urlA | Open a deep link in the app under test. The link goes to that app only, never a browser: on Android a link the app has no screen for fails; on iOS only the app's own URL scheme (e.g. myapp://settings) is accepted, and a web or system link is refused. |
| relaunch_appA | Close the app under test and start it again: a cold start that keeps the app's data, e.g. to check that something persists. Its log keeps streaming across the restart. Not available on embed sessions. |
| set_postureA | Fold or unfold a foldable device (form factor |
| rotateA | Rotate the device. A phone (and an Android foldable) toggles between portrait and landscape; the iPhone Duo turns a quarter clockwise, or by degrees 180/270. Reports the new orientation. Not available on TV devices. |
| shakeB | Shake the device once (phones, tablets and foldables) |
| set_locationA | Set the device's simulated GPS location, for location-based flows. Phones, tablets and foldables (iOS and Android); not available on TV devices. |
| set_languageA | Restart the app under test in another language — a language tag such as de, fr, ja or pt-BR, or 'default' for the device's language — e.g. to check translations or take localized screenshots. Only the app changes; the device, its status bar and other apps keep their language. iPhone, iPad, Apple TV and Android 13+; not Roku or embed sessions. |
| set_status_barA | Show a clean status bar for screenshots (9:41, full battery, full Wi-Fi and cellular signal) or put the device's own status bar back. It stays until you change it or the session ends. iOS phones and tablets only. |
| waitB | Wait for a specified number of seconds before continuing. |
| findC | Find an element by text with optional spatial constraints (below/above/near). |
| tap_focusedA | TV: move focus to an element and press SELECT in one step. |
| focusA | TV: move focus to an element without activating it. |
| dev_startA | Start a VibeView session held by this MCP server, and use it as the default session for every other tool call until dev_stop. By default it is a React Native dev loop: a debug build that loads its JS from your local Metro. Pass standalone: true to run any build as it is (a release, CI or cloud build) with no Metro. In a Flutter, Capacitor or native (not React Native) project the session is standalone automatically. Returns once the session accepts commands (device up, app installed), with the device it got (model, OS, form factor, posture) — call ui_tree next. |
| dev_stopA | Stop the dev-loop session started by dev_start. |
| dev_reloadA | Roku only: re-package the channel with the build command from vibeview.json (platforms.roku.build), upload it, and reload it into the session dev_start is holding (or, with no held session, this project's |
| upload_appA | Upload an app build (zipped simulator .app for iOS/tvOS, .apk for Android/Android TV, or a Roku channel .zip) and return its app_id for dev_start. The MCP equivalent of |
| list_device_modelsA | List the device models you can start right now (model, OS version, platform, category, form_factor "foldable" for any device with a hinge — the iPhone Duo, Android foldables such as the Pixel 9 Pro Fold — and how many of each are free and busy). Pass a model name to dev_start to run on it; a model with none free queues until one is. |
| list_appsA | List your organization's uploaded apps: app id, name, platform and bundle id / package name. Sample apps (is_sample) are VibeView's examples, never this project's app. Pass an app id to dev_start (app) or list_builds. |
| list_buildsA | List an app's uploaded builds, newest first: id, version, build number, platform, kind (debug/release/unknown), upload time, note and retention (keep, expires_on as YYYY-MM-DD, expired; absent on older servers). Pass a debug build's id to dev_start as build_id. |
| stop_sessionA | Stop any session by id — e.g. one created through the API, the sandbox, or a collaboration link. For the session dev_start started, dev_stop does the same without an id. |
| create_testA | Create a test for an app from plain-language steps, one per line; a check is a step starting with "Verify". Returns the test id for run_test. The first run is driven by AI; once it passes, later runs replay the saved path. |
| run_testA | Run a saved test. With session_id it runs on that session (the device you are driving). Without it, VibeView always starts a new device of the test app's platform, runs the test and stops the device (it does not use a session you hold from dev_start; pass session_id to run on a session you hold). Returns a run id for get_run. |
| run_groupA | Run every test of a group in order. With session_id it runs on that session; without it, on a new device of the app platform that VibeView starts and stops (it does not use a session you hold from dev_start; pass session_id to run on a session you hold). Returns a run id for get_run. |
| get_runA | A run's status and, when a test failed, which step and why. Pass the run id run_test or run_group returned. |
| send_feedbackA | Send the VibeView team a bug report, a friction note or a feature idea about VibeView itself. Only for problems with VibeView itself (the CLI, MCP tools, devices, sessions, runs, dashboard, docs) — never for bugs in the user's own app. Show the user what you will send and get their OK first. Never include passwords, tokens, API keys, test data values or personal data. One report per problem; do not resend it. kind: bug (something broke), friction (it worked but was confusing, slow or awkward), idea (a missing capability). user_quote: the user's own words, verbatim — never a paraphrase. The report includes the session's device and status when it names one. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.