Skip to main content
MCP setup, including optional custom MCP with a literal command, lives in MCP setup. This page is a short client-index only.

Quick Install

Cursor — add to .cursor/mcp.json in your project root (or ~/.cursor/mcp.json for global):
Restart Cursor after saving. If you previously ran revyl auth login, no API key is needed. Claude Code: claude mcp add revyl -- revyl mcp serve Codex: codex mcp add revyl -- revyl mcp serve
The one-click buttons install the server without an API key. Run revyl auth login first, or add REVYL_API_KEY to your MCP config afterward.
Using Cursor Automations to prove CI-uploaded builds on a device? See Cursor proof (BYO-CI).

Prerequisites

1. Install the CLI

2. Authenticate

Approval happens through Revyl rather than a local port, so this works over SSH, in a container, and in a cloud agent. Or set an API key for an unattended machine:
See Authentication for the full reference.

3. Verify


Setup by Tool

Cursor

Create .cursor/mcp.json in your project root (project-scoped) or ~/.cursor/mcp.json (global):
Restart Cursor after editing. If you previously ran revyl auth login, you can omit the env block.

Claude Code

Codex (OpenAI)

CLI:
Config file (~/.codex/config.toml):
Keep MCP and your shell CLI pointed at the same binary. A mismatch can make session lists appear inconsistent.

Claude Desktop

Edit the config file:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

VS Code (Copilot Chat)

Add to your VS Code settings.json:

Windsurf

Create or edit ~/.codeium/windsurf/mcp_config.json:

Multi-Session Example

Run the same login flow on iOS and Android simultaneously:

Prompt Library

Use these copy/paste prompts to activate the right skill family.

CLI dev-loop prompt (revyl-cli-dev-loop)

MCP dev-loop prompt (revyl-mcp-dev-loop)

MCP create prompt (revyl-mcp-create)

CLI analyze prompt (revyl-cli-analyze)


Verify It Works

After configuring your tool, try these prompts:
  • “Start an Android device and take a screenshot”
  • “List all my Revyl tests”
  • “Run the login-flow test”
  • “Install this app and tap the Sign In button”
If something goes wrong, ask the agent to “Run device_doctor” — it checks auth, session, device, and grounding health.

Troubleshooting

The CLI is not in your PATH.
  1. Restart your IDE/tool
  2. Check the server starts manually: revyl mcp serve
  3. Enable debug logging by adding "--debug" to the args array in your MCP config
  4. Run revyl device doctor to check connectivity
Sessions auto-terminate after 5 minutes of idle time. Call start_device_session to provision a new device.
If direct device service DNS lookups fail (e.g. in Codex/Claude sandbox environments), the CLI/MCP automatically falls back to backend proxy routing.If actions still fail after fallback:
  1. Run device_doctor to verify session and device status
  2. Confirm the session still appears in list_device_sessions
  3. Start a fresh session if the current one was terminated externally
  1. Take a screenshot() to see what’s actually on screen
  2. Use more specific descriptions: "blue 'Sign In' button" instead of "button"
  3. Rephrase the target using exact visible text and retry