Agent Device

listing.by

Drive iOS and Android apps on simulators, emulators and devices so coding agents can verify their changes.

state.local.long (state.local.title)listing.badge.runs_with

listing.install

listing.local.explain

npx -y agent-device@latest mcp

listing.local.needs listing.local.note

act.add_to a11y.new_tabact.add_to a11y.new_tab

listing.share.h

listing.share.p_local

mcp.tc/i/agent-device

listing.about

Agent Device lets coding agents inspect, control, debug and verify apps on iOS, Android and HarmonyOS simulators, emulators and physical devices. It also targets tvOS, Android TV, Vega OS, web, macOS and Linux. Agents read accessibility snapshots, act through refs and selectors, and save screenshots, video, logs and traces as evidence.

It runs locally as a stdio server started with agent-device mcp, using the same execution path as the CLI. No sign-in or API key is needed. It requires Node.js 22.12 or newer, and web automation needs Node.js 24 or newer. A CLI and a typed Node.js API are also available.

listing.can

  • Open apps and inspect screens through accessibility snapshots
  • Tap, fill, scroll and run gestures using refs and selectors
  • Capture screenshots, video, logs, traces and network data
  • Profile performance and inspect React Native component trees
  • Save workflows as replay scripts for CI
  • Target simulators, emulators, physical devices, TV, web and desktop

listing.tools

listing.notools.local

listing.prompts

  • Run the onboarding screen on the iOS simulator and attach screenshots.

  • Reproduce this crash on the Android emulator and capture the logs.

  • Check whether this change causes extra React Native re-renders.

  • Explore the checkout flow and save it as a replay script for CI.

listing.setup.h

listing.setup.local

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio agent-device -- npx -y agent-device@latest mcp
  1. Start Claude Code and type /mcp. agent-device should show as connected.

Add --scope user to make it available in every project.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "agent-device": {
      "command": "npx",
      "args": [
        "-y",
        "agent-device@latest",
        "mcp"
      ]
    }
  }
}
  1. Save the file and restart Claude Desktop.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Add to Cursor a11y.new_tab

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

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

Needs Node.js on your computer.

VS Code

Install in VS Code a11y.new_tab

Or from a terminal:

code --add-mcp '{"name":"agent-device","type":"stdio","command":"npx","args":["-y","agent-device@latest","mcp"]}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "agent-device": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "agent-device@latest",
        "mcp"
      ]
    }
  }
}

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "agent-device": {
      "command": "npx",
      "args": [
        "-y",
        "agent-device@latest",
        "mcp"
      ]
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add agent-device -- npx -y agent-device@latest mcp

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.agent-device]
command = "npx"
args = ["-y", "agent-device@latest", "mcp"]

Needs Node.js on your computer.

Gemini CLI

gemini mcp add agent-device npx -- -y agent-device@latest mcp

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

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

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer.

listing.faq

Can I paste mcp.tc/i/agent-device into my MCP client?

No. Agent Device runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y agent-device@latest mcp.

Does Agent Device need an API key?

No. It doesn't declare any keys or environment variables. It runs with your user account's permissions, so check what its tools can reach.

Is Agent Device a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y agent-device@latest mcp, which needs Node.js.

What can Agent Device do?

You can open apps and inspect screens through accessibility snapshots, tap, fill, scroll and run gestures using refs and selectors and capture screenshots, video, logs, traces and network data.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Who wrote this page?

mcp.tc's robot read Agent Device's public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead_local listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![Agent Device on mcp.tc](https://mcp.tc/i/agent-device/badge.svg)](https://mcp.tc/i/agent-device)
HTML
<a href="https://mcp.tc/i/agent-device"><img src="https://mcp.tc/i/agent-device/badge.svg" alt="Agent Device on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/agent-device.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/agent-device" title="Agent Device on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json_local

https://mcp.tc/i/agent-device.json

listing.em.fields

listing.related

listing.more_in

  • WinDbg

    svnscha

    state.local.label (state.local.title)

    Analyze Windows crash dumps and debug live user-mode or kernel targets through WinDbg (CDB and KD) in natural language.

    mcp.tc/i/windbg

  • ROS MCP Server

    robotmcp

    state.local.label (state.local.title)

    Connect LLMs to ROS and ROS 2 robots to work with topics, services, actions and parameters through rosbridge.

    mcp.tc/i/ros

  • MATLAB

    MathWorks

    state.local.label (state.local.title)

    Run MATLAB code, tests and static code analysis from an AI assistant using a local MATLAB install.

    mcp.tc/i/matlab

  • Google Colabvf.sr

    Google (Colab)

    state.local.label (state.local.title)

    Connect a local agent to a Google Colab notebook session open in your browser.

    mcp.tc/i/colab

  • Jupyter MCP Server

    Datalayer

    state.local.label (state.local.title)

    Read, edit and execute cells in live Jupyter notebooks from your AI assistant.

    mcp.tc/i/jupyter

  • Nx

    Nx (Nrwl)

    state.local.label (state.local.title)

    Give your AI assistant Nx workspace context: project graph, project details, generators and up-to-date Nx docs.

    mcp.tc/i/nx

listing.disclaimer_checked