Manage Appium 2.x drivers and plugins from the command line
domain: appium.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Install the Appium 2 server globally with npm install -g appium
List available and installed extensions with appium driver list --installed and appium plugin list --installed
Install a driver with appium driver install uiautomator2, or pin a version with appium driver install uiautomator2@<version>
Install from git/GitHub with --source=github --package=<npm-package-name> when the extension isn't published to npm
Set the APPIUM_HOME environment variable consistently before install and before starting the server if you want extensions stored outside the default ~/.appium
Known gotchas
Appium 1.x's bundled drivers are gone in 2.x — a freshly started server has no drivers at all until you explicitly appium driver install the ones you need
APPIUM_HOME must match between install time and server-start time, or the running server won't see extensions installed under a different value
appium driver update intentionally refuses to cross a major version boundary automatically, so breaking driver upgrades require an explicit reinstall rather than a routine update
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?