Mobile MCP
Is it safe?
No known CVEs for @mobilenext/mobile-mcp. 1 previously resolved.
No authentication — any process on your machine can connect to this server.
License not specified.
Last scanned 0 days ago.
Is it maintained?
Last commit 0 days ago. 4,311 GitHub stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
How much context will it use?
0 tools. Token cost not measured.
What if it doesn't work?
Common issues: JSON syntax errors in config, wrong Node.js version, npx cache. Setup guide covers troubleshooting. Or check GitHub issues for known problems.
{
"mcpServers": {
"mobile-mcp": {
"command": "npx",
"args": [
"-y",
"@mobilenext/mobile-mcp"
]
}
}
}Auto-generated from package name. Add to your client's MCP config file.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y @mobilenext/mobile-mcp 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
This server is missing description, tools, and install config. If you've used it, help the community by adding this info.
Add informationLast scanned 2h ago
No open vulnerabilities. 1 fixed CVE.
CVE-2026-33989Fixed@mobilenext/mobile-mcp alllows arbitrary file write via Path Traversal in mobile screen capture tools
### Summary The `@mobilenext/mobile-mcp` server contains a Path Traversal vulnerability in the `mobile_save_screenshot` and `mobile_start_screen_recording` tools. The `saveTo` and `output` parameters were passed directly to filesystem operations without validation, allowing an attacker to write files outside the intended workspace. ### Details **File:** `src/server.ts` (lines 584-592) ```typescript tool( "mobile_save_screenshot", "Save Screenshot", "Save a screenshot of the mobile
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.