Quick Install
Cursor — add to.cursor/mcp.json in your project root (or ~/.cursor/mcp.json for global):
revyl auth login, no API key is needed.
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. Runrevyl auth loginfirst, or addREVYL_API_KEYto your MCP config afterward.
Prerequisites
1. Install the CLI
2. Authenticate
3. Verify
Setup by Tool
Cursor
Create.cursor/mcp.json in your project root (project-scoped) or ~/.cursor/mcp.json (global):
revyl auth login, you can omit the env block.
Claude Code
Codex (OpenAI)
CLI:~/.codex/config.toml):
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 Codesettings.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”
Troubleshooting
"revyl: command not found"
"revyl: command not found"
The CLI is not in your PATH.
Authentication errors
Authentication errors
MCP server not responding
MCP server not responding
- Restart your IDE/tool
- Check the server starts manually:
revyl mcp serve - Enable debug logging by adding
"--debug"to theargsarray in your MCP config - Run
revyl device doctorto check connectivity
"no active device session"
"no active device session"
Sessions auto-terminate after 5 minutes of idle time. Call
start_device_session to provision a new device.DNS failures in sandboxed agents
DNS failures in sandboxed agents
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:
- Run
device_doctorto verify session and device status - Confirm the session still appears in
list_device_sessions - Start a fresh session if the current one was terminated externally
Grounding model not finding elements
Grounding model not finding elements
- Take a
screenshot()to see what’s actually on screen - Use more specific descriptions:
"blue 'Sign In' button"instead of"button" - Rephrase the target using exact visible text and retry