Drengr MCP server
{
"mcpServers": {
"drengr": {
"command": "npx",
"args": [
"-y",
"drengr@latest"
]
}
}
}{
"mcpServers": {
"drengr": {
"command": "npx",
"args": [
"-y",
"drengr@latest"
]
}
}
}{
"mcpServers": {
"drengr": {
"command": "npx",
"args": [
"-y",
"drengr@latest"
]
}
}
}{
"servers": {
"drengr": {
"command": "npx",
"args": [
"-y",
"drengr@latest"
]
}
}
}{
"mcpServers": {
"drengr": {
"command": "npx",
"args": [
"-y",
"drengr@latest"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y drengrversion 0.10.8
What it does
Drengr is an MCP server that enables AI agents to see and interact with Android and iOS mobile apps through screenshot observation, tapping, typing, and navigation. It's for developers who want to automate mobile app testing, exploration, or control via Claude, GPT, or Gemini.
- Automate mobile app testing by having an AI agent navigate screens, tap buttons, enter text, and verify behavior.
- Explore and map a mobile app's navigation structure and functionality automatically.
- Monitor mobile app interactions including HTTP network calls made during each action.
Tools this server exposes
| Tool | Does |
|---|---|
| drengr_look | Observe the current mobile device screen with annotated visual information. |
| drengr_do | Take actions on a mobile device such as tapping, typing, and navigating between screens. |
| drengr_query | Ask questions about the mobile app or current screen state. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.