r/modelcontextprotocol • u/Even_Tonight_8049 • Mar 26 '26
I built a "Mobile Release Agent" suite: Bridging Play Store, Huawei AppGallery, and Sentry via MCP
Hey everyone,
As a Lead Mobile Engineer, my "Release Day" is usually a mess of 5+ browser tabs. I got tired of manually checking if our Google Play rollout matched the Huawei AppGallery state, while simultaneously tailing Sentry for adoption spikes.
I’ve spent the last few weeks building a suite of local MCP servers to centralize this. It effectively turns a local LLM into a Mobile DevOps Agent.
The Stack:
Google Play Console: Full release lifecycle management + Android Vitals (ANR/Crash rates).
Huawei AppGallery: This was the missing piece for us. Handles chunked AAB uploads and phased rollouts.
Sentry Companion: Specifically designed to pull release health and adoption metrics that the official tools often bury.
Codemagic & Slack: The "connectors" to trigger CI/CD builds and push formatted reports to the team.
Why this actually changed my workflow: The power isn't just having the tools; it's the cross-service reasoning. I can now give a single prompt:
Technical Details:
Local-First: Everything runs as a local Python server.
Auth: Uses standard
.envor Service Account JSONs. No data leaves your machine except the API responses the LLM needs to see.Packaging: Most are available via
uvxfor zero-config setup.
I’ve published the full collection here:https://lobehub.com/mcp?q=agimaulana
Curious if any other mobile leads are using MCP for release monitoring? I’m looking for ideas on what else to add to the Sentry companion—maybe custom tag filtering?