Ext Ops Panel
Open dashboard
Comparison

TriliumNext (trilium-mcp) vs LoreConvo

TriliumNext (trilium-mcp) is an MCP server published by OVDEN13. Marketplaces we read that list it: 1 (Official MCP Registry). LoreConvo is an MCP server published by labyrinth-analytics. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-19. 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
MarketplaceTriliumNext (trilium-mcp)LoreConvo
Official MCP Registry Listed
Version: 0.1.5
Forks (GitHub): 2
Stars (GitHub): 5
Not marked · First seen
Listed
Version: 0.10.12
Downloads/month (PyPI): 902
Downloads/week (PyPI): 177
Forks (GitHub): 1
Stars (GitHub): 12
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.9.0
Forks (GitHub): 1
Stars (GitHub): 12
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

TriliumNext (trilium-mcp) vs LoreConvo
FactTriliumNext (trilium-mcp)LoreConvo
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)5 (worse)12 (better)
Forks (GitHub) (differs)2 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ghcr.io/ovden13/trilium-mcp:0.1.5)On your machine (loreconvo)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 11, secrets among them: 1
Hooks it runs (differs)Not published4
Parts of the bundle (differs)Not a bundle7
Licence (differs)Not statedBSL-1.1
Repository (differs)github.com/ovden13/trilium-mcpgithub.com/labyrinth-analytics/loreconvo
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

TriliumNext (trilium-mcp)

In its own words, on Official MCP Registry:

Read and write a self-hosted TriliumNext knowledge base over its ETAPI.

LoreConvo

In its own words, on Official MCP Registry:

Local-first persistent session memory for Claude Code and other agents. SQLite + FTS5, no cloud.

How to run each

TriliumNext (trilium-mcp) As a local MCP server: Docker image

Claude Code
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.5

Requires: TRILIUM_TOKEN (secret), TRILIUM_URL

LoreConvo As a local MCP server: PyPI package

Claude Code
claude mcp add --env "LORECONVO_PRO=<YOUR_LORECONVO_PRO>" --transport stdio loreconvo -- uvx loreconvo

Requires: LORECONVO_PRO (secret)

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 TriliumNext (trilium-mcp) asks for

  • TRILIUM_HTTP_TIMEOUT_SECONDS
  • TRILIUM_MCP_LOG
  • TRILIUM_TOKEN (secret)
  • TRILIUM_URL

Only LoreConvo asks for

  • LORECONVO_PRO (secret)

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

What it can do: TriliumNext (trilium-mcp) · What it can do: LoreConvo · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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