Ikenga iyke (control bridge) runs on your own machine — the client starts it, so there is no endpoint to ping. 47 installs a week from npm. Last commit 11 Aug 2026.
Drive a running Ikenga desktop app from MCP clients — DOM, click, type, navigate, screenshot.
The author archived this repository on GitHub, meaning it is no longer maintained.
We read the source, 12 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет @ikenga/mcp-iyke ссылается на ikenga-hq/ikenga-pkgs
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add ikenga-pkg-mcp-iyke -- npx -y @ikenga/mcp-iyke
{
"mcpServers": {
"ikenga-pkg-mcp-iyke": {
"args": [
"-y",
"@ikenga/mcp-iyke"
],
"command": "npx"
}
}
}
[mcp_servers.ikenga-pkg-mcp-iyke]
command = "npx"
args = ["-y", "@ikenga/mcp-iyke"]
{
"mcpServers": {
"ikenga-pkg-mcp-iyke": {
"args": [
"-y",
"@ikenga/mcp-iyke"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"ikenga-pkg-mcp-iyke": {
"args": [
"-y",
"@ikenga/mcp-iyke"
],
"command": "npx"
}
}
}
Drive a running Ikenga desktop app from MCP clients — DOM, click, type, navigate, screenshot.
Automate cloud Chrome—navigate, click, type, screenshot, run code, record screen video
macOS desktop control for Claude: click, type, screenshot, AX tree, browser control, agentic loops.
MCP server for desktop, browser (CDP), and Android automation. Screenshot, OCR, click, type.
Drive a running tModLoader (Terraria) instance from an agent: launch, query, screenshot, read state.
Control Windows desktop via MCP: mouse, keyboard, screenshots, clipboard, and apps.
Hosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot.
Let AI agents inspect and drive running WPF apps: tree, bindings, screenshots, clicks, text input.
Answers built from our own checks of this server.