
Drengr
- Updated July 5, 2026
- SharminSirajudeen/drengr-community
Drengr is a MCP server that gives AI agents eyes and hands on Android and iOS devices via stdio.
About
Drengr (dev.drengr/server) is a Model Context Protocol server that connects AI coding agents to Android and iOS devices so they can observe screens and perform actions like a remote tester. Developers shipping mobile apps with Claude Code, Cursor, or Codex can register the stdio npm package drengr instead of manually driving every tap during iterative fixes. Use it when you want agent-assisted reproduction of bugs, smoke flows, or accessibility checks on real hardware or simulators. It complements repo-side skills and integrations—it does not replace XCTest, Espresso, or store submission tooling. Expect to pair it with your existing mobile stack and device provisioning; the catalog treats it as agent tooling for native mobile products rather than a generic cloud browser automation MCP.
- stdio MCP server (npm package drengr, v0.8.0) for agent-driven mobile interaction
- Positions itself as eyes and hands for agents on Android and iOS
- Community repo: github.com/SharminSirajudeen/drengr-community
- Fits solo builders automating on-device QA and exploratory UI passes from the agent chat
Drengr by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add drengr -- npx -y drengrAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | drengr |
|---|---|
| Transport | STDIO |
| Auth | None |
| Last updated | July 5, 2026 |
| Repository | SharminSirajudeen/drengr-community ↗ |
What it does
Give Claude or Cursor real screen taps, gestures, and UI reads on physical or emulated Android and iOS devices while you ship mobile features.
Who is it for?
Best when you already use MCP with Claude Code or Cursor and want agent-led device interaction during feature work.
Skip if: Skip if you only ship web or API backends with no mobile runtime, or anyone and needs official store CI without local device setup.
What you get
After you add dev.drengr/server to your agent, the model can drive on-device UI flows and observations while you iterate on mobile builds.
- Registered stdio MCP connection to dev.drengr/server
- Agent-visible control and observation channel on a mobile target
By the numbers
- Server version 0.8.0
- npm identifier: drengr
- Transport: stdio
README.md
Drengr
Eyes and hands for AI agents on mobile devices.
Drengr is an MCP server that gives AI agents (Claude, GPT, Gemini) the ability to see, tap, type, and navigate mobile apps — Android and iOS.
Install
npm install -g drengr
Or run without installing:
npx drengr
Or via shell script:
curl -fsSL https://drengr.dev/install.sh | bash
Quick Setup
# Check your system
drengr doctor
# Configure your MCP client (Claude Desktop, Claude Code, Cursor, etc.)
drengr setup
Add to Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"drengr": {
"command": "drengr",
"args": ["mcp"]
}
}
}
Add to Claude Code
claude mcp add drengr -- drengr mcp
Add to Cursor
Add to .cursor/mcp.json in your project:
{
"mcpServers": {
"drengr": {
"command": "drengr",
"args": ["mcp"]
}
}
}
What Drengr does
- 3 MCP tools:
drengr_look(observe screen),drengr_do(take action),drengr_query(ask questions) - Android & iOS — ADB for Android, simctl for iOS, Appium for cloud devices
- Vision-first — sees your app like a human via annotated screenshots
- Text mode — ~300 tokens per screen instead of 100KB images
- Situation reports — after every action: what changed, what's new, is it stuck?
- Screen exploration — auto-maps your app's navigation graph
- Network capture — sees HTTP calls during each action
Supported platforms
| Platform | Architecture | Supported |
|---|---|---|
| macOS | arm64 (M1+) | ✓ |
| macOS | x64 | ✓ |
| Linux | x64 | ✓ |
| Linux | arm64 | ✓ |
Documentation
Full documentation at drengr.dev
License
Proprietary — © 2026 Drengr. All rights reserved. See LICENSE for details.
Recommended MCP Servers
How it compares
Native mobile device MCP bridge, not a headless browser or Playwright-style web automation server.
FAQ
Who is dev.drengr/server for?
Developers and small teams shipping Android or iOS apps who want their coding agent to interact with real or emulated devices through MCP.
When should I use dev.drengr/server?
Use it during Build when you are implementing or debugging mobile UI and want the agent to observe and act on the device instead of only editing source files.
How do I add dev.drengr/server to my agent?
Register the stdio MCP entry pointing at the npm package drengr (v0.8.0), install Node dependencies per the drengr-community repo, and connect your configured Android or iOS target.