Ext Ops Panel
Open dashboard
Comparison

memory-mcp vs ai.membase/membase

memory-mcp is a plugin bundle for AI coding tools published by Michael Denyer. Marketplaces we read that list it: 1 (Community GitHub marketplaces). ai.membase/membase is an MCP server published by membase.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplacememory-mcpai.membase/membase
Community marketplace michael-denyer/memory-mcp Listed
Version: 0.8.0
Forks (GitHub): 2
Stars (GitHub): 10
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 8
Stars (GitHub): 24
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

memory-mcp vs ai.membase/membase
Factmemory-mcpai.membase/membase
Marketplaces that list it11
Stars (GitHub) (differs)10 (worse)24 (better)
Forks (GitHub) (differs)2 (worse)8 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.app.membase.ai/mcp-http)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)4Not published
Parts of the bundle (differs)17Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/michael-denyer/memory-mcpgithub.com/unibaseio/membase
Changes in the last 7 days22
First seen2026-10-142026-10-14
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

memory-mcp

In its own words, on Community GitHub marketplaces:

Persistent memory for Claude Code with hot cache instant recall and semantic search. Give your AI assistant a second brain.

ai.membase/membase

In its own words, on Official MCP Registry:

Long-term memory for you and your AIs: search memories, read the profile, add facts and documents.

How to run each

memory-mcp As a Claude Code plugin

Claude Code
/plugin marketplace add michael-denyer/memory-mcp
/plugin install memory-mcp@memory-mcp-marketplace

ai.membase/membase As a remote MCP server

Claude Code
claude mcp add --transport http membase https://api.app.membase.ai/mcp-http

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

Neither one's marketplaces publish the settings it asks for.

What it can do: memory-mcp · What it can do: ai.membase/membase · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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