Server data from the Official MCP Registry
Drive a running Ikenga desktop app from MCP clients — DOM, click, type, navigate, screenshot.
About
Drive a running Ikenga desktop app from MCP clients — DOM, click, type, navigate, screenshot.
Security Report
Valid MCP server (2 strong, 2 medium validity signals). No known CVEs in dependencies. ⚠️ Package registry links to a different repository than scanned source. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
14 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"dev-ikenga-mcp-iyke": {
"args": [
"-y",
"@ikenga/mcp-iyke"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
ikenga-pkgs
The canonical home for first-party Ikenga packages — engines, MCP servers, mini-apps, and helpers — in one Apache-2.0 monorepo.
What it is
Every first-party Ikenga package lives here (ADR-009), versioned and published with Changesets. It's a good place to read working examples of each pkg archetype before authoring your own.
Layout
packages/
engine/ AI engine adapters (claude-code, noop, …)
mcp/ MCP servers (iyke, …)
apps/ User-facing iframe mini-apps (studio, tasks, …)
connectors/ External-service adapters
sidecars/ Long-lived headless processes
Workflow
This monorepo uses Changesets for per-package versioning and publish.
pnpm install
pnpm -r build
pnpm changeset # author a changeset describing your change
git commit -am "feat: ..."
# Open PR; on merge to main, "Version Packages" PR opens.
# Merging that PR publishes all bumped packages to npm and updates the registry index.
Each PR that changes a package must include a .changeset/*.md (the
changeset-bot will nag you on PRs that don't).
Registry
Published versions appear in the ikenga-registry
within seconds of pnpm changeset publish completing, via the
scripts/update-registry-index.mjs step in the release workflow. The shell and
ikenga CLI both consume that registry for discovery and install.
Links
ikenga— the desktop shell that loads theseikenga-contract— the manifest schema each pkg validates against- Building in the Loop — biweekly letters on running a real multi-agent Claude Code system
License
Apache-2.0 — see LICENSE.
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
MarkItDown
Freeby Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.