# Ikenga iyke (control bridge)

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/ikenga-hq/ikenga-pkgs  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ikenga-iyke-control-bridge-2

## Description
Drive a running Ikenga desktop app from MCP clients — DOM, click, type, navigate, screenshot.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "ikenga-iyke-control-bridge": {
    "command": "npx",
    "args": ["-y","ikenga-iyke-control-bridge-2"]
  }
}
```

## Documentation & README

# ikenga-pkgs

[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
[![Discussions](https://img.shields.io/badge/community-discussions-5865F2.svg)](https://github.com/ikenga-hq/ikenga-pkgs/discussions)
[![Newsletter](https://img.shields.io/badge/newsletter-Building%20in%20the%20Loop-e8590c.svg)](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`](https://github.com/ikenga-hq/ikenga-pkgs/blob/HEAD/LICENSE).