app-automating
PulseGate's liveness check found it on 10 Sep 2026; it is registered on GitHub and PyPI and has been in the index since 10 Sep 2026. How this is checked
app-automating is an open-source MCP server that drives Android emulators and physical devices for app automation and testing. It uses persistent memory of navigation paths to help developers and QA engineers repeat workflows more efficiently.
Inferred · not functionally tested
Overview
6 featuresPurpose: Automating Android apps across emulators and devices without repeatedly rediscovering navigation paths.
Inferred · not functionally tested
Audience: Android developers and QA engineers
Inferred · not functionally tested
Functions: browser_automation
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted, api_only
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: pypi.org · github.com. These links do not verify the individual claims.
app-automating sits in PulseGate's Browser DevTools & extensions category. Inferred · not functionally tested: It focuses on automating Android apps across emulators and devices without repeatedly rediscovering navigation paths. Inferred · not functionally tested: app-automating is an open-source project aimed at android developers and QA engineers. Basis unknown · not verified: app-automating is open source under the MIT license. Basis unknown · not verified: It runs on the command line and API, and it can be self-hosted.
Behind app-automating is dkmostafa, and it first shipped in 2026. The project is developed in the open on GitHub with 10 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are android automation, emulator control, and real device control. Inferred · not functionally tested: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Android automation
- Emulator control
- Real device control
- MCP server
- Appium support
- Navigation memory
Topics: Inferred · not functionally tested
Built with & integrations
- Claude Code
- .claude/
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed10 Sep · 22:59 UTCapp-automating seen via PyPI Bulk EnumeratorSource: PyPI Bulk Enumerator · Open
Frequently asked questions about app-automating
- What is app-automating?
- Inferred · not functionally tested: App-automating focuses on automating Android apps across emulators and devices without repeatedly rediscovering navigation paths. It is catalogued under Browser DevTools & extensions on PulseGate.
- Who is app-automating for?
- Inferred · not functionally tested: app-automating is an open-source project built for android developers and QA engineers.
- Is app-automating free?
- Basis unknown · not verified: Yes — app-automating is open source under the MIT license and free to use.
- What platforms does app-automating run on?
- Basis unknown · not verified: app-automating runs on the command line and API. It can also be self-hosted.
- Is app-automating still maintained?
- PulseGate's liveness check found it on 10 Sep 2026. Its GitHub repository shows 10 commits in the last 90 days.
- What projects are similar to app-automating?
- Similar projects tracked by PulseGate include mcp-appium, AutoMobile, and maa-mcp.mcp-appiumAutoMobilemaa-mcp
- Who makes app-automating?
- app-automating is developed by dkmostafa.
- How long has app-automating been around?
- app-automating first shipped in 2026.
Similar projects
Closest matches by what these projects do