Swipium supports all models available through the connected MCP client.
The same local QA server can be used from Claude Code, Codex, Gemini CLI,
Cursor, VS Code, Grok, Grok Build, and other MCP-compatible agent workflows.
Claude Desktop and Windsurf work with a manual configuration.
Claude Code
Use Claude Code with Fable 5.1, Opus 5.5, Sonnet 5.5, and any model available in the client. Register Swipium at project scope to keep QA execution local, or install the Claude Code plugin with /plugin marketplace add GeroPalombo/swipium and /plugin install swipium@swipium.
npm install -g swipium
swipium init claude \
--scope project --apply
Gemini CLI
Expose simulator setup, smoke checks, reports, and artifacts as structured MCP tools for Gemini CLI workflows.
npm install -g swipium
swipium init gemini --apply
Codex
Use Codex with GPT-6.1 Sol and any model available in the client. Run swipium init codex so Codex passes test credentials and the Android SDK path to Swipium, and let the agent drive repeatable mobile QA from the project root.
npm install -g swipium
swipium init codex --apply
Cursor and VS Code
Register Swipium in the editor you already use. Project-scoped setup writes a portable config the team can commit.
npx -y swipium init cursor \
--apply
npx -y swipium init vscode \
--apply
Grok and Grok Build
Use Grok, Grok Build, or MCP-compatible bridges to route simulator QA tasks into the same local Swipium server.
npx -y swipium verify
npx -y swipium