Ext Ops Panel
Open dashboard
Comparison

Embers: Tabletop RPG Toolkit vs LoreConvo

Embers: Tabletop RPG Toolkit is an MCP server published by embersds.com. 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-26. 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
MarketplaceEmbers: Tabletop RPG ToolkitLoreConvo
Official MCP Registry Listed
Version: 0.0.58
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

Embers: Tabletop RPG Toolkit vs LoreConvo
FactEmbers: Tabletop RPG ToolkitLoreConvo
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 (gateway.embersds.com/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 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days 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

Embers: Tabletop RPG Toolkit

In its own words, on Official MCP Registry:

Characters, campaigns, adventures & worlds for D&D 5e/5.5e, Pathfinder, Savage Worlds, Fate, & more.

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

Embers: Tabletop RPG Toolkit As a remote MCP server

Claude Code
claude mcp add --transport http embers https://gateway.embersds.com/mcp

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 Embers: Tabletop RPG Toolkit 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 Embers: Tabletop RPG Toolkit publish no settings it asks for, so we do not compare settings.

What it can do: Embers: Tabletop RPG Toolkit · 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