M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionMCP AppiumAppium MCP server for iOS and Android mobile automationGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS57 / 100 · C76 / 100 · B
Reliability9 / 2013 / 20
Security and permissions12 / 2014 / 20
Maintenance11 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience11 / 2014 / 20
Best for
  • Teams doing Android/iOS automation testing with Appium
  • Developers who want to create and debug mobile tests in natural language
  • Engineering teams that need generated test code and Page Object templates
  • Teams running mobile automation in trusted CI environments
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Shared or multi-tenant services exposed to untrusted users
  • Environments without Android SDK, Xcode, or a Java toolchain
  • Pure browser or desktop web automation instead of mobile
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Read access to the local Android SDK and Xcode/simulator setup
  • Access to local mobile devices or emulators through adb or simulator tooling
  • Read/write access to the screenshots and recordings directory (SCREENSHOTS_DIR or the system temp directory)
  • Optional: network access to a remote Appium/WebDriver server (remoteServerUrl)
  • Optional: outbound calls to an external vision model API (AI_VISION_API_BASE_URL and AI_VISION_API_KEY)
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • remoteServerUrl is caller-controlled; if it is derived from untrusted input it can reach unintended servers, so restrict destinations with REMOTE_SERVER_URL_ALLOW_REGEX
  • By default the server deletes all MCP-owned Appium sessions when the MCP client disconnects, and transports that drop easily such as httpStream can tear down automation in one go; use APPIUM_MCP_ON_CLIENT_DISCONNECT=skip to keep them
  • Enabling vision element finding sends screenshots to a third-party vision API, which can incur cost and data exposure
  • Persisted session files may contain credentials and sensitive capabilities (created with 0600 permissions)
  • Plugins execute inside the server process, so only trusted files and packages should be loaded
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsCursor, Claude Code, Gemini CLIClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools2015