ETHER Long-Term Memory vs XMemo
ETHER Long-Term Memory is a plugin bundle for AI coding tools published by Siddharth. Marketplaces we read that list it: 1 (Community GitHub marketplaces). XMemo is an MCP server published by yonro. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 |  XMemo | |
|---|---|---|
| Community marketplace artineering/ether-ltm | Not seen in the last pass Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.346 Downloads/month (npm): 1 758 Downloads/week (npm): 64 Forks (GitHub): 1 Stars (GitHub): 12 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 | ETHER Long-Term Memory | XMemo |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 12 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (xmemo.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 15 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/artineering/ether-ltm | github.com/yonro/memory-os-cli |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-13 |
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
ETHER Long-Term Memory
Provenance-disciplined long-term memory for Claude Code.
XMemo
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
How to run each
ETHER Long-Term Memory As a Claude Code plugin
/plugin marketplace add artineering/ether-ltm
/plugin install ether-ltm@ether-ltm-localXMemo As a remote MCP server
claude mcp add --transport http xmemo https://xmemo.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: XMEMO_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only XMemo has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of ETHER Long-Term Memory publish no settings it asks for, so we do not compare settings.
What it can do: ETHER Long-Term Memory · What it can do: XMemo · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.