Agents write your code. Kifas tests it.
One MCP server, 65 tools, first-class in Claude Code, Cursor, and Windsurf. Your agent drives real browsers, iOS and Android emulators, and a Device Farm of physical devices, and the loop covers your repo on every push.
$10 in credits, no card. Cold starts land in under three seconds.
Real browsers, emulators, and physical devices.
Cloud browsers · Emulators · Device Farm · p50 < 3s cold start
The agent wrote the feature in twenty minutes. Nobody tested it. Code velocity tripled the day you adopted Cursor. Your verification did not get the memo.
Give the agent that wrote it a way to prove it.
Kifas is a testing platform your agent talks to natively, plus a loop that keeps covering the repo when no one is at the keyboard.
65 tools, one server, npx @kifas/mcp@latest. Built around Model Context Protocol from the first call, not bolted on after.
Cloud browsers (Chromium, Firefox), iOS and Android emulators, and a Device Farm of real physical devices. All callable from the same tool surface.
Scan, suggest, build, run, self-heal. Coverage keeps pace with commits even when no human is watching the pipeline.
Save a logged-in session or a seeded workspace as a named handle and reuse it across multi-turn agent runs instead of rebuilding it every time.
And it runs on its own, on every push:
Not a number. A surface.
65 tools, grouped into the families your agent calls. A few from each below; the full reference, with arguments and examples, lives in the docs.
- workflow.create
- workflow.run
- workflow.diff
- workflow.publish
- auth.add
- auth.rotate
- state.save
- state.load
- browser.spawn
- device.spawn
- device.tap
- device.install
- run.read
- run.replay
- run.flake_score
- run.compare
- inbox.create
- inbox.wait_for
- inbox.list
- inbox.purge
- tunnel.start
- tunnel.attach
- tunnel.list
- tunnel.stop
Native, and yours to drive.
Is this a wrapper, or actually MCP-native?
Built MCP-first. The dashboard you see is a UI over the same 65 tools your agent calls. There is no second, lesser API hiding behind the pretty one.
Loop, or standalone?
Either. Every piece runs standalone from your agent, and the autonomous loop is the fast path on top when you want coverage to run itself. Your call on who holds the wheel.
What does an agent run cost?
A credit is about a penny. Cloud browsers run at 2 credits a minute, mobile emulators at 5, and the Device Farm of real devices at 22. AI steps are 1 to 12 credits depending on depth. The free tier's $10 covers real usage, and adding teammates costs nothing.
Priced by what you actually run.
Credits, not seats. Adding teammates costs nothing. You spend when tests run.
- GitHub-connected autonomous loop
- Self-healing with break thresholds
- Auth Catalog · vibe testing · hybrid engine