Ext Ops Panel
Open dashboard
Comparison

com.usememra/memra vs DeepMem

com.usememra/memra is an MCP server published by usememra.com. Marketplaces we read that list it: 1 (Official MCP Registry). DeepMem is an MCP server published by deepmemteam. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacecom.usememra/memraDeepMem
Official MCP Registry Listed
Version: 4.7.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.0
Forks (GitHub): 2
Stars (GitHub): 114
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

com.usememra/memra vs DeepMem
Factcom.usememra/memraDeepMem
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)114 (better)
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (usememra.com/mcp)Remote server (deepmem.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/usememra/mcpgithub.com/deepmemteam/deepmem
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 33 h agoNot responding since 2026-10-16

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

com.usememra/memra

In its own words, on Official MCP Registry:

Persistent memory for AI agents. EU-hosted, privacy-first, hybrid recall, contradiction detection.

DeepMem

In its own words, on Official MCP Registry:

Mem0-compatible persistent memory for AI agents: write facts once, recall them semantically.

How to run each

com.usememra/memra As a remote MCP server

Claude Code
claude mcp add --transport http memra https://usememra.com/mcp

DeepMem As a remote MCP server

Claude Code
claude mcp add --transport http deepmem https://deepmem.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of com.usememra/memra responded at the last daily check. How we check endpoints

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: com.usememra/memra · What it can do: DeepMem · 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