Agent Device vs Fenestra

In-depth architectural comparison of the Agent Device and Fenestra MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Agent Device when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Cross-platform support for iOS, Android, tvOS, macOS, Linux, and web, Accessibility tree snapshots with token-efficient element references, UI actions including press, fill, scroll, wait, and alert handling.

Explore Agent Device Details

Choose Fenestra when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Deterministic headless rendering without GPU/display, Semantic querying and interaction of UI elements, Accessibility checks: contrast, focus order, hit target size.

Feature & Specification Comparison

Specification	Agent Device callstackincubator Browser Automation	Fenestra richer-richard Browser Automation
Summary	Discovery router for the agent-device CLI. Exposes status, install guidance, version-matched help, prompts, and resources for iOS, Android, tvOS, macOS, and Linux automation workflows.	Render and verify native Rust GUIs with no display or GPU: render to a typed accessibility tree, query/interact by semantic selector (never coordinates), check contrast/focus-order/hit-target-size, diff screenshots, and watch motion play as a captioned filmstrip. 13 tools. cargo install fenestra-mcp.
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

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

{
  "mcpServers": {
    "richer-richard-fenestra": {
      "command": "npx",
      "args": [
        "-y",
        "richer-richard-fenestra"
      ]
    }
  }
}

Related MCP Server Comparisons