Ext Ops Panel
Open dashboard
Comparison

chat-fork-map vs brain — the recorder

chat-fork-map is a plugin bundle for AI coding tools published by jdneo. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). brain — the recorder is an MCP server published by mordechaipotash. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). 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
Marketplacechat-fork-mapbrain — the recorder
Copilot CLI: github/awesome-copilot Listed
Version: 0.0.5
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.0.0
Downloads/month (PyPI): 10 320
Downloads/week (PyPI): 145
Forks (GitHub): 18
Stars (GitHub): 81
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 2.1.1
Downloads/month (PyPI): 10 320
Downloads/week (PyPI): 145
Forks (GitHub): 18
Stars (GitHub): 81
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

chat-fork-map vs brain — the recorder
Factchat-fork-mapbrain — the recorder
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 (worse)81 (better)
Forks (GitHub) (differs)0 (worse)18 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (brain-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
LicenceMITMIT
Repository (differs)github.com/jdneo/copilot-chat-mapgithub.com/mordechaipotash/brain-mcp
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

chat-fork-map

In its own words, on Copilot CLI: github/awesome-copilot:

Maps branching Copilot conversations so parallel follow-up questions and exploration paths from complex tasks or learning can be navigated without losing context. Its visual layout makes breadth-first exploration easier than managing multiple active threads in a traditional conversation list.

brain — the recorder

In its own words, on Official MCP Registry:

Records your Claude Code, Codex and Pi history before deletion. Cited-or-abstain recall.

How to run each

chat-fork-map

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

brain — the recorder As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio brain-mcp -- uvx brain-mcp

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 chat-fork-map publish no settings it asks for, so we do not compare settings.

What it can do: chat-fork-map · What it can do: brain — the recorder · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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