mcp-appium-gestures

This MCP server provides documentation resources for common Appium gestures (tap, swipe, scroll, pinch/zoom, long press, drag-and-drop, and double-tap) and tools to generate code in JavaScript (WebdriverIO v9+ and older) and Java. You can access gesture documentation directly via the gesture:// URIs (e.g., gesture://tap) and use the built-in code generation tools to produce ready-to-use snippets for your test suites. In Claude or similar clients, you can configure the appium-gestures MCP under your mcpServers section and invoke its tools to generate language-specific code or fetch gesture docs for integration in your projects.

Prerequisites:

• Node.js and npm installed on your machine
• Internet access to install dependencies via npm

Install and run locally:

1. Clone the repository (replace with the actual URL if different): git clone https://github.com/yourusername/mcp-appium-gestures.git cd mcp-appium-gestures
2. Install dependencies: npm install
3. Start the server (stdio transport by default): npm start or npm run start:stdio

Optional: start with SSE transport for remote usage (if supported by the project): npm run start:sse npm run start:sse:port 3000

Tests and development:

• Run internal tests or linting as defined in package.json, e.g. npm run dev or npm run inspect

Tips and common issues:

• Ensure Node.js version compatibility as documented in package.json engines section; use nvm to manage Node versions if needed.
• If the server fails to start, check that dependencies are installed correctly (npm install) and that port usage (for SSE) does not conflict with other services.
• When using Claude integration, ensure the mcp_settings.json file includes the appium-gestures entry with the correct command and transport settings as shown in the README example.
• The tools support generating code for both JavaScript and Java. Use the language parameter to select the target language, and provide coordinates or element IDs as required by each tool (e.g., generate-tap-code, generate-swipe-code, etc.).
• Documentation resources are accessible via gesture:// URIs; use those endpoints to quickly reference gesture usage and parameters.