podium-mcp
Related Servers
Alternatives to podium-mcp
- AlicenseAqualityAmaintenanceA Model Context Protocol server that enables scalable mobile automation through a platform-agnostic interface for iOS and Android devices, allowing agents and LLMs to interact with mobile applications using accessibility snapshots or coordinate-based interactions.3223,436 npm6,679Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for cross-platform mobile automation (iOS/Android) using accessibility trees and screenshots, enabling agents to interact with apps on simulators, emulators, and physical devices.7Apache 2.0
Related Servers
- AlicenseNot gradedqualityCmaintenanceLocal MCP server for iOS Simulator and macOS app automation with a TypeScript MCP layer and Swift native bridge. Enables UI inspection, input automation, and simulator control through unified generic tools.23 npm26MIT

SilbercueSwiftofficial
AlicenseNot gradedqualityBmaintenanceHigh-performance MCP server for iOS development and test automation. Gives AI coding assistants direct access to iOS simulators with sub-20ms screenshots, UI interaction, building, testing, and an intelligent operator mode.8MIT- AlicenseNot gradedqualityBmaintenanceMCP server for mobile device testing with iOS simulators, Android emulators, and USB devices, managing Maestro flows, device diagnostics, screenshots, logs, and React Native/Expo development plumbing.7 npmMIT
- AlicenseAqualityDmaintenanceUnified MCP server for Xcode + iOS Simulator — build, deploy, screenshot, and interact with your iOS app from Claude Code, Cursor, or any MCP client. Built in Swift. Single binary. No Node/Python runtime required.69MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI to control iOS simulators through the MCP protocol. Supports device management, UI automation, and network interception including screenshot capture, text input, and HTTP request mocking.-
- AlicenseNot gradedqualityDmaintenanceMCP server and CLI for iOS development — build, test, automate, and diagnose from any AI agent or terminal.1MIT
TDQS
Scored across 43 tools
Each tool has a clearly distinct purpose. App management, device operations, Metro debugging, WebView interactions, gestures, assertions, and utilities are all well-separated with no overlap.
All tool names follow a consistent verb_noun pattern with underscores, e.g., app_install, crash_list, webview_inspect. No mixed conventions.
With 43 tools, the server has far more than the typical 3-15 well-scoped range. While each tool is specialized, the count feels excessive and may overwhelm agents.
The tool surface covers a broad spectrum of mobile test automation tasks: app lifecycle, device control, gestures, assertions, Metro debugging, WebView interaction, and network capture. Minor gaps exist (e.g., no tool for clearing app data), but overall it is very comprehensive.