Ext Ops Panel
Open dashboard
Comparison

synaptic vs io.github.volsier/memforge-memory

synaptic is a plugin bundle for AI coding tools published by HYPERLYNQ. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.volsier/memforge-memory is an MCP server published by volsier. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
Marketplacesynapticio.github.volsier/memforge-memory
Claude Code: claude-plugins-community Listed
Version: 1.7.7
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Downloads/month (npm): 52
Downloads/week (npm): 7
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

synaptic vs io.github.volsier/memforge-memory
Factsynapticio.github.volsier/memforge-memory
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@memforgeai/memory-service)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 1
Hooks it runs (differs)5Not published
Parts of the bundle (differs)9Not a bundle
Licence (differs)SEE LICENSE IN LICENSENot stated
Repository (differs)github.com/hyperlynq/synapticNot stated
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

synaptic

In its own words, on Claude Code: claude-plugins-community:

Persistent local memory for Claude Code — cross-session context, semantic search, zero cloud

io.github.volsier/memforge-memory

In its own words, on Official MCP Registry:

Team engineering memory for AI coding assistants. 47 MCP tools, pgvector semantic search.

How to run each

synaptic

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

io.github.volsier/memforge-memory As a local MCP server: npm package

Claude Code
claude mcp add --env "DATABASE_URL=<YOUR_DATABASE_URL>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "OPENAI_BASE_URL=<YOUR_OPENAI_BASE_URL>" --env "OPENAI_EMBEDDING_MODEL=<YOUR_OPENAI_EMBEDDING_MODEL>" --transport stdio memforge-memory -- npx -y @memforgeai/memory-service

Requires: DATABASE_URL, OPENAI_API_KEY (secret), OPENAI_BASE_URL, OPENAI_EMBEDDING_MODEL

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

What it can do: synaptic · What it can do: io.github.volsier/memforge-memory · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-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