Ikenga iyke (control bridge)

dev.ikengaPublished by ikenga.devv0.2.3Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyBrowser Automation Developer Tools

Server details

Identifier: dev.ikenga/mcp-iyke
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to ikenga.dev. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/dev.ikenga%2Fmcp-iyke.svg)](https://sourceweft.com/mcp/dev.ikenga%2Fmcp-iyke?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local stdio MCP bridge that lets an assistant drive a running Ikenga desktop app through DOM inspection, clicks, typing, navigation and screenshots.

What you can do: Inspect the DOM of the running Ikenga desktop app to see page structure and elements. Click elements and type text into the app's interface. Navigate the app to different views or pages. Capture screenshots of the app for visual confirmation.
When to use it: Useful when you want an assistant to operate or test the Ikenga desktop app directly — walking through UI flows, filling in fields, or verifying what the app displays — rather than working through files or APIs.
Requirements: Runs as a local process on the user's machine via npx from the npm package @ikenga/mcp-iyke over stdio. Requires the Ikenga desktop app to be running and reachable; desktop only, not available as a web executable. No authentication, environment variables or headers are declared.

Before you install

It controls a live desktop application: clicks, typing and navigation change the app's state and may trigger real actions in it. Screenshots capture whatever the app displays, which may include private data. Review what the assistant is asked to do before granting control.

Installation

In SourceWeft

Open Ikenga iyke (control bridge) in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

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 installpnpm -r buildpnpm changeset            # author a changeset describing your changegit 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.

pnpm installpnpm -r buildpnpm changeset            # author a changeset describing your changegit 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.

License

Apache-2.0 — see LICENSE.

Source: README.md at commit dab3dec

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.2.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts