Ext Ops Panel
Open dashboard
Comparison

ai.kazkar/kazkar vs LoreConvo

ai.kazkar/kazkar is an MCP server published by kazkar.ai. 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-24. 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
Marketplaceai.kazkar/kazkarLoreConvo
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.10.12
Downloads/month (PyPI): 902
Downloads/week (PyPI): 380
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

ai.kazkar/kazkar vs LoreConvo
Factai.kazkar/kazkarLoreConvo
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub12
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)Remote server (kazkar.ai/api/mcp)On your machine (loreconvo)
Transport (differs)Streamable HTTPstdio
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)Not a bundle7
Licence (differs)Not statedBSL-1.1
Repository (differs)Not statedgithub.com/labyrinth-analytics/loreconvo
Changes in the last 7 days (differs)20
First seen (differs)2026-10-182026-10-11
Endpoint at the last check (differs)Responded 3 h ago, requires a keyno 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

ai.kazkar/kazkar

In its own words, on Official MCP Registry:

Access your Kazkar TTRPG world — campaigns, chronicles, transcripts, lore — in any MCP client.

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

ai.kazkar/kazkar As a remote MCP server

Claude Code
claude mcp add --transport http kazkar https://kazkar.ai/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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.

Only ai.kazkar/kazkar 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 ai.kazkar/kazkar publish no settings it asks for, so we do not compare settings.

What it can do: ai.kazkar/kazkar · 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