U Ministry Utility
25“"This is an MCP Server that enables scalable mobile automation, development through a platform-agnostic interface, eliminating the need for…”
source unavailable
mobile-next/mobile-mcp
Model Context Protocol Server for Mobile Automation and Scraping (iOS, Android, Emulators, Simulators and Real Devices)
Trust Score
54.2
Last full review 2026-09-27 · Trust Score decays −2 points per month without a fresh review (never below 20)
U Ministry Utility
25“"This is an MCP Server that enables scalable mobile automation, development through a platform-agnostic interface, eliminating the need for…”
source unavailable
M Maturity
75“"latest tag 1.0.4 published 2026-09-13T20:24:38Z" (api.releases); "pushed_at": "2026-09-23T15:38:57Z" (api.repos); "commits_90d": 72…”
source unavailable
S Security / License
45.0 → 56.2 (+11.2 over window)
ranked #1 of 27 in G2
mobile-next/mobile-mcp looks like a candidate for ai, agents & mcp servers; General-purpose mobile automation MCP server with no ministry-specific features or church/faith context.
Use it with
Selected: Gloo AI Studio
Tool names and logos belong to their owners; shown so you can pick your own client. Not affiliated.
Step 1 — Connect Refinry once (prompt only)
Gloo AI Studio does not document external MCP server setup. Use this prompt with the copied Refinry research brief in Studio.
https://studio.ai.gloo.com/I am choosing open-source software for my ministry using Refinry, a review site. Read Refinry’s plain-language agent feed — https://refinry.dev/docs.md — then help me evaluate mobile-next/mobile-mcp: summarize the Trust Score, the strongest and weakest dimensions, and any caution flags it cites. Give me one small first step I can complete this week, and tell me honestly if this looks like more than I can handle.
Some clients need manual setup. Follow the plain-language steps on the Docs page.
Step 2 — Plan your first step
Tell the AI what you want to do; edit this to match your situation.
I am choosing open-source software for my ministry using Refinry, a review site. Read Refinry’s public review of mobile-next/mobile-mcp (https://refinry.dev) and help me assess it for using mobile-next/mobile-mcp for ai, agents & mcp servers in my ministry. Summarize the Trust Score, the strongest and weakest dimensions, and any caution flags it cites, separating reviewed evidence from what still needs verification. Give me one small first step I can complete this week, and tell me honestly if this looks like more than I can handle.
Prefer a hand-off that works without a connection? Copy the research brief: every reviewed fact, all caution flags, and a feasibility-only first assignment.
license 75 · security 75
“"license.spdx_id": "Apache-2.0" (api.repos) — permissive license; "osv_vulns": []" and "security_md": {"present": true}" (security) — clean…”
source unavailable
A Ease of Adoption
50dev 75 · volunteer 25
“"npx" and "@mobilenext/mobile-mcp@latest" with VS Code install badge (README) — one-command install for developers; however requires mobile…”
source unavailable
C Community Trust
50“"stargazers_count": 7889" and "forks_count": 672" (api.repos) — one weak input; "benlmyers" with 3 contributions (api.contributors) shows…”
source unavailable
I AI-Agent Integrability
75“"This is an MCP Server" with "Works with Claude Code, Codex, Gemini, GitHub Copilot, Antigravity — or any MCP-compatible client" (README) —…”
source unavailable