Odel
MCP server: One MCP server.

Ikenga iyke (control bridge)

@ikengaRun by its publisher: served from their own domain, namespace checked by the registry.MCP server · External

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

Computer controlv0.2.3Apache-2.0TypeScript
Freeno charge per call
How to install

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: moves money, runs code or commands, deletes data, or sends messages for you.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npm@ikenga/mcp-iykev0.2.3

Run

npx -y @ikenga/mcp-iyke

MCP client config

{
  "mcpServers": {
    "ikenga-iyke-control-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "@ikenga/mcp-iyke"
      ]
    }
  }
}
README1 min read

ikenga-pkgs

License Discussions Newsletter

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.

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 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 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.

Similar modules

Browse Computer control