English Français العربية

Ikenga iyke (control bridge)

Official registry Productivity

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

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @ikenga/mcp-iyke
Claude Code 
claude mcp add ikenga-iyke-control-bridge -- npx -y @ikenga/mcp-iyke@0.2.3
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "ikenga-iyke-control-bridge": {
            "command": "npx",
            "args": [
                "-y",
                "@ikenga/mcp-iyke@0.2.3"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. ikenga-pkgs
  2. What it is
  3. Layout
  4. Workflow
  5. Registry
  6. Links
  7. License

ikenga-pkgs

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), 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 for per-package versioning and publish.

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 will nag you on PRs that don't).

Registry

Published versions appear in the 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.

  • ikenga — the desktop shell that loads these
  • ikenga-contract — the manifest schema each pkg validates against
  • Building in the Loop — biweekly letters on running a real multi-agent Claude Code system

License

Apache-2.0 — see LICENSE.

Frequently asked questions

What is Ikenga iyke (control bridge)?

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

How do I install Ikenga iyke (control bridge)?

It runs on your machine. In Claude Code: claude mcp add ikenga-iyke-control-bridge -- npx -y @ikenga/mcp-iyke@0.2.3. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Ikenga iyke (control bridge) need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Ikenga iyke (control bridge) open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains Ikenga iyke (control bridge)?

It is published by ikenga-hq. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.