About VibeView
VibeView provides skills and an MCP server for coding agents to test app builds on live cloud devices. It supports mobile and TV device sessions, UI-tree interaction, logs, and screenshots, with a handoff when a human must act.
Key features
- 01Upload app builds
- 02Start cloud device sessions
- 03Control apps through UI-tree refs
- 04Read logs and capture screenshots
- 05Stop for human intervention
Use cases
- 01Verify a mobile app build
- 02Check app behavior on TV devices
- 03Inspect logs and screenshots during testing
MCP support
The `vibeview` CLI runs the MCP server over stdio, exposing device-session controls for compatible MCP clients. The project also includes setup options that register the server with Claude Code.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y vibeviewVIBEVIEW_API_TOKENSecretA VibeView API token (Settings → API tokens). Alternatively run `vibeview login` once; the server reuses the saved login.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEVibeView agent skills
Skills and an MCP server that let a coding agent verify its work on a live cloud device: upload a build, start an iOS, Android, Apple TV or Android TV session, drive the app by UI-tree refs, read logs, take screenshots, and stop when only a human can act.
VibeView streams iOS simulators, Android emulators, Apple TV and Android TV simulators, and Roku devices to a browser and to agents. No Mac, no local simulator, no device on the desk. Docs: AI agent control.
Install
You need the vibeview CLI, logged in:
npm install -g vibeview
vibeview login
Then pick whichever fits your agent.
Any agent that reads skills (Claude Code, Cursor, Codex, and others via the skills CLI):
npx skills add vibeview/skills
Claude Code, as a plugin (installs the skill and registers the MCP server in one step):
/plugin marketplace add vibeview/skills
/plugin install vibeview@vibeview
Claude Code, from the CLI you already installed (copies the skill into ~/.claude/skills/ and offers to register the MCP server):
vibeview agent-setup
Any MCP client: run vibeview mcp over stdio.
{
"mcpServers": {
"vibeview": { "command": "vibeview", "args": ["mcp"] }
}
}
With Claude Code specifically: claude mcp add vibeview -- vibeview mcp.
What's here
| Path | What it is |
|---|---|
skills/vibeview-agent/SKILL.md | The agent workflow: build requirements, the dev loop, verifying with ui-tree, screenshots and logs, TV d-pad navigation, the human hand-off rule, cleanup, and the full command reference for both the CLI and MCP. |
.claude-plugin/ | Claude Code plugin manifest: the skill plus the vibeview mcp server. |
.mcp.json | The same MCP server in the standard root-level form that plugin and MCP directories scan for. |
Where this comes from
The canonical copy of the skill ships inside the vibeview npm package (vibeview agent-setup copies it from there). This repository mirrors it so agents and registries can discover it on GitHub. Versions track the CLI.
Issues and questions: [email protected].
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.