Memex — Local AI Memory vs TriliumNext (trilium-mcp)
Memex — Local AI Memory is a plugin bundle for AI coding tools published by Shvmvrshny. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). TriliumNext (trilium-mcp) is an MCP server published by OVDEN13. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  Memex — Local AI Memory |  TriliumNext (trilium-mcp) |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.5 Forks (GitHub): 2 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
| Fact | Memex — Local AI Memory | TriliumNext (trilium-mcp) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (worse) | 5 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (ghcr.io/ovden13/trilium-mcp:0.1.5) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 1 |
| Hooks it runs (differs) | 4 | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/shvmvrshny/memex | github.com/ovden13/trilium-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
Memex — Local AI Memory
Local AI memory system for Claude Code and Cursor. Remembers your preferences, decisions, and project context across sessions using a Go HTTP service and Qdrant vector database running locally in Docker. All data stays on your machine — nothing is sent to the cloud.
TriliumNext (trilium-mcp)
Read and write a self-hosted TriliumNext knowledge base over its ETAPI.
How to run each
Memex — Local AI Memory As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install memex@claude-communityTriliumNext (trilium-mcp) As a local MCP server: Docker image
claude mcp add --env "TRILIUM_TOKEN=<YOUR_TRILIUM_TOKEN>" --env "TRILIUM_URL=<YOUR_TRILIUM_URL>" --transport stdio trilium-mcp -- docker run -i --rm -e TRILIUM_TOKEN -e TRILIUM_URL ghcr.io/ovden13/trilium-mcp:0.1.5Requires: TRILIUM_TOKEN (secret), TRILIUM_URL
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 Memex — Local AI Memory publish no settings it asks for, so we do not compare settings.
What it can do: Memex — Local AI Memory · What it can do: TriliumNext (trilium-mcp) · 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.