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、选择器或文本点击，输入文字、发送快捷键、等待条件满足、截图。
  • 读取运行时诊断：最近的控制台与错误日志、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 分