openviking-memory vs XMemo
openviking-memory is a plugin bundle for AI coding tools published by OpenViking. Marketplaces we read that list it: 1 (Community GitHub marketplaces). XMemo is an MCP server published by yonro. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-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 |  XMemo | |
|---|---|---|
| Community marketplace volcengine/openviking | Listed Version: 0.7.23 Forks (GitHub): 3 479 Stars (GitHub): 42 205 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.346 Downloads/month (npm): 901 Downloads/week (npm): 127 Forks (GitHub): 0 Stars (GitHub): 13 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.4.193 Downloads/month (npm): 901 Downloads/week (npm): 127 Forks (GitHub): 0 Stars (GitHub): 13 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 | openviking-memory | XMemo |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 42 205 (better) | 13 (worse) |
| Forks (GitHub) (differs) | 3 479 (better) | 0 (worse) |
| Last release (differs) | 2026-11-13 (better) | 2026-10-28 (worse) |
| 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 (differs) | Not published | 2, secrets among them: 1 |
| Hooks it runs (differs) | 9 | Not published |
| Parts of the bundle (differs) | 16 | Not a bundle |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/volcengine/openviking | github.com/yonro/memory-os-cli |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen (differs) | 2026-11-10 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 12 h ago, requires authentication |
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
openviking-memory
Long-term semantic memory for Claude Code, powered by OpenViking
XMemo
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
How to run each
openviking-memory As a Claude Code plugin
/plugin marketplace add volcengine/openviking
/plugin install openviking-memory@openvikingXMemo 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 openviking-memory publish no settings it asks for, so we do not compare settings.
What it can do: openviking-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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.