ix-memory vs io.github.shofer-dev/live-memory
ix-memory is a plugin bundle for AI coding tools published by ix-infrastructure. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.shofer-dev/live-memory is an MCP server published by shofer-dev. Marketplaces we read that list it: 2 (Official MCP Registry, 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 | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 2.3.0 Forks (GitHub): 2 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.6.0 Downloads/month (PyPI): 68 Downloads/week (PyPI): 14 Forks (GitHub): 0 Stars (GitHub): 7 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 | ix-memory | io.github.shofer-dev/live-memory |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) | 7 | 7 |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 7 | 3 |
| Parts of the bundle (differs) | 16 | 8 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/ix-infrastructure/ix-claude-plugin | github.com/shofer-dev/claude-code-live-memory |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
ix-memory
Ix Memory connects Claude Code to Ix, a structured, persistent memory backend for codebases. Instead of reading raw source files to answer questions about your code, Claude queries a live knowledge graph — dramatically reducing token usage, improving accuracy, and enabling reasoning that scales to large, complex projects. All analysis runs locally on your machine. No source code is ever transmitted to external servers.
io.github.shofer-dev/live-memory
Persistent, read-only codebase memory for Claude Code; ask it instead of re-reading files.
How to run each
ix-memory As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install ix-memory@claude-community
io.github.shofer-dev/live-memory As a Claude Code plugin
/plugin marketplace add shofer-dev/claude-code-live-memory
/plugin install live-memory@shofer-live-memory
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: ix-memory · What it can do: io.github.shofer-dev/live-memory · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.