Ikenga iyke (control bridge)

io.github.Royalti-ioPublished by GitHub account Royalti-iov0.1.2Updated Oct 27, 2026

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

VerifiedSTDIODesktop onlyProductivity & WorkflowBrowser AutomationDeveloper Tools

Overview

AI-generated overview

MCP bridge that lets an assistant drive a running Ikenga desktop app: navigate panes, click, type, inspect DOM, logs and network, and take screenshots.

What you can do
  • Inspect and change the app layout: read sidebar mode and pane tree, navigate routes, switch modes, open tabs, split, focus and close panes.
  • Drive the live UI: accessibility-tree DOM snapshots, clicking by ref, selector or text, typing, keyboard shortcuts, waiting on predicates, screenshots.
  • Read runtime diagnostics: recent console and error logs, fetch/XHR network entries, TanStack Query cache, and open DevTools in debug builds.
  • Work with iframe panes: read their published state and send fire-and-forget postMessage.
  • Manage projects: create, update, list, archive, set and read the active project.
When to use it
Useful when you want an agent to operate or debug the Ikenga desktop app itself — reproducing UI flows, checking what a pane renders, reading logs and network activity, or switching projects — rather than working on unrelated code.
Requirements
Runs locally via npx or a global npm install; Node.js 20 or newer. The Ikenga desktop app must be running and expose its localhost control server; the server reads port, bearer token and PID from the app's control.json in the platform app-local-data directory. No environment variables or headers are declared.
Before you install
Tools act on a live app: they click, type, send keys, navigate, split and close panes, and create, update, archive or switch projects, so changes are real. The bearer token in control.json grants control of the app and should not be shared. The server only talks to 127.0.0.1 and claims no outbound network or telemetry. The source repository is archived; install from npm, not from a clone.

Installation

In SourceWeft

  1. Open Ikenga iyke (control bridge) in the dashboard and add it to a workspace.
  2. 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

[!IMPORTANT]

This repository has moved — do not build from it

Development of @ikenga/mcp-iyke continues in the ikenga-pkgs monorepo:

→ Royalti-io/ikenga-pkgs/packages/mcp/iyke

This repo was last updated on 15 May 2026 and is now archived and read-only.

Why this matters if you cloned it. The state left here is neither the last release nor the current one: its package.json declares 0.1.2, but its source carries a partially-migrated tool set from the period before the code moved back into the monorepo. Building from this tree gives you something that was never published. Anything you install from npm is unaffected.

@ikenga/mcp-iyke

[npm] [License]

A Model Context Protocol server that exposes the Ikenga desktop app's iyke control bridge — so any MCP client (Claude Code, Cursor, custom agents) can drive a running Ikenga session the same way a developer types into the iyke CLI at a shell.

What this is

Ikenga is a Tauri-based AI workspace shell with a manifest-driven package kernel. While the app is running, it exposes a localhost HTTP server (with a bearer token in control.json) that lets external tools introspect and drive the live UI: switch panes, navigate routes, take DOM snapshots, click elements, read logs, capture screenshots.

This package wraps that HTTP server in MCP so an LLM agent can use it natively. Tools mirror the iyke CLI subcommands.

Install

Via Claude Code (recommended)

bash
npm install -g @ikenga/mcp-iykeclaude mcp add iyke -s user -- iyke-mcp

After that, any Claude Code session can call iyke_state, iyke_go, iyke_mode, iyke_open, iyke_split, iyke_focus, iyke_close, plus the runtime-inspection tools (iyke_dom, iyke_logs, iyke_network, iyke_screenshot, iyke_wait, iyke_click, iyke_type, iyke_key, iyke_query_cache, iyke_devtools), iframe tools (iyke_iframe_state, iyke_iframe_send) and project tools (iyke_project_create, iyke_project_update, iyke_project_list, iyke_project_archive, iyke_project_set_active, iyke_project_get_active).

Via npx (no install)

bash
claude mcp add iyke -s user -- npx -y @ikenga/mcp-iyke

From source (for contributors)

bash
git clone https://github.com/Royalti-io/ikenga-pkg-mcp-iyke.gitcd ikenga-pkg-mcp-iykenpm installnpm run build

Then point your MCP client at node /path/to/ikenga-pkg-mcp-iyke/dist/index.js.

Tools

Layout & navigation

ToolPurpose
iyke_stateShow current sidebar mode + focused pane's route + full pane tree.
iyke_goNavigate the focused pane to a route path.
iyke_modeSwitch sidebar activity mode.
iyke_openOpen a new tab in the focused pane (route, terminal, chat, artifact, mini-app).
iyke_splitSplit a pane horizontally or vertically.
iyke_focusFocus a pane by id or 1-based DFS leaf index (⌃1..⌃6).
iyke_closeClose a pane (focused if pane_id omitted).

Runtime inspection & driving

ToolPurpose
iyke_domAccessibility-tree snapshot of the focused pane (Playwright-style refs).
iyke_logsLast 500 console + error logs from the running webview.
iyke_networkLast 100 fetch/XHR network entries with status + duration.
iyke_screenshotPNG screenshot of the window or a specific pane.
iyke_waitWait until a predicate is satisfied (text/selector/ref/gone).
iyke_clickClick an element by ref, selector, or text.
iyke_typeType into an input/textarea/contenteditable.
iyke_keyDispatch a keyboard combo (e.g. Ctrl+S, Meta+K).
iyke_query_cacheDump the TanStack Query cache for the focused pane.
iyke_devtoolsOpen Chrome DevTools (debug builds only).

Iframe runtime state

ToolPurpose
iyke_iframe_stateRead the latest published state object for an iframe pane.
iyke_iframe_sendSend a fire-and-forget postMessage to an iframe pane.

Projects

ToolPurpose
iyke_project_createCreate a project (slug + display name; optional root_path, icon, color, description).
iyke_project_updatePatch fields on an existing project (display_name, root_path, icon, color, description, position).
iyke_project_listList projects in switcher order; pass include_archived=true to surface archived ones.
iyke_project_archiveSoft-delete a project; refuses to archive the built-in Default project.
iyke_project_set_activeSwitch the shell's active project; refetches project-scoped queries.
iyke_project_get_activeReturn the currently active project.

Trust boundary

The MCP server reads control.json from the platform-specific app-local-data directory (~/Library/Application Support/app.ikenga/control.json on macOS, $XDG_DATA_HOME/app.ikenga/control.json on Linux, %APPDATA%/app.ikenga/control.json on Windows). The control file contains:

  • port — localhost port the in-app HTTP server is listening on
  • token — bearer token required on every request
  • pid — owning process PID (used to detect stale files)

A stale control.json left behind by kill -9 is auto-deleted once it's at least 5 minutes old; younger stale files are reported (likely a launch race) so we don't clobber a starting app.

If the Ikenga desktop app isn't running, every tool call fails with a structured error rather than hanging — your agent reads the failure and reports it instead of silently waiting.

The MCP server only ever talks to 127.0.0.1 on the port from control.json, with the bearer token from the same file. No outbound network, no telemetry.

Compatibility

  • Ikenga shell: any version exposing the v1 control.json schema.
  • Node.js: ≥ 20.
  • Bun: runs without compilation (bun src/index.ts).
  • MCP SDK: @modelcontextprotocol/sdk ^1.23.0.

Versioning

This package follows SemVer 2.0.0. Major-version bumps may break MCP tool names or argument shapes; minor bumps add new tools or non-breaking improvements; patches fix bugs.

The iyke HTTP protocol version (the in-app server's API surface) is independent — it's pinned via schema_version: 1 in control.json. This package currently supports protocol v1 only.

Contributing

Contributions welcome. See CONTRIBUTING.md for setup, conventions, and the DCO. By contributing, you agree your contributions are licensed under Apache 2.0 (matching the repo).

For bugs or feature requests, open an issue. For security issues, see SECURITY.md — please don't open a public issue.

License

Apache License 2.0 — Copyright (c) 2026 Royalti, Inc.

Related

Source: README.md at commit 9be6167

Tools

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

Version history

1
  1. v0.1.2LatestSep 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