Ext Ops Panel
Open dashboard
Comparison

mengram vs Perenna

mengram is a plugin bundle for AI coding tools published by Ali Baizhanov. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Perenna is an MCP server published by scarletkc. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-11-10. 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
MarketplacemengramPerenna
Community marketplace alibaizhanov/mengram Listed
Version: 0.1.4
Forks (GitHub): 34
Stars (GitHub): 207
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.1
Downloads/month (PyPI): 248
Downloads/week (PyPI): 29
Forks (GitHub): 2
Stars (GitHub): 60
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

mengram vs Perenna
FactmengramPerenna
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)207 (better)60 (worse)
Forks (GitHub) (differs)34 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mengram.io/mcp)On your machine (perenna)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 2
Hooks it runs (differs)2Not published
Parts of the bundle (differs)52
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/alibaizhanov/mengramgithub.com/scarletkc/perenna
Changes in the last 7 days00
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)Responded 20 h agono remote endpoint we check

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

mengram

In its own words, on Community GitHub marketplaces:

Persistent memory for Claude Code that survives /clear, machine switches, and team handoffs. Hosted memory backend with hybrid retrieval (vector + BM25 + RRF), Ebbinghaus temporal decay, and importance weighting. Same memory available across Claude Code, Cursor, Codex, and ChatGPT.

Perenna

In its own words, on Official MCP Registry:

A lightweight, Git-backed permanent memory for AI agents.

How to run each

mengram As a Claude Code plugin

Claude Code
/plugin marketplace add alibaizhanov/mengram
/plugin install mengram@mengram

Perenna As a local MCP server: PyPI package

Claude Code
claude mcp add --env "VEXOR_API_KEY=<YOUR_VEXOR_API_KEY>" --env "VEXOR_REMOTE_RERANK_API_KEY=<YOUR_VEXOR_REMOTE_RERANK_API_KEY>" --transport stdio perenna -- uvx perenna mcp

Requires: VEXOR_API_KEY (secret), VEXOR_REMOTE_RERANK_API_KEY (secret)

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

Only mengram 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

The marketplaces of mengram publish no settings it asks for, so we do not compare settings.

What it can do: mengram · What it can do: Perenna · 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