mobile-next/mobile-mcp

Model Context Protocol Server for Mobile Automation and Scraping (iOS, Android, Emulators, Simulators and Real Devices)

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 19 seconds ago
Added to GitGenius on September 10th, 2026
Created on March 28th, 2025
Open Issues & Pull Requests: 50 (+0)
GitHub issues: Enabled
Number of forks: 576
Total Stargazers: 6,658 (+0)
Total Subscribers: 44 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 25.9 hours
Mean response time: 6.6 days
90th percentile: 23.6 days
Tracked items: 146

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 7% of issues opened in the past year have been closed. Three people close 79% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 33
New in 7 days: 1
Closed in 7 days: 8
Avg open age: 263 days
Stale 30+ days: 27
Stale 90+ days: 23

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • waiting for reporter (22)
  • enhancement (14)
  • bug (12)
  • documentation (6)
  • duplicate (4)
  • help wanted (1)

Detailed Description

Mobile Next MCP is a Model Context Protocol server that enables mobile automation and scraping across iOS, Android, emulators, simulators, and real devices through a unified interface.

The tool solves the problem of controlling mobile applications without requiring separate expertise for each platform. It works by providing agents and language models with structured accessibility snapshots or screenshot-based coordinate interactions, allowing them to automate native app interactions, scripted flows, form submissions, and multi-step user journeys. The server operates on local devices or integrates with cloud-based real device infrastructure, presenting the same interface regardless of deployment location.

Developers should choose this tool if they need to automate mobile testing, data entry, or user journey workflows across both iOS and Android without maintaining platform-specific knowledge. It suits projects requiring agent-driven mobile interaction, whether for testing frameworks, data extraction, or general application automation. The tool works with multiple MCP-compatible clients including Claude Code, Codex, Gemini, and GitHub Copilot, making it flexible for different development environments.

The project shows active development with regular updates and maintenance across its codebase. The team maintains comprehensive documentation including a wiki and provides multiple language resources for the README. Community engagement is supported through an active Slack channel where users can ask questions and share experiences.