Ikenga iyke (control bridge)
Drive a running Ikenga desktop app from MCP clients — DOM, click, type, navigate, screenshot.
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.
Links
ikenga— the desktop shell that loads theseikenga-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.
Installation
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @ikenga/mcp-iykeSet up in your AI client
Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"dev-ikenga-mcp-iyke": {
"command": "npx",
"args": [
"-y",
"@ikenga/mcp-iyke"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencePackage
Compatible MCP Clients
Ikenga iyke (control bridge) works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
- Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect. - Cursor
~/.cursor/mcp.jsonRestart Cursor for changes to take effect. - VS Code
.vscode/mcp.jsonReload VS Code window for changes to take effect. - Windsurf
~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect. - Claude Code
.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.