Appium MCP (official)
Capped at 70: no passing tool call yet; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested npm package 1.99.0 (server reports itself as 1.87.4 in the handshake)
Transport (tested 2026-10-26): stdio
Score 70/100 · Tools 31 · Token cost ~10,027 · Compare · Last tested 2026-10-26 · Version tested 1.99.0 · Package appium-mcp · Repo appium/appium-mcp
Summary: Appium MCP (official) completed an MCP handshake without credentials and exposed 31 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 31
- Context cost
- 10,027 model-visible tokens (name, description, inputSchema; tiktoken cl100k_base)
Extra payload (sent by the server, usually not read by the model): 379 tokens; raw tools/list total 10,406. Clients differ in what they forward. ranking · add up your servers' context cost - API key
- No key to connect (handshake passed)
- Tested
- 2026-10-26
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install appium-mcp (Node 20, Linux) succeeded in 21s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 31 tools listed in 2.5s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 509 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Automated check of the package's own README (README shipped in npm package). |
| license | pass | 10 | Apache-2.0 (OSI-approved). |
Local-model readiness
Schema context cost: ~10,027 tokens for 31 tools (44,492 bytes) · about 122% of an 8k context. Method: tiktoken cl100k_base over compact JSON of name+description+inputSchema (approximate).
Small-model friendly (schema heuristic, not a model result): unknown.
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-10-26
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 31 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Tool-schema token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that it is safe to give it access to your data.
Known security issues
Checked on 2026-10-27 for version 1.99.0 against OSV, GitHub advisories, GitHub repository advisories. Scope: the package itself; dependencies not scanned.
No published advisories found in OSV and GitHub advisories whose affected range includes appium-mcp 1.99.0 as of 2026-10-27. This is not a security audit.
Other advisories we checked (3)
- Tested version 1.99.0 is not in the affected range of GHSA-x975-rgx4-5fh4.
- Tested version 1.99.0 is not in the affected range of GHSA-pchr-rp2x-w3vw.
- Tested version 1.99.0 is not in the affected range of GHSA-3cp6-m69f-v2cj.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-10-26 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
bc3ed8f0c04d: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "appium-mcp",
"version": "1.99.0",
"registry": "npm",
"status": "working",
"tested": "2026-10-26",
"tools_count": 31,
"tools_schema_tokens_est": 10027,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install appium-mcp` (Node 20, Linux) succeeded in 21s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 31 tools listed in 2.5s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 509 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Automated check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"Apache-2.0 (OSI-approved)."
]
}
}Install
npx -y appium-mcp
Tools listed
select_device, appium_session_management, appium_mobile_device_control, appium_geolocation, appium_mobile_device_info, appium_mobile_file, appium_driver_settings, prepare_ios_simulator, appium_prepare_ios_real_device, appium_gesture, appium_drag_and_drop, appium_perform_actions, appium_find_element, appium_mobile_press_key, appium_set_value, appium_mobile_keyboard, appium_get_text, appium_get_element_attribute, appium_mobile_clipboard, appium_get_active_element, appium_get_page_source, appium_orientation, appium_alert, appium_screenshot, appium_get_window_size, appium_screen_recording, appium_app_lifecycle, appium_mobile_permissions, appium_context, generate_locators, appium_generate_tests
Quick config
{
"mcpServers": {
"appium-mcp-official": {
"command": "npx",
"args": [
"-y",
"appium-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install appium-mcp(Node 20). This is the exact command we ran on 2026-10-26. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (31 in our test).
{
"mcpServers": {
"appium-mcp-official": {
"command": "npx",
"args": [
"-y",
"appium-mcp"
]
}
}
}Test history
No dated events yet.
FAQ
Is Appium MCP (official) deprecated?
No. appium-mcp was not deprecated or archived when we last tested it on 2026-10-26.
What replaces Appium MCP (official)?
Nothing; Appium MCP (official) is not deprecated as of 2026-10-26.
Does Appium MCP (official) need an API key?
No. It completed an MCP handshake with no credentials and listed 31 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.