Swipium MCP server
io.github.GeroPalombo/swipium·v2.4.0Mobile QA on local Android Emulators and iOS Simulators: autopilot tests, evidence, reports.
not scanned yet
0 stars38 downloads/wk
Reviews
Write oneNobody has reviewed Swipium yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Swipium tools
No tool declarations could be read from the package source. They show once the server is installed.
How Swipium compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 65% of 48,255 servers
- Downloads a week
- 38
- more than 29% of 12,191 servers with a package
Release history: 3 versions in the registry since 2026-10-12, latest 2026-11-02, typically one every 13 days.
Install Swipium in Claude Code, Cursor or VS Code
Runs npx -y swipium on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add swipium -- npx -y swipium
What the publisher says
From the Swipium repository's README, as published. We do not edit it. Read it on GitHub
Swipium
An MCP server that lets coding agents QA mobile apps on Android Emulators and iOS Simulators.
Swipium gives an AI coding agent (Claude Code, Codex, Gemini CLI, Cursor, VS Code, and other MCP clients) the tools a QA engineer uses: find or build the app, boot a simulator, install and launch it, read the screen, tap and type through real user flows, and write a report backed by screenshots, logs, and UI dumps. A run can be turned into a repeatable flow, a test suite, or Appium code.
It is for mobile developers who want their agent to catch the broken login screen before a TestFlight or Play Console build. It runs locally (stdio; the server opens no network port, and the WebDriverAgent it manages for iOS takes commands on 127.0.0.1 only, though its screen stream port is reachable from the network; see Security), drives devices through adb, simctl, and WebDriverAgent rather than Appium, and asks your consent before anything with side effects. swipium.com
A session, abbreviated
You: Smoke test this app on Android with Swipium.
Agent > qa_test_this { goal: "smoke", waitForCompletion: true } (runs by default)
🔐 Consent required (low): • boot_emulator: emulator -avd Pixel_8_API_35 -no-audio -no-snapshot-save -no-boot-anim -gpu auto -no-window
• install_apk: adb -s <Pixel_8_API_35 once booted> install -r -g android/app/.../app-release.apk
You: Approve (one prompt covers boot + install)
state: "running", sessionId: "3f9c2a1b", jobId: "a41c09e2"
Agent > qa_job_status { sessionId: "3f9c2a1b", jobId: "a41c09e2", waitMs: 45000 }
status: "done", result.state: "completed"
reportHead: "RELEASE RISK: SHIP … app: PASS … coverage: COVERED … tool: PASS …"
nextRecommendedAction: qa_get_artifact { uri: "swipium://session/3f9c2a1b/report/…-summary.md" }
Agent: The app launched and passed the smoke checks with no crashes or error screens.Three calls: start the run, wait for it, and (only when the inlined head isn't enough) read report.md. The report behind that summary, rendered with npx swipium report --latest --format markdown, includes:
**Release risk: 🟢 SHIP**
**App status:** PASS - No high-severity app/native finding observed in this run.
**Coverage status:** COVERED - Structured smoke/workflow evidence was collected.
**Tool status:** PASS - No Swipium/MCP limitations or tool errors recorded in this run.Contents
Requirements · Quickstart · Starter prompts · How it works · Tools · Where results go · Configuration · CLI · CI · Upgrading · Troubleshooting · Security
Requirements
Node.js 22.12 or newer. On an older Node.js the server prints a warning on stderr and swipium verify fails. Swipium works with emulators and simulators only; physical devices are refused with PHYSICALDEVICEUNSUPPORTED (why). Structured iOS automation needs WebDriverAgent 6.0 or newer (qa_wda {action:"setup"} builds and starts one); without it an iOS Simulator is visual-only.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Swipium: common questions
- Is Swipium MCP server safe?
- Mostly: it is graded B (83/100). Read the Swipium safety report
- How do I install Swipium?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Swipium need an API key?
- Yes. The registry entry asks for
SWIPIUM_TEST_PASSWORD. - Is Swipium maintained?
- The last commit was 23 days ago (2026-10-12). The latest release is v2.4.0.
- What can I use instead of Swipium?
- Servers from other publishers that do the same job: Mobile MCP server, MCP Appium - Mobile Development and Automation Server MCP server and Mobilerun MCP server. Compare all Swipium alternatives.
- How does Swipium compare with other MCP servers?
- safety score 83/100 (higher than 65% of 48,255 servers); downloads a week 38 (more than 29% of 12,191 servers with a package). Full comparison.
Alternatives to Swipium
Same job from other publishers: the closest match first, then the best rated.
- MobileMCP server for iOS and Android Mobile Development, Automation and Testingnot reviewedWidely usedA
- MCP Appium - Mobile Development and Automation ServerMCP server for Appium mobile automation on iOS and Android devices with test creation tools.not reviewedEstablishedA
- MobilerunLet AI agents control Android and iOS devices on Mobilerun Cloud: screen, input, apps, workflows.not reviewedEstablishedA