@ikenga/mcp-iyke
This MCP server provides full programmatic control over a running Ikenga desktop app session, enabling agents to automate UI interactions, inspect runtime state, manage projects/sessions/packages, and leverage scoped storage and coordination tools.
UI Automation & Navigation: switch sidebar modes, navigate/focus/split/close panes, open new tabs (route, terminal, chat, artifact, mini-app), and inspect the pane tree.
Runtime Inspection & Driving: capture accessibility snapshots, read console/network logs, take screenshots, wait for UI conditions, perform clicks/typing/keyboard strokes, dump query caches, and open DevTools (debug builds).
Iframe Control: read published state from iframe panes and send postMessage actions.
Project Management: create, update, list, archive, and set/get the active project.
Chat Sessions: list, move, and start Claude chat threads per project.
MCP & Package Management: list/restart MCP servers, check package trust status and violations, install/change scope/uninstall packages.
Secrets Vault: securely read, write, delete, and list secrets per scope.
Scratchpads: create, append, read, list, and delete project-scoped Markdown notes.
Key-Value Store: store, retrieve, delete, and list small JSON values.
Distributed Locks: acquire, check status, release, and renew project-scoped lease locks for resource coordination.
Todos: create, update, list, and complete project-scoped todos with tags, assignees, and blockers.
Timers: schedule one-shot timers with OS notifications and agent inbox delivery, cancel, and list them.
Agent Registration: register an agent for lock attribution and inbox messages.
Layout Management: get and reset saved per-project layout state.
Claude Asset Management: list, pin, and unpin Claude-config assets (skills, agents, commands, hooks, MCPs) to resolve conflicts across sources.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@ikenga/mcp-iykelist my projects"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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-iykeIssues 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.
Related MCP server: KiCad MCP Server
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-mcpAfter 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-iykeFrom source (for contributors)
git clone https://github.com/Royalti-io/ikenga-pkg-mcp-iyke.git
cd ikenga-pkg-mcp-iyke
npm install
npm run buildThen point your MCP client at node /path/to/ikenga-pkg-mcp-iyke/dist/index.js.
Tools
Layout & navigation
Tool | Purpose |
| Show current sidebar mode + focused pane's route + full pane tree. |
| Navigate the focused pane to a route path. |
| Switch sidebar activity mode. |
| Open a new tab in the focused pane (route, terminal, chat, artifact, mini-app). |
| Split a pane horizontally or vertically. |
| Focus a pane by id or 1-based DFS leaf index (⌃1..⌃6). |
| Close a pane (focused if |
Runtime inspection & driving
Tool | Purpose |
| Accessibility-tree snapshot of the focused pane (Playwright-style refs). |
| Last 500 console + error logs from the running webview. |
| Last 100 fetch/XHR network entries with status + duration. |
| PNG screenshot of the window or a specific pane. |
| Wait until a predicate is satisfied (text/selector/ref/gone). |
| Click an element by ref, selector, or text. |
| Type into an input/textarea/contenteditable. |
| Dispatch a keyboard combo (e.g. |
| Dump the TanStack Query cache for the focused pane. |
| Open Chrome DevTools (debug builds only). |
Iframe runtime state
Tool | Purpose |
| Read the latest published state object for an iframe pane. |
| Send a fire-and-forget postMessage to an iframe pane. |
Projects
Tool | Purpose |
| Create a project (slug + display name; optional root_path, icon, color, description). |
| Patch fields on an existing project (display_name, root_path, icon, color, description, position). |
| List projects in switcher order; pass |
| Soft-delete a project; refuses to archive the built-in Default project. |
| Switch the shell's active project; refetches project-scoped queries. |
| Return 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 ontoken— bearer token required on every requestpid— 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.jsonschema.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.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityCmaintenanceMCP server exposing KiCad PCB Editor functionality via IPC API.41MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that exposes KiCad PCB design automation tools to AI assistants and other MCP clients.
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with the Phiacta knowledge platform.17GPL 3.0
- AlicenseNot gradedqualityCmaintenanceA local MCP server that enables MCP-compatible AI clients to inspect and control the currently open scene in a running Autodesk VRED Professional 2027 instance via a secure bridge, supporting read-only inspection and gated mutations like selection, visibility, transforms, and screenshots.MIT
Related MCP Connectors
MCP server exposing the Backtest360 engine API as tools for AI agents.
MCP server for generating rough-draft project plans from natural-language prompts.
Personal assistant MCP server with search, execute, packages, jobs, secrets, and integrations.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Royalti-io/ikenga-pkg-mcp-iyke'
If you have feedback or need assistance with the MCP directory API, please join our Discord server