Ikenga iyke (control bridge)
Drive a running Ikenga desktop app from MCP clients — DOM, click, type, navigate, screenshot.
Open source Open in the app JSON README (API)
About
Drive a running Ikenga desktop app from MCP clients — DOM, click, type, navigate, screenshot.
Details
- Kind
- MCP servers
- Topic
- Web search, scraping & browser
- Publisher
- dev.ikenga
- Origin
- official
- Category
- ferramentas
- Transport
- local
- Version
- 0.2.3
- Open pull requests
- 1
- Last push
- 2026-09-08T10:23:56Z
- Repository state
- ativo
- Language
- TypeScript
- License
- Apache-2.0
- Added
- 2026-08-29 03:01:30
- Updated
- 2026-08-29 03:01:30
- Origin id
dev.ikenga/mcp-iyke
README
# ikenga-pkgs [](LICENSE) [](https://github.com/ikenga-hq/ikenga-pkgs/discussions) [](https://buildingintheloop.substack.com/subscribe) > The canonical home for first-party Ikenga packages — engines, MCP servers, mini-apps, and > helpers — in one Apache-2.0 monorepo. ## What it is Every first-party Ikenga package lives here ([ADR-009](https://github.com/ikenga-hq/ikenga/blob/main/docs/adr/009-monorepo-pkgs-all-open.md)), versioned and published with Changesets. It's a good place to read working examples of each pkg archetype before authoring your own. ## Layout ``` packages/ engine/ AI engine adapters (claude-code, noop, …) mcp/ MCP servers (iyke, …) apps/ User-facing iframe mini-apps (studio, tasks, …) connectors/ External-service adapters sidecars/ Long-lived headless processes ``` ## Workflow This monorepo uses [Changesets](https://github.com/changesets/changesets) for per-package versioning and publish. ```bash pnpm install pnpm -r build pnpm changeset # author a changeset describing your change git commit -am "feat: ..." # Open PR; on merge to main, "Version Packages" PR opens. # Merging that PR publishes all bumped packages to npm and updates the registry index. ``` Each PR that changes a package must include a `.changeset/*.md` (the [changeset-bot](https://github.com/apps/changeset-bot) will nag you on PRs that don't). ## Registry Published versions appear in the [ikenga-registry](https://github.com/ikenga-hq/ikenga-registry) within seconds of `pnpm changeset publish` completing, via the `scripts/update-registry-index.mjs` step in the release workflow. The shell and `ikenga` CLI both consume that registry for discovery and install. ## Links - [`ikenga`](https://github.com/ikenga-hq/ikenga) — the desktop shell that loads these - [`ikenga-contract`](https://github.com/ikenga-hq/ikenga-contract) — the manifest schema each pkg validates against - [Building in the Loop](https://buildingintheloop.substack.com/subscribe) — biweekly letters on running a real multi-agent Claude Code system ## License Apache-2.0 — see [`LICENSE`](LICENSE).