Doksi Docs
Device API

Device API

Full remote control of cloud Android devices through MCP. No SDK, emulator, or ADB required.

An MCP server that gives AI agents full control over cloud-hosted Android devices. No local Android SDK, emulator, or ADB installation required — provision a device, interact with it, and tear it down entirely through tool calls.

How it works

  1. Provision. Call start_session to spin up a cloud Android device. Boot takes ~90 seconds.
  2. Control. Use 50+ tools to interact — screenshots, taps, app installs, log queries, GPS spoofing, network throttling, and more.
  3. Tear down. Call end_session to deprovision. Billing stops immediately.

Sessions persist across your conversation. Build multi-step test flows, debug production issues, or run exploratory QA — all without touching a physical device.

Tools

Session

Provision devices, list active sessions, configure network tunnels.

Observation

Screenshots, UI hierarchy, device state, performance and memory metrics.

Interaction

Tap, swipe, long press, type text, press hardware and system keys.

App Management

Install, launch, terminate, uninstall apps. Grant and revoke permissions.

Logs & Data

Application logs, HTTP traffic capture, internal app storage inspection.

Device Settings

Orientation, battery, GPS, dark mode, network speed, font scale, animations.

Simulate Events

Incoming SMS, phone calls, fingerprint sensor touches.

Files & Navigation

Clipboard, file transfer, deep links, system panels, volume.

Configuration

VariableRequiredDescription
DOKSI_API_KEYYesAPI key from app.doksi.ai/devices/api-keys

Requirements

Compatibility

Works with any MCP-compatible client: Claude Code, Cursor, VS Code Copilot, Codex, Windsurf, Cline, Continue, Zed, and others.

Integrations

Connect Doksi to Slack, GitHub, Jira, CI/CD pipelines, and more.

Quickstart

Install the Doksi Device MCP server and run your first session.

On this page

How it worksToolsConfigurationRequirementsCompatibility