Omi vs alley-oop
Omi is an MCP server published by BasedHardware. Marketplaces we read that list it: 1 (Docker MCP Catalog). alley-oop is a plugin bundle for AI coding tools published by 1azarus. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Omi |  alley-oop |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:674097f43757 Forks (GitHub): 2 605 Pulls (Docker Hub): 33 761 Stars (Docker Hub): 1 Stars (GitHub): 13 719 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.0.5 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Omi | alley-oop |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 13 719 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 33 761 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 2 605 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/omi) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 6 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/basedhardware/omi | github.com/1azarus/alley-oop |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Omi
A Model Context Protocol server for Omi interaction and automation. This server provides tools to read, search, and manipulate Memories and Conversations.
alley-oop
Alley Oop keeps your development momentum going across sessions without the cost of replaying full conversation history. When you're ready to hand off, /alley distills your current session into a compact cold-start prompt — capturing just what the next session needs to orient and act immediately. Start the new session with /oop and you're back in the game. For parallel workstreams, /alleyarchive and /ooparchive let you branch, archive, and resume multiple threads independently.
How to run each
Omi As a local MCP server: Docker image
claude mcp add --env "OMI_API_KEY=<YOUR_OMI_API_KEY>" --transport stdio omi -- docker run -i --rm -e OMI_API_KEY mcp/omiRequires: OMI_API_KEY (secret)
alley-oop As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install alley-oop@claude-communityCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of alley-oop publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of alley-oop publish no settings it asks for, so we do not compare settings.
What it can do: Omi · What it can do: alley-oop · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.