Ext Ops Panel
Open dashboard
Comparison

session-wrap vs LoreConvo

session-wrap is a plugin bundle for AI coding tools published by Team Attention. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-11-09. 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
Marketplacesession-wrapLoreConvo
Community marketplace team-attention/plugins-for-claude-natives Listed
Version: 1.0.0
Forks (GitHub): 106
Stars (GitHub): 831
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.11.0
Downloads/month (PyPI): 902
Downloads/week (PyPI): 100
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

session-wrap vs LoreConvo
Factsession-wrapLoreConvo
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)831 (better)12 (worse)
Forks (GitHub) (differs)106 (better)1 (worse)
Last release (differs)Not published2026-11-06
Where it runs (differs)Installs as a plugin bundleOn your machine (loreconvo)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Hooks it runs (differs)Not published4
Parts of the bundle (differs)97
Licence (differs)MITBSL-1.1
Repository (differs)github.com/team-attention/plugins-for-claude-nativesgithub.com/labyrinth-analytics/loreconvo
Changes in the last 7 days (differs)21
First seen (differs)2026-11-082026-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

session-wrap

In its own words, on Community GitHub marketplaces:

Session wrap-up workflow with multi-agent analysis for documentation, automation, learning, and follow-up

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

session-wrap As a Claude Code plugin

Claude Code
/plugin marketplace add team-attention/plugins-for-claude-natives
/plugin install session-wrap@team-attention-plugins

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

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

What it can do: session-wrap · What it can do: LoreConvo · 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. 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