Skip to content
plugmcp
DirectorySkillsCategoriesBlog
EN/中文
Sign inSign up
Home/Servers/Ikenga Iyke (control Bridge)

Ikenga Iyke (control Bridge)

I
by io.github.Royalti-io

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

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command
npx -y @ikenga/[email protected]
Provider
Claude Code
claude mcp add io.github.royalti-io-ikenga-pkg-mcp-iyke -- npx -y @ikenga/[email protected]

Run in a terminal.

Claude Desktop
{
  "mcpServers": {
    "io.github.royalti-io-ikenga-pkg-mcp-iyke": {
      "command": "npx",
      "args": [
        "-y",
        "@ikenga/[email protected]"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

View more
  • Firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
  • N
    NotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
  • Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

Related skills

View all
  • reaReverse engineer anything with agents, from app behavior down to native binaries.
  • rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
  • rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

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

[!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.

  • npm (unchanged, still the right package): @ikenga/mcp-iyke
  • Issues and PRs: please open them on ikenga-pkgs

@ikenga/mcp-iyke

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)

npm install -g @ikenga/mcp-iyke
claude 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)

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

From source (for contributors)

git clone https://github.com/Royalti-io/ikenga-pkg-mcp-iyke.git
cd ikenga-pkg-mcp-iyke
npm install
npm 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

  • Ikenga shell — the desktop app this drives.
  • @ikenga/contract — shared manifest + iyke runtime constants.
  • Model Context Protocol — the protocol this server speaks.
How do I install Ikenga Iyke (control Bridge)?
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Ikenga Iyke (control Bridge) need an API key?
No required environment variable is listed on this record.
What transport does Ikenga Iyke (control Bridge) use?
Ikenga Iyke (control Bridge) runs locally over stdio.
When was Ikenga Iyke (control Bridge) last checked?
Last checked 2026-10-16. Drive a running Ikenga desktop app from MCP clients — DOM, click, type, navigate, screenshot.

No tool list yet. Remote servers get one after the first health check.

plugmcp

Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.

  • github.com/TODO
  • x.com/TODO
  • linkedin.com/company/TODO

PlugMCP, 2026

Product
  • Browse
  • Install
  • Host your own
  • Voice mode
  • Browser
Directory
  • All MCP servers
  • Agent skills
  • Categories
  • New
  • Voice
  • Submit a server
Developers
  • Docs
  • Blog
  • What is MCP
  • What is WebMCP
  • Status
Company
  • About
  • Contact
  • Terms
  • Privacy
  • DPA