An MCP server that wraps Ikenga’s local iyke control bridge so MCP clients can drive a running Ikenga desktop session. It exposes tools for navigation, pane management, runtime inspection, input simulation, screenshots, logs, network data, and iframe interaction.
From the registry: Drive a running Ikenga desktop app from MCP clients — DOM, click, type, navigate, screenshot.
Please install the `ikenga-pkg-mcp-iyke` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install Node.js 20 or newer** — Node.js version 20 or higher is required to run the MCP server via npx or a global npm install.
- **Install and run the Ikenga desktop app** — The MCP server connects to a running Ikenga desktop app by reading its local control.json file and talking to the app's localhost control bridge. If the app is not running, tool calls fail. (https://github.com/Royalti-io/ikenga)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@ikenga/mcp-iyke"]
Note: Prefer the no-install npx path shown in the README. The server does not require user-supplied environment variables; it discovers the localhost port and bearer token from Ikenga's platform-specific control.json file.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.MCP server for Firecrawl web scraping, structured data extraction and web search integration.