Ext Ops Panel
Open dashboard
Comparison

ETHER Long-Term Memory vs AI Context Flow

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). AI Context Flow is an MCP server published by plurality.network. 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

Where each is published
MarketplaceETHER Long-Term MemoryAI Context Flow
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: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 2
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

ETHER Long-Term Memory vs AI Context Flow
FactETHER Long-Term MemoryAI Context Flow
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (app.plurality.network/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)15Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/artineering/ether-ltmgithub.com/web3-plurality/plurality-mcp-server
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 30 h ago, requires a key

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

In its own words, on Community GitHub marketplaces:

Provenance-disciplined long-term memory for Claude Code.

AI Context Flow

In its own words, on Official MCP Registry:

Universal memory for AI agents and tools. Save, organize and search context anywhere.

How to run each

ETHER Long-Term Memory As a Claude Code plugin

Claude Code
/plugin marketplace add artineering/ether-ltm
/plugin install ether-ltm@ether-ltm-local

AI Context Flow As a remote MCP server

Claude Code
claude mcp add --transport http ai-context-flow https://app.plurality.network/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only AI Context Flow 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

Neither one's marketplaces publish the settings it asks for.

What it can do: ETHER Long-Term Memory · What it can do: AI Context Flow · 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.

Where the data comes from: how the catalog is built