MCP Appium Server

Created By
Rsec08a year ago
MCP SERVER for appium
Overview

what is MCP Appium Server?

MCP Appium Server is a Model Context Protocol (MCP) server implementation designed for mobile app automation using Appium, enabling developers to automate testing for both Android and iOS applications.

how to use MCP Appium Server?

To use the MCP Appium Server, you need to set up the necessary prerequisites, install dependencies, and configure your mobile device or emulator. After setting up, you can run tests by starting the MCP server and executing your test scripts.

key features of MCP Appium Server?

  • Supports automation for both Android and iOS applications.
  • Provides various Appium actions such as element interactions, app management, and device controls.
  • Allows context switching between Native and WebView.
  • Advanced features like custom gestures and file operations.

use cases of MCP Appium Server?

  1. Automating UI tests for mobile applications.
  2. Running regression tests on different devices and platforms.
  3. Integrating with CI/CD pipelines for continuous testing.

FAQ from MCP Appium Server?

  • What are the prerequisites for using MCP Appium Server?

You need Node.js, JDK, Android SDK, Xcode (for iOS), and Appium Server installed.

  • Can I use MCP Appium Server for both Android and iOS?

Yes, MCP Appium Server supports automation for both Android and iOS applications.

  • How do I troubleshoot connection issues?

Ensure the Appium server is running, check for port conflicts, and verify that the correct capabilities are set.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Rsec08
Star
0
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago