Ext Ops Panel
Open dashboard
Comparison

nexo-brain vs YourMemory

nexo-brain is a plugin bundle for AI coding tools published by wazionapps. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). YourMemory is an MCP server published by sachitrafa. Marketplaces we read that list it: 1 (Official MCP Registry). 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

Where each is published
Marketplacenexo-brainYourMemory
Claude Code: claude-plugins-community Listed
Version: 6.0.4
Forks (GitHub): 9
Stars (GitHub): 27
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.4.18
Downloads/month (PyPI): 444
Downloads/week (PyPI): 57
Forks (GitHub): 21
Stars (GitHub): 270
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

nexo-brain vs YourMemory
Factnexo-brainYourMemory
Marketplaces that list it11
Stars (GitHub) (differs)27 (worse)270 (better)
Forks (GitHub) (differs)9 (worse)21 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (yourmemory)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 01, secrets among them: 0
Hooks it runs (differs)8Not published
Parts of the bundle (differs)8Not a bundle
Licence (differs)AGPL-3.0Not stated
Repository (differs)github.com/wazionapps/nexogithub.com/sachitrafa/yourmemory
Changes in the last 7 days00
First seen2026-10-112026-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

nexo-brain

In its own words, on Claude Code: claude-plugins-community:

Cognitive co-operator that gives AI agents persistent memory, learning, and work continuity. Includes session management, episodic/semantic memory (Atkinson-Shiffrin model), overnight learning (Deep Sleep), autonomous processes, trust scoring, adaptive calibration, unified diagnostics, and a web dashboard. Turns a stateless LLM into an operational partner that remembers, learns from mistakes, and improves over time.

YourMemory

In its own words, on Official MCP Registry:

Persistent memory for AI agents. Memories decay with time and strengthen on recall.

How to run each

nexo-brain As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install nexo-brain@claude-community

YourMemory As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio yourmemory -- uvx yourmemory

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

Only nexo-brain asks for

  • NEXO_CODE
  • NEXO_HOME

Only YourMemory asks for

  • PYTHONIOENCODING

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: nexo-brain · What it can do: YourMemory · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built