Drengr
Give Claude or Cursor real screen taps, gestures, and UI reads on physical or emulated Android and iOS devices while you ship mobile features.
Overview
Drengr is a MCP server for the Build phase that gives AI agents eyes and hands on Android and iOS devices via stdio.
What is this MCP server?
- 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
- Server version 0.8.0
- npm identifier: drengr
- Transport: stdio
What problem does it solve?
Coding agents can edit mobile code in the repo but cannot see or touch the running app on a phone or simulator without a dedicated device bridge.
Who is it for?
Indie mobile builders who already use MCP with Claude Code or Cursor and want agent-led device interaction during feature work.
Skip if: Teams that only ship web or API backends with no mobile runtime, or anyone who needs official store CI without local device setup.
What do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
Mobile agent control lands in Build because you wire device bridges while implementing and exercising app flows, not during initial idea research. agent-tooling is the shelf for MCP servers that extend what coding agents can perceive and do beyond the repo—here, native mobile surfaces.
How it compares
Native mobile device MCP bridge, not a headless browser or Playwright-style web automation server.
Common Questions / FAQ
Who is dev.drengr/server for?
Solo builders 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.