Ext Ops Panel
Open dashboard
Comparison

chat-fork-map vs fish-bridge — Session Knowledge Graph

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). fish-bridge — Session Knowledge Graph is an MCP server published by MakeaMouse. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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-mapfish-bridge — Session Knowledge Graph
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: 0.1.3
Downloads/month (PyPI): 89
Downloads/week (PyPI): 42
Forks (GitHub): 0
Stars (GitHub): 2
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 fish-bridge — Session Knowledge Graph
Factchat-fork-mapfish-bridge — Session Knowledge Graph
Marketplaces that list it11
Stars (GitHub)22
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (fish-bridge-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 3
Licence (differs)MITNot stated
Repository (differs)github.com/jdneo/copilot-chat-mapgithub.com/makeamouse/fish-bridge-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.

fish-bridge — Session Knowledge Graph

In its own words, on Official MCP Registry:

Compresses AI chat sessions into a typed knowledge graph. Local/offline via Ollama.

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.

fish-bridge — Session Knowledge Graph As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio fish-bridge-mcp -- uvx fish-bridge-mcp

Requires: ANTHROPIC_API_KEY (secret), GEMINI_API_KEY (secret), OPENAI_API_KEY (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 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: fish-bridge — Session Knowledge Graph · 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. 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