Ext Ops Panel
Open dashboard
Comparison

LocalSynapse - Local File Search MCP Server vs io.github.egoughnour/cowork-history

LocalSynapse - Local File Search MCP Server is an MCP server published by LocalSynapse. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.egoughnour/cowork-history is an MCP server published by egoughnour. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
MarketplaceLocalSynapse - Local File Search MCP Serverio.github.egoughnour/cowork-history
Official MCP Registry Listed
Version: 2.1.0
No figure published
Not marked · First seen
Listed
Version: 4.0.3
Downloads/month (PyPI): 72
Downloads/week (PyPI): 19
Forks (GitHub): 0
Stars (GitHub): 1
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

LocalSynapse - Local File Search MCP Server vs io.github.egoughnour/cowork-history
FactLocalSynapse - Local File Search MCP Serverio.github.egoughnour/cowork-history
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)On your machine (https://github.com/LocalSynapse/LocalSynapse/releases/download/v2.1.0/localsynapse-mcp.mcpb)On your machine (cowork-history)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/egoughnour/cowork-history
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

LocalSynapse - Local File Search MCP Server

In its own words, on Official MCP Registry:

Offline AI-powered local file search. BM25 + semantic hybrid search across all documents.

io.github.egoughnour/cowork-history

In its own words, on Official MCP Registry:

Hybrid search for Cowork history: FTS, Spotlight, and semantic vectors

How to run each

LocalSynapse - Local File Search MCP Server

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

io.github.egoughnour/cowork-history As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio cowork-history -- uvx cowork-history

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 LocalSynapse - Local File Search MCP Server publish no settings it asks for, so we do not compare settings.

What it can do: LocalSynapse - Local File Search MCP Server · What it can do: io.github.egoughnour/cowork-history · Compare two other plugins

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