Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
callstackincubator avatar

Agent Device

  • 3.7k repo stars
  • Updated July 27, 2026
  • callstackincubator/agent-device

Agent Device is a MCP server that enables AI agents to inspect, control, and debug iOS, Android, desktop, and TV apps.

About

Agent Device MCP lets AI coding agents interact with real mobile, desktop, and TV applications for inspection, control, and debugging. developers shipping React Native or multi-platform clients can delegate repetitive device checks—navigation flows, layout issues, crash reproduction—to the agent instead of manually driving simulators between IDE sessions. Register the npm agent-device package over stdio in your MCP client, connect to your dev environment per Callstack’s setup, and use agent prompts to exercise UI like a tester. It shines in ship and test subphase when binaries exist and you need confidence before release; it is less about greenfield UI coding and more about validating behavior on actual targets. Pair with your CI story separately; this is interactive, agent-driven device QA in the loop.

  • MCP server agent-device (v0.16.9) for real device and emulator control
  • Supports iOS, Android, desktop, and TV app surfaces from Callstack incubator repo
  • stdio npm transport for Claude Code, Cursor, and compatible MCP clients
  • Oriented to inspect, control, and debug—not just screenshots
  • Fits React Native and cross-platform stacks common to Callstack tooling

Agent Device by the numbers

  • Data as of Jul 28, 2026 (Skillselion catalog sync)
terminal
claude mcp add agent-device -- npx -y agent-device

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
repo stars3.7k
Packageagent-device
TransportSTDIO
AuthNone
Last updatedJuly 27, 2026
Repositorycallstackincubator/agent-device

What it does

Let your coding agent inspect, tap, and debug real iOS, Android, desktop, and TV app builds before you ship updates.

Who is it for?

Best when you use MCP agents and need hands-on device debugging beyond static code review.

Skip if: Web-only SaaS developers with no native apps, or teams unwilling to configure device/emulator tooling locally.

What you get

Your agent can drive and debug installed apps across platforms from MCP, tightening pre-ship test loops.

  • Agent-driven inspect and control sessions on supported platforms
  • Faster reproduction of UI and navigation bugs on real targets
  • MCP bridge between coding agent and native app debug workflows

By the numbers

  • npm package agent-device version 0.16.9
  • Platforms listed: iOS, Android, desktop, and TV
  • Repository callstackincubator/agent-device on GitHub
README.md
agent-device: device automation CLI for AI agents

agent-device

npm version CI License: MIT Glama MCP server

Mobile app verification for AI agents.

A device automation CLI for real apps on iOS, Android, TV, web, and desktop. Agents get token-efficient snapshots, semantic refs, and evidence captured only when needed.

agent-device lets coding agents open apps, inspect the current UI, interact with visible elements, and collect debugging evidence through one CLI. Use it when an agent needs to verify what actually happens on a device, not just reason about code.

If you know Vercel's agent-browser, agent-device is the same idea for mobile, TV, and desktop apps. Minimal --platform web support reuses agent-browser when a browser session needs to fit into the same command/session/replay loop.

It works with native iOS and Android apps, plus apps built with Expo, Flutter, and React Native, as long as the target can run on a supported device, simulator, emulator, or desktop environment.

agent-device demo showing Codex using agent-device to create a new contact in the iOS Contacts app from a simple prompt

Capabilities

  • Inspect real app UI through structured accessibility snapshots, interactive refs like @e3, selectors, and React Native component trees.
  • Interact by opening apps, tapping, typing, scrolling, performing gestures, waiting, asserting state, handling alerts, and closing sessions.
  • Capture evidence with screenshots, videos, logs, traces, network traffic, performance samples, crash context, and React profiles.
  • Replay workflows by recording .ad scripts for local runs, CI, repeatable e2e checks, and strict Maestro YAML export when a flow needs to run in Maestro.
  • Run across platforms with iOS Simulator automation, Android Emulator automation, physical devices, tvOS, Android TV, macOS, Linux, and desktop app automation, so agents can see and feel the app they work on.

Use Cases

  • Verify mobile changes on real devices, simulators, and emulators before review or merge.
  • Give AI coding agents a real app feedback loop while they implement features.
  • Debug regressions with screenshots, logs, traces, network evidence, and crash context.
  • Profile performance issues with CPU/memory samples and React render profiles when needed.
  • Turn exploratory app interactions into replayable e2e checks for CI.
  • Use one agent workflow across native iOS, Android, Expo, Flutter, React Native, TV, and desktop apps.

Sketch showing agent-device as the live app verification layer in the agentic development loop

Quick Start

Install the CLI:

npm install -g agent-device@latest
agent-device --version
agent-device help workflow

The installed CLI help is the source of truth for agents. Start with agent-device help workflow, then follow the topic-specific help when a task needs dogfooding, debugging, replay, or React Native profiling.

Prerequisites depend on the target platform: Node.js 22+, Xcode for iOS/tvOS/macOS targets, Android SDK + ADB for Android, and macOS Accessibility permission for desktop automation. Web automation requires Node 24+. See Installation for platform setup.

Try the basic loop:

# Find an app.
agent-device apps --platform ios
agent-device apps --platform android

# Start a session.
agent-device open SampleApp --platform ios

# Inspect the current screen. -i returns interactive elements only.
agent-device snapshot -i
# @e1 [heading] "Settings"
# @e2 [button] "Sign In"
# @e3 [text-field] "Email"

# Act, capture evidence, and close.
agent-device fill @e3 "test@example.com"
agent-device screenshot ./artifacts/settings.png
agent-device close

Snapshots assign refs like @e1, @e2, and @e3 to elements on the current screen. Refs from the latest snapshot are immediately actionable; after scrolling or changing screens, take a fresh snapshot.

Next Steps

  • Set up your agent: run the CLI from Cursor, Codex, Claude Code, Windsurf, or another agent terminal. For skills, rules, direct MCP tools, and client-specific setup, see AI Agent Setup.
  • Try the sample app: clone the repo and run the bundled Expo fixture when you want a guided first dogfood run with screenshots, replay, and performance evidence. See Quick Start.
  • Go deeper: use Commands, Replay & E2E, and Debugging & Profiling for production workflows.

Articles & Videos

Articles

Videos

Where To Run agent-device

Path Best for Start with
Local Exploration, debugging, and development loops on simulators, emulators, physical devices, macOS apps, and Linux desktop targets. Follow the Quick Start.
CI/CD Automated PR and merge validation with replay scripts and captured artifacts. Try the EAS workflow template. GitHub Actions template coming soon.
Cloud / remote execution Linux runners, managed devices, and remote execution. Use Agent Device Cloud, see Commands for remote profiles, or contact Callstack for team-scale QA.

How It Works

agent-device runs session-aware commands through platform backends: XCTest for iOS and tvOS, ADB plus the Android snapshot helper for Android, a local helper for macOS desktop automation, and AT-SPI for Linux desktop targets.

Node consumers can use the typed client and public subpaths for bridge integrations. agent-device/android-adb exposes the Android ADB provider contract, logcat/clipboard/keyboard/app helpers, and port reverse management.

FAQ

What is agent-device?

agent-device is a device automation CLI for AI mobile app testing. It lets AI agents verify real apps on iOS, Android, TV, desktop, simulators, emulators, and physical devices.

Does it work with React Native, Expo, Flutter, and native apps?

Yes. agent-device works with native iOS and Android apps, Expo apps, Flutter apps, React Native apps, TV apps, and desktop apps that run on supported targets.

How is it different from Appium, Detox, or Maestro?

Appium, Detox, and Maestro are traditional mobile automation frameworks. agent-device is optimized for AI agents that need to inspect app state, interact semantically, capture evidence, debug, profile, and turn useful explorations into replayable checks.

Used By

Used by teams and developers at Callstack, JPMorgan Chase, Expensify, Shopify, Kindred, Total Wine & More, LegendList, HerLyfe, App & Flow, and more.

Documentation

Contributing

See CONTRIBUTING.md.

Made at Callstack

agent-device is open source and MIT licensed. Visit agent-device.dev, try the EAS workflow template, read the docs, or contact us at hello@callstack.com.

Recommended MCP Servers

How it compares

Real-device control MCP server, not a Playwright-only browser skill.

FAQ

Who is Agent Device MCP for?

Developers shipping native or cross-platform apps who want Claude Code or Cursor to interact with real devices and emulators via MCP.

When should I use Agent Device MCP?

Use it in ship/testing when you have runnable builds and need agent-assisted reproduction, UI checks, or debug sessions on iOS, Android, desktop, or TV.

How do I add Agent Device MCP to my agent?

Install the Agent Device npm package, configure your local device/simulator toolchain per the GitHub repo, register stdio MCP in your client, then issue control and inspect commands from the agent.

Developer Toolstestingfrontend

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.