Ikenga Iyke (Control Bridge)
Let Claude Code or Cursor drive a live Ikenga desktop app for UI automation, DOM inspection, and screenshots without writing a separate test harness.
Overview
Ikenga iyke is a MCP server for the Build phase that drives a running Ikenga desktop app via DOM, input, navigation, and screenshot tools.
What is this MCP server?
- stdio npm package @ikenga/mcp-iyke v0.1.2, run via npx
- DOM introspection plus click, type, and navigate against a running Ikenga app
- Screenshot capture for visual regression and agent verification
- Requires a locally running Ikenga desktop instance to attach the bridge
- Server version 0.1.2 on npm as @ikenga/mcp-iyke
- Transport: stdio
- 4 capability areas: DOM, click, type, navigate, screenshot
What problem does it solve?
Agents cannot safely operate proprietary desktop UIs without a dedicated bridge that exposes structured control instead of brittle OS-level macros.
Who is it for?
Indie builders already using Ikenga who want MCP-driven UI automation from their coding agent.
Skip if: Teams that only need public web scraping or headless Chrome without the Ikenga desktop runtime.
What do I get? / Deliverables
Your agent can exercise Ikenga screens programmatically and return DOM and visual artifacts you can fold into test or demo scripts.
- Programmatic clicks, typing, and navigation inside Ikenga
- DOM snapshots and screenshots returned to the agent thread
Recommended MCP Servers
Journey fit
How it compares
Desktop Ikenga control bridge, not a generic Playwright or browser-only MCP skill.
Common Questions / FAQ
Who is Ikenga iyke for?
Solo and small-team developers running Ikenga desktop apps who want Claude Code, Cursor, or Codex to click, type, and screenshot inside that app.
When should I use Ikenga iyke?
Use it during build or ship when you need agent-driven UI checks, navigation proofs, or screenshots against a live Ikenga instance.
How do I add Ikenga iyke to my agent?
Add an MCP stdio entry that runs npx @ikenga/mcp-iyke, ensure Ikenga is running locally, then reload your agent MCP config.