Ikenga iyke (control bridge)

What Ikenga iyke (control bridge) does

Ikenga iyke (control bridge) connects MCP clients to a running Ikenga desktop app and exposes desktop-control actions through MCP. The documented interaction surface covers DOM work, mouse-style clicking, text entry, navigation, and screenshots.

This makes the server relevant to agents that need to operate an Ikenga session as part of a workflow. It is not described as a general-purpose browser automation server, a remote desktop service, or an adapter for external SaaS systems. Its stated target is the Ikenga desktop application.

How it works

The bridge is used alongside an active Ikenga desktop app. An MCP client sends requests to the server, and the server drives the running application using the supported interaction capabilities. The available description does not define individual MCP tool names, request schemas, response formats, authentication behavior, or whether the connection uses standard input/output or HTTP.

The repository places the package in the packages/mcp/ area of the ikenga-pkgs monorepo. That repository is the first-party home for Ikenga packages, including MCP servers, and uses per-package versioning and publishing through Changesets.

Setup and configuration

The repository-level workflow starts with installing dependencies and building the monorepo:

pnpm install
pnpm -r build

These commands are documented for the monorepo as a whole, not as a complete, package-specific launch procedure for Ikenga iyke (control bridge). The provided material does not include an MCP client configuration block, an npm package name, a server start command, required environment variables, or instructions for connecting to a running desktop instance.

Published package versions are added to the Ikenga registry after the repository’s release process completes. The Ikenga shell and ikenga CLI use that registry for discovery and installation, but the excerpt does not describe the exact installation steps for this bridge.

Tools and capabilities

The documented capabilities are:

• Work with the Ikenga app DOM.
• Click within the running desktop app.
• Type into the app.
• Navigate through the app.
• Capture screenshots.

These capabilities are described at a high level. The source material does not identify separate tool names, parameters, return values, selectors, screenshot formats, or navigation targets. Implementations should therefore consult the package documentation or source before building a client integration around a specific schema.

Limitations and notes

Ikenga iyke (control bridge) requires a running Ikenga desktop app according to the listing description. The excerpt does not state whether the bridge can launch the app, reconnect to it, manage multiple app instances, or work with applications other than Ikenga.

No client compatibility list is provided. Likewise, the material does not document environment variables, authentication, permissions, platform support, performance characteristics, or error handling. The repository is licensed under Apache-2.0, and the package is maintained within the ikenga-pkgs monorepo.