Ext Ops Panel
Open dashboard
Comparison

SuperLocalMemory vs Neonia: The Cloud Backend for AI Agents

SuperLocalMemory is a plugin bundle for AI coding tools published by Qualixar. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Neonia: The Cloud Backend for AI Agents is an MCP server published by neonia.io. 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
MarketplaceSuperLocalMemoryNeonia: The Cloud Backend for AI Agents
Community marketplace varun369/superlocalmemoryv2 Listed
Version: 4.2.7
Forks (GitHub): 36
Stars (GitHub): 236
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Forks (GitHub): 1
Stars (GitHub): 5
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

SuperLocalMemory vs Neonia: The Cloud Backend for AI Agents
FactSuperLocalMemoryNeonia: The Cloud Backend for AI Agents
Marketplaces that list it11
Stars (GitHub) (differs)236 (better)5 (worse)
Forks (GitHub) (differs)36 (better)1 (worse)
Last release (differs)2026-10-15Not published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.neonia.io/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Hooks it runs (differs)10Not published
Parts of the bundle (differs)27Not a bundle
Licence (differs)AGPL-3.0-or-laterNot stated
Repository (differs)github.com/varun369/superlocalmemoryv2github.com/neonia-io/agent-mcp-examples
Changes in the last 7 days (differs)50
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot 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

SuperLocalMemory

In its own words, on Community GitHub marketplaces:

Local-first agent memory + reversible context compression and KV cache, as an MCP server, with optional pictures, PDFs and bot messaging. Serves the 58-tool full profile by default; `slm tools set <name>` changes it for every app.

Neonia: The Cloud Backend for AI Agents

In its own words, on Official MCP Registry:

Multiple MCP tools, persistent graph memory, token-saving data pointers, and more.

How to run each

SuperLocalMemory As a Claude Code plugin

Claude Code
/plugin marketplace add varun369/superlocalmemoryv2
/plugin install superlocalmemory@qualixar

Neonia: The Cloud Backend for AI Agents As a remote MCP server

Claude Code
claude mcp add --transport http cloud-backend https://mcp.neonia.io/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

The marketplaces of Neonia: The Cloud Backend for AI Agents publish no settings it asks for, so we do not compare settings.

What it can do: SuperLocalMemory · What it can do: Neonia: The Cloud Backend for AI Agents · 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