Stars

—

Tools

—

Uptime

—

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 these
• ikenga-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.

© 2026 MCP Directory.