
AutoGenesis Appium
io.github.FSQ-labPublished by GitHub account FSQ-labv0.4.0Updated Oct 29, 2026
BDD automation runtime for iOS, Android, and macOS through Appium.
Overview
Local stdio MCP runtime for BDD-style UI automation on iOS, Android and macOS through Appium.
- What you can do
- Run BDD automation flows against iOS, Android and macOS apps through Appium.
- Launch the runtime for a chosen platform with an explicit config file and business-project root.
- Generate automation code, with confirmation tied to an exact preview identity and digest plus explicit approval.
- No individual tools are listed in the manifest, so capabilities are known only from the description and README.
- When to use it
- Useful when you want an assistant to drive or generate BDD-style Appium tests for mobile and macOS apps inside an existing business project, rather than writing the automation by hand.
- Requirements
- Runs as a local process, installed from the PyPI package autogenesis-appium-mcp and started with uvx. Needs the pinned dependency autogenesis-agent-contract==2.1.0, an Appium setup for the target platform, and absolute paths for a config file and project root passed on launch. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open AutoGenesis Appium in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
AutoGenesis Appium MCP
Installable stdio MCP runtime for BDD automation on iOS, Android, and macOS through Appium.
The runtime requires autogenesis-agent-contract==2.1.0. Launch it with an explicit configuration and business-project root:
Canonical Registry metadata is in server.json. Generated-code confirmation requires the exact preview identity and digest plus explicit approval.
Source: appium-mcp-server/README.md at commit 2f96dc4
Tools
0Version history
1- v0.4.0LatestOct 29, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.