What it does
Self-healing Appium locators for Android and iOS apps, healed on the screen each test failed on.
- Connects Runs on your computer
- Account or key No key needed
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install k11 Appium QA. Follow https://mcp.popnx.com/i/k11-software-solutions-appium-qa.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 17, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Let AI install it
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server k11 Appium QA for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "appium-qa": { "command": "uvx", "args": [ "k11-appium-qa-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the k11 Appium QA tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Paste these settings and save the file
{ "mcpServers": { "appium-qa": { "command": "uvx", "args": [ "k11-appium-qa-mcp" ] } } }Quit Claude and open it again
Try it
Use k11 Appium QA and tell me what you can do for me, then show me one thing✓ If Claude says it is using k11 Appium QA or shows a k11 Appium QA tool in the answer, you are connected
1 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
QA_MCP_ROOTFolder with your Appium tests and .qa-mcp/
Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect k11 Appium QA yet
k11 Appium QA runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect k11 Appium QA
- Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
- Install Python (uv) on your computer first (one time)
- Install Python (uv) on your computer first (one time)
- Install Python (uv) on your computer first (one time)
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server k11 Appium QA for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user appium-qa -- uvx k11-appium-qa-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the k11 Appium QA tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Paste this command and press Enter
claude mcp add --scope user appium-qa -- uvx k11-appium-qa-mcpType /mcp in Claude Code
You should see k11 Appium QA listed as connected
Try it
Use k11 Appium QA and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using k11 Appium QA or shows a k11 Appium QA tool in the answer, you are connected
1 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
QA_MCP_ROOTFolder with your Appium tests and .qa-mcp/
Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server k11 Appium QA for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "appium-qa": { "command": "uvx", "args": [ "k11-appium-qa-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the k11 Appium QA tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open the AI chat in Cursor in Agent mode
Try it
Use k11 Appium QA and tell me what you can do for me, then show me one thing✓ If Cursor says it is using k11 Appium QA or shows a k11 Appium QA tool in the answer, you are connected
1 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
QA_MCP_ROOTFolder with your Appium tests and .qa-mcp/
Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Python (uv) on your computer first (one time)
Let AI install it
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server k11 Appium QA for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "appium-qa": { "type": "stdio", "command": "uvx", "args": [ "k11-appium-qa-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the k11 Appium QA tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Install uv (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
uv --version- A version number such as uv … = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number:
uv --versionInstall once; it works for everything that needs uv
Open the AI chat in VS Code in Agent mode
Try it
Use k11 Appium QA and tell me what you can do for me, then show me one thing✓ If VS Code says it is using k11 Appium QA or shows a k11 Appium QA tool in the answer, you are connected
1 optional setting(s) (works without them)
The command above works without these. Add them only if you want to change something, following the maker’s description.
QA_MCP_ROOTFolder with your Appium tests and .qa-mcp/
Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
For developers: Terminal commands and JSON settings
Installed on your computer
Claude Code
claude mcp add --scope user appium-qa -- uvx k11-appium-qa-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"appium-qa": {
"command": "uvx",
"args": [
"k11-appium-qa-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"appium-qa": {
"command": "uvx",
"args": [
"k11-appium-qa-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"appium-qa": {
"type": "stdio",
"command": "uvx",
"args": [
"k11-appium-qa-mcp"
]
}
}
}Values you fill in
QA_MCP_ROOTenvFolder with your Appium tests and .qa-mcp/
Descriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
- Downloads per weeki
- Not on npm/PyPI
- Connection
- Runs on your computer
- Latest versioni
- 0.1.0
- Categoryi
- Developer tools
- Published to registryi
- Nov 17, 2026
- Code last changedi
- Nov 17, 2026
- Maker
- K11-Software-Solutions
- Packages
pypi: k11-appium-qa-mcp- Website
- github.com
- Registry status
- Active
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account K11-Software-Solutions, which owns the repo
- ✓ Pass
Still maintained
Code last changed 2 days ago
- ✓ Pass
Has a licence
Uses MIT
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
No entries on OSV.dev for k11-appium-qa-mcp@0.1.0
Checks only this package version, not every dependency · checked Nov 17, 2026
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/k11-software-solutions-appium-qa)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 0% of the other 6116 servers in this category
- Published to the registry more recently than 93% of the other 6116 servers in this category
- Basic checks equal to or better than 99% of the other 6116 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is k11 Appium QA safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed 2 days ago, and the latest version (0.1.0) reached the registry 2 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one k11 Appium QA | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
k11 Appium QA: self-healing locators for mobile apps
When an app redesign breaks your Appium tests, fix the locators with evidence, not guesses.
Self-healing for mobile tests usually lives inside a paid device cloud, as a black box. k11 Appium QA is open source and runs wherever your tests already run: a laptop with an emulator, your CI, or any device cloud.
- Heals on the exact screen the test failed on. A small pytest plugin saves the screen (Appium's page source) at the moment an element isn't found. Healing runs against that screen, with no need to navigate back to it.
- Shows its working: confidence, the reasons ("text equivalent: Log in → Sign in", "resource id similar 62%"), the runner-up and alternatives. Accessibility ids are preferred.
- Fixes locators where they live: Python
AppiumBy/Bytuples and Page Object constants; JavaAppiumBy/MobileBy/Bycalls and@AndroidFindBy/@iOSXCUITFindByannotations (each keeps its own platform). - Verified, not hoped:
heal-cire-runs the healed tests on the device and reverts any change that doesn't pass. When a test gets further and breaks on the next locator, it heals that one too. - Android and iOS: UiAutomator2 and XCUITest screens; accessibility id, id, class name, XPath, UiSelector and iOS predicate locators are evaluated offline.
- Accessibility check: tappable elements a screen reader can't name, and duplicate accessibility ids. Bad for users, and the reason tests are fragile.
See it heal
A login screen redesign broke three locators in one test and one in another. k11-appium-qa-mcp heal-ci --apply:
3 healed and verified, 1 needs review, 1 failure not caused by locators.
| Test | Old locator | New locator | Confidence | Re-run |
|---|---|---|---|---|
| test_log_in |
(AppiumBy.ID, "et_email")|(AppiumBy.ACCESSIBILITY_ID, "email-field")| 94% | passed |
| test_log_in |
(AppiumBy.ACCESSIBILITY_ID, "password-input")|(AppiumBy.ACCESSIBILITY_ID, "password-field")| 100% | passed |
| test_log_in |
(AppiumBy.ACCESSIBILITY_ID, "login-button")|(AppiumBy.ACCESSIBILITY_ID, "sign-in-button")| 77% | passed |
*Why "sign-in-button"?* accessibility id similar (62%) · resource id similar:
btn_login→btn_sign_in· text equivalent: "Log in" → "Sign in" · class matches.
Needs a person: the sign-up button lost its accessibility id; best guess
btn_registerat 42%, so it was not changed.
Not caused by locators: the title changed from "Welcome back". Untouched; it may be a real change.
The changes land in the Page Object (tests/pages/login_page.py), not scattered across tests.
Tools (MCP)
Every tool works on a saved screen (page source XML, e.g. the one saved when a test failed) or on the live device when .qa-mcp/appium.yaml points at an Appium server.
| Tool | What it does |
|---|---|
inspect_screen | Elements with locators verified to match exactly one element, most stable first |
check_locator | How many elements a locator matches (1 = good) and whether it's visible |
capture_baseline | While tests pass, records each locator's element (per platform) so healing is confident later |
heal_locator | Finds the intended element and suggests a verified replacement, in Python or Java form |
accessibility_check | Unnamed tappable elements and duplicate accessibility ids |
save_screen | Saves the live device's screen for later, device-free work |
run_tests | Runs the pytest suite; failures include the locator, line, platform and saved screen |
Command: `/heal-mobile-tests`, a guided workflow from failing tests to healed, verified locators.
k11 Appium QA doesn't try to replace device-control servers like the official Appium MCP or mobile-mcp; use them to drive and explore the app, and this to keep your existing test suite healthy.
Install
pip install "k11-appium-qa-mcp[live]" # [live] adds the Appium client for live sessions; saved screens need nothing extra
Claude Code plugin:
/plugin marketplace add K11-Software-Solutions/k11techlab-appium-qa-mcp
/plugin install appium-qa@k11-appium-qa
Any MCP client:
{ "mcpServers": { "appium-qa": { "command": "uvx", "args": ["k11-appium-qa-mcp"] } } }
For live sessions, copy docs/appium.example.yaml to .qa-mcp/appium.yaml (server URL and capabilities; secrets as ${ENV:NAME}). Device clouds such as BrowserStack and Sauce Labs work the same way.
Healing in CI
k11-appium-qa-mcp heal-ci # dry run: suggestions only
k11-appium-qa-mcp heal-ci --apply # apply confident changes, verify on the device, revert what fails
- Runs your pytest suite with the plugin, which saves the screen of every test that fails on a missing element.
- Heals each broken locator against that screen and the committed baseline (
.qa-mcp/appium-baselines.json). - Applies a change only at 70% confidence or more (
--min-confidence), clearly ahead of the runner-up. Tests that share a broken locator are healed together, with one change. - Re-runs the healed tests on the device; a test that now breaks on another locator gets that one healed too (up to five rounds). Every change is kept only if all the tests using it pass.
- Leaves failures that aren't about locators alone, and writes
heal-report.md(for the pull request) andheal-report.json.
docs/heal-mobile-locators.yml runs it on an Android emulator in GitHub Actions and opens a pull request. The report uses the same format as k11 Playwright QA and Selenium QA, so the k11 Release Gate reads it as UI evidence.
Java projects: the MCP tools and source rewriting support Java (Page Objects with @AndroidFindBy/@iOSXCUITFindBy, AppiumBy calls). heal-ci currently runs pytest suites; for Maven or Gradle suites, save the screen on failure (driver.getPageSource()) and use heal_locator, or /heal-mobile-tests.
How it's tested
- No device needed for most tests: real-format UiAutomator2 and XCUITest page sources, and a fake Appium driver that serves them, run the whole heal-ci loop (run, heal, rewrite, re-run, report) in seconds.
- A real emulator on every push:
e2e-android.ymlstarts an Android 14 emulator and an Appium server, reads the built-in Settings app live, captures a baseline and heals a broken locator, both live and from the saved screen.
Safety
- Suggestions are never applied silently:
heal_locatornever edits files, andheal-cichanges code only above the threshold and keeps a change only when the tests pass. - Screens are parsed with entity expansion and network access disabled; paths must stay inside the project.
- Locators from tests and models are parsed, never executed.
- Capabilities and credentials come from
.qa-mcp/appium.yamlwith${ENV:NAME}secrets.
Part of the K11 QA suite
Playwright QA · Selenium QA · Appium QA · API Contract QA · API Functional QA · Performance QA · LLM Assure · Release Gate · Release Readiness Agent
Roadmap
heal-cifor Java (Maven/Gradle) suites, with a TestNG/JUnit listener that saves the screen on failure- iOS simulator job in CI (macOS runner)
- Screenshot similarity as an extra healing signal
- Flutter and React Native specifics (semantics labels, testID)
Built by K11 Software Solutions. MIT licensed.