English Français العربية

VibeView

Official registry Productivity

Drive cloud iOS, Android, Apple TV, Android TV and Roku devices to verify app changes.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package vibeview
Claude Code 
claude mcp add vibeview -e 'VIBEVIEW_API_TOKEN=<your vibeview_api_token>' -- npx -y vibeview@0.62.0 mcp
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "vibeview": {
            "command": "npx",
            "args": [
                "-y",
                "vibeview@0.62.0",
                "mcp"
            ],
            "env": {
                "VIBEVIEW_API_TOKEN": "<your vibeview_api_token>"
            }
        }
    }
}

Environment variables

  • VIBEVIEW_API_TOKEN secret A VibeView API token (Settings → API tokens). Alternatively run `vibeview login` once; the server reuses the saved login.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. VibeView agent skills
  2. Install
  3. What's here
  4. Where this comes from

VibeView 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

PathWhat it is
skills/vibeview-agent/SKILL.mdThe 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.jsonThe 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: support@vibeview.io.

Frequently asked questions

What is VibeView?

Drive cloud iOS, Android, Apple TV, Android TV and Roku devices to verify app changes.

How do I install VibeView?

It runs on your machine. In Claude Code: claude mcp add vibeview -e 'VIBEVIEW_API_TOKEN=<your vibeview_api_token>' -- npx -y vibeview@0.62.0 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.

Does VibeView need an API key?

Yes. It expects VIBEVIEW_API_TOKEN, which you set in its configuration.

Is VibeView open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains VibeView?

It is published by vibeview. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.