MCP.so
Sign In
A

Agent Device

@callstackincubator

About Agent Device

Discovery router for the agent-device CLI with status, install, help, prompts, and resources.

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "agent-device": {
      "command": "npx",
      "args": [
        "-y",
        "agent-device",
        "mcp"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Agent Device?

Agent Device is a device automation CLI for AI agents that lets coding agents run real apps, inspect UI state, interact with visible elements, and collect debugging evidence. It integrates with iOS, Android, tvOS, Android TV, macOS, and Linux platforms and is built around token-efficient accessibility snapshots instead of pixel-first screenshots.

How to use Agent Device?

Install globally with npm install -g agent-device@latest. Use commands like agent-device help workflow, agent-device open, agent-device snapshot, and agent-device close in a terminal. For MCP-aware clients, configure as a stdio MCP server with command agent-device and args ["mcp"] for discovery-only handoff; automation always runs through the CLI.

Key features of Agent Device

  • Token-efficient accessibility snapshots with refs like @e1, @e2
  • Supports iOS, Android, tvOS, Android TV, macOS, and Linux
  • Captures screenshots, video, logs, network, CPU/memory/perf, crash logs, and React profiles
  • Produces replayable .ad scripts for local or CI e2e runs
  • MCP router for discovery-oriented clients (automation via CLI only)

Use cases of Agent Device

  • AI-driven mobile testing and QA on real devices and simulators
  • Development: build from specs, inspect runtime behavior, iterate until UI matches
  • Automated PR validation with replay scripts and captured artifacts in CI/CD
  • Performance analysis with CPU/memory/perf samples and React profile surveys

FAQ from Agent Device

How does Agent Device differ from agent-browser?

Agent-browser is for web browsers; Agent Device is the same idea for apps and devices (mobile, TV, desktop).

What are the prerequisites for Agent Device?

Node.js 22+, Xcode for iOS/tvOS/macOS targets, Android SDK + ADB for Android, and macOS Accessibility permission for desktop automation.

Where do data and artifacts live?

Locally, in CI/CD (EAS workflow template, GitHub Actions template coming soon), or via Agent Device Cloud for remote execution.

Can MCP clients use Agent Device for device automation?

No. The MCP router is discovery-only and exposes only a status tool for CLI handoff guidance. All device automation happens through the terminal CLI.

What transport does the Agent Device MCP server use?

Stdio transport.

Frequently asked questions

How does Agent Device differ from agent-browser?

Agent-browser is for web browsers; Agent Device is the same idea for apps and devices (mobile, TV, desktop).

What are the prerequisites for Agent Device?

Node.js 22+, Xcode for iOS/tvOS/macOS targets, Android SDK + ADB for Android, and macOS Accessibility permission for desktop automation.

Where do data and artifacts live?

Locally, in CI/CD (EAS workflow template, GitHub Actions template coming soon), or via Agent Device Cloud for remote execution.

Can MCP clients use Agent Device for device automation?

No. The MCP router is discovery-only and exposes only a status tool for CLI handoff guidance. All device automation happens through the terminal CLI.

What transport does the Agent Device MCP server use?

Stdio transport.

Comments

More AI & Agents MCP servers