Agent Device (callstack) vs Chrome DevTools MCP
Two MCP servers from our browser automation ranking, compared on live data - updated nightly, never sponsored.
Bottom line · 2026-08-25
Chrome DevTools MCP records significantly more monthly package installs (7,879,708 vs 586,584); both are actively maintained, with commits inside the last month.
How they differ in kind
Agent Device (callstack) focuses on: Mobile app automation and verification for AI coding agents. Chrome DevTools MCP focuses on: Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser.
What each one does
Agent Device (callstack)
Mobile app automation and verification for AI coding agents. Give coding agents a live app feedback loop through a CLI, built-in MCP server, or typed Node.js API. It runs locally over stdio via the published package.
From the project's README.
Chrome DevTools MCP
Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser. It acts as a Model-Context-Protocol (MCP) server, giving your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in-depth debugging, and performance analysis. Its 40 documented tools cover heapsnapshot, page, performance, take.
From the project's README.
14 signals, side by side
| Signal | Agent Device (callstack) | Chrome DevTools MCP |
|---|---|---|
| Monthly installs | 586,584 | 7,879,708 |
| GitHub stars | 4,212 | 49,617 |
| Last commit | 2026-08-24 | 2026-08-23 |
| Releases · last 90 days | 10+ | 7 |
| In the registry since | Aug 2026 | Sep 2025 |
| Registry versions | 4 | 49 |
| Documented tools | not extracted - see README | 40 |
| Env vars extracted | none extracted - see README | none extracted - see README |
| Runs | local (stdio) | local (stdio) |
| Endpoint auth | local only | local only |
| Maintenance | actively maintained | actively maintained |
| License | MIT | Apache-2.0 |
| Language | TypeScript | TypeScript |
| Category rank | #3 of 196 | #2 of 196 |
What their tools cover
Extracted from each project's README - the tools each server hands your agent. A missing list means the README doesn't document one, not that no tools exist.
Agent Device (callstack) no tool list in README
Chrome DevTools MCP 40 tools documented
clickdragfillfill_formhandle_dialoghoverpress_keytype_text
+32 more on the full page
Which one, for what
Derived from the signals above, not hands-on testing.
Pick Agent Device (callstack) if…
- → release velocity matters - 10+ releases in 90 days vs 7
- → category standing - #3 of 196 maintained browser automation servers
Pick Chrome DevTools MCP if…
- → you want the more widely installed option - 7,879,708 monthly installs vs 586,584
- → its documented toolset fits - 40 tools including click, drag
Who's behind them
Agent Device (callstack) - callstack: 1 MCP server tracked, 1 maintained, 4,212 combined stars.
Chrome DevTools MCP - chromedevtools: 1 MCP server tracked, 1 maintained, 49,617 combined stars.
Not sold on either?
The next-ranked browser automation servers we track:
Quick answers
Is Agent Device (callstack) better than Chrome DevTools MCP?
Package installs favor Chrome DevTools MCP: 7,879,708 monthly installs to 586,584. Agent Device (callstack) still ranks #3 of 196 maintained browser automation servers. Data as of 2026-08-25; we haven't hands-on tested either.
Can I use Agent Device (callstack) and Chrome DevTools MCP together?
Yes - MCP clients accept multiple servers in one config, so you can enable both browser automation servers side by side. If their tools overlap, keep the one whose toolset fits to keep your agent's tool list lean.
Keep exploring: best browser automation servers · TypeScript servers · all comparisons · every server
Methodology: package-usage signal = npm/PyPI installs (last month, platform APIs) · maintenance = commit recency + release cadence (GitHub) · tool lists and environment-variable names extracted from each project's README · endpoint auth from our own nightly probes. We haven't hand-tested these servers; everything here is data as of 2026-08-25.