Ikenga iyke (control bridge)

io.github.Royalti-io由 GitHub 帳號 Royalti-io 發布v0.1.2更新於 Oct 27, 2026

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

已驗證STDIO僅桌面效率與工作流瀏覽器自動化開發者工具

概覽

AI 產生的概覽

把執行中的 Ikenga 桌面應用接入 MCP：讓助理切換面板、點擊、輸入、檢視 DOM、日誌與網路並截圖。

可以做什麼
  • 檢視並調整介面配置：讀取側邊欄模式與面板樹、切換路由、切換模式、開啟分頁、分割、聚焦與關閉面板。
  • 操作即時介面：取得無障礙樹 DOM 快照，依 ref、選擇器或文字點擊，輸入文字、送出快速鍵、等待條件成立、截圖。
  • 讀取執行期診斷：最近的 console 與錯誤日誌、fetch/XHR 網路紀錄、TanStack Query 快取，偵錯版可開啟 DevTools。
  • 處理 iframe 面板：讀取其發布的狀態物件，並送出即發即忘的 postMessage。
  • 管理專案：建立、更新、列出、封存專案，以及設定與讀取目前使用中的專案。
適用情境
適合讓助理直接操作或偵錯 Ikenga 桌面應用本身，例如重現介面流程、查看面板呈現結果、讀取日誌與網路活動、切換專案，而不是處理無關的程式碼工作。
執行需求
透過 npx 或全域 npm 安裝後在本機執行，需要 Node.js 20 以上版本。Ikenga 桌面應用必須正在執行並提供本機控制服務；伺服器會從應用程式本機資料目錄的 control.json 讀取連接埠、bearer 權杖與 PID。未宣告任何環境變數或請求標頭。
安裝前請注意
工具會直接作用於執行中的應用：點擊、輸入、送出按鍵、切換路由、分割與關閉面板，以及建立、更新、封存或切換專案，變更都是真實的。control.json 中的 bearer 權杖等同應用控制權，不應外流。伺服器只連線 127.0.0.1，並聲明沒有對外網路與遙測。原始碼儲存庫已封存，應從 npm 安裝而非複製後建置。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Ikenga iyke (control bridge)，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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

來源：README.md，提交 9be6167

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

1
  1. v0.1.2最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分