mcpField
I
Ikenga iyke (control bridge)

Ikenga iyke (control bridge)

Local
github.comBrowser Automation0Updated today
RepositoryVisit website

About Ikenga iyke (control bridge)

Ikenga iyke is an MCP server package for controlling a running Ikenga desktop app. Its README identifies it as part of the Ikenga package monorepo but does not describe the server's available controls.

Key features

  1. 01Package in the Ikenga monorepo

MCP support

It is an MCP server intended to let MCP clients drive a running Ikenga desktop app. The tagline lists DOM access, clicking, typing, navigation, and screenshots.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "dev-ikenga-mcp-iyke": {
      "command": "npx",
      "args": [
        "-y",
        "@ikenga/mcp-iyke"
      ]
    }
  }
}
Run commandnpx -y @ikenga/mcp-iyke

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@ikenga/mcp-iyke0.2.3

Tools

76

Saved tool list · updated 2w ago

This tool takes no parameters.

Details

From the project README

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.

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.