agent-device
Earlier Revision Confidence: Good (0.85)agent-device is an MCP server published by Callstack, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. It is the first-party server from Callstack. Last verified 2026-08-07.
Does agent-device support the current MCP specification (2026-07-28)?
Not yet confirmed. agent-device is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-07.
Is agent-device a first-party (official) MCP server?
Yes. agent-device is the first-party MCP server published by Callstack (last verified 2026-08-07).
How do I connect to agent-device?
agent-device is available via the package npm:agent-device, the official MCP Registry under io.github.callstack/agent-device, the source repository at https://github.com/callstack/agent-device. Authentication: none. Transports: stdio.
Does agent-device support MCP revision 2025-11-25?
Yes. agent-device supports MCP revision 2025-11-25 (checked 2026-08-07).
When were agent-device's facts last verified?
2026-08-07. Each fact on this page links to the sources used to verify it.
agent-device is Callstack's CLI for app automation from coding agents.
Its README covers the span: agents can "inspect, control, and verify
apps on iOS, Android, tvOS, Android TV, Amazon Vega OS TV through the
Vega Virtual Device (VVD), web, macOS, and Linux", reading accessibility
snapshots, acting through refs and selectors, and pulling screenshots,
logs, traces, network data, and crash details for debugging.
agent-device mcp starts what the docs call the official stdio MCP
server, exposing structured tools over the installed CLI commands.
The MCP layer is hand-rolled rather than SDK-based: package.json
declares no MCP SDK dependency, and src/mcp/router.ts implements the
JSON-RPC surface directly. That file hard-codes
SUPPORTED_PROTOCOL_VERSION = '2025-11-25' and returns it from the
initialize handler, which grounds this record's legacy status: the
shipped code negotiates 2025-11-25 and implements no 2026-07-28
discovery path.
Two registry identities exist because the repository moved from the
callstackincubator org to callstack. The current record,
io.github.callstack/agent-device, tracked 0.20.6 on 2026-08-07; the
older io.github.callstackincubator/agent-device record remains active
at 0.16.9 from June. The stale record's version sits inside the range of
GHSA-m7q5-6423-2mwq (published 2026-08-03, patched in 0.20.4), a
medium-severity issue where a repository-supplied agent-device.json
could redirect remote-daemon credentials to an attacker-controlled URL.
The advisory affects the optional remote-daemon path only, not the
local stdio transport.
Which MCP spec revisions does agent-device support?
agent-device has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source |
How widely adopted is agent-device?
Ranked #8 in The MCP 500 with Adoption Index 88.43 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| GitHub stars | 4,094 | API · |
| GitHub forks | 252 | API · |
| Last push | 2026-08-14T09:06:34Z | API · |
| Repository archived | no | API · |
How was this verified, and what are the sources?
Verified · method: repo-source
· confidence 0.85 (Good).
- Official MCP Registry record io.github.callstack/agent-device version 0.20.6 (published 2026-08-07) - npm package agent-device; the older record io.github.callstackincubator/agent-device remains active in the registry at version 0.16.9 (published 2026-06-01) from before the repository moved from the callstackincubator org to callstack - accessed
- callstack/agent-device README - "agent-device lets coding agents inspect, control, and verify apps on iOS, Android, tvOS, Android TV, Amazon Vega OS TV through the Vega Virtual Device (VVD), web, macOS, and Linux"; package.json author field reads "Callstack" and mcpName reads io.github.callstack/agent-device - accessed
- agent-device docs, "AI Agent Setup" - "agent-device mcp starts the official stdio MCP server. It exposes direct structured tools for installed CLI commands"; tool failures return MCP tool results with isError true - accessed
- src/mcp/router.ts on main - declares const SUPPORTED_PROTOCOL_VERSION = '2025-11-25' and returns it from the initialize handler; the MCP layer is hand-rolled, with no @modelcontextprotocol/sdk dependency in package.json - accessed
- GitHub security advisory GHSA-m7q5-6423-2mwq, "agent-device Project Config Redirects Remote Daemon Credentials" - medium severity, CWE-200, published 2026-08-03, vulnerable range >= 0.8.0, <= 0.20.3, patched in 0.20.4; affects the optional remote-daemon path, not the local stdio transport - accessed