Ext Ops Panel
Open dashboard
Comparison

pseudolife-memory vs com.clauderecall/recall

pseudolife-memory is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.

pseudolife-memory is a plugin bundle for AI coding tools published by Pseudogiant-xr. No marketplace we read lists it any more. com.clauderecall/recall is an MCP server published by clauderecall.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacepseudolife-memorycom.clauderecall/recall
Community marketplace pseudogiant-xr/pseudolife-mcp Removed on 2026-10-20
Version: not stated
Forks (GitHub): 1
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.183.2
Downloads/month (npm): 572
Downloads/week (npm): 122
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

pseudolife-memory vs com.clauderecall/recall
Factpseudolife-memoryno longer listed · com.clauderecall/recall
Marketplaces that list it (differs)01
Stars (GitHub) (differs)5No figure on GitHub
Forks (GitHub) (differs)1No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@clauderecallhq/cli)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)11Not published
Parts of the bundle (differs)9Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/pseudogiant-xr/pseudolife-mcpgithub.com/clauderecallhq/clauderecall
Changes in the last 7 days00
First seen (differs)2026-10-142026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of pseudolife-memory

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • Pseudolife Memory

    Persistent memory for MCP-compatible agents: memory bank, fact cortex, dreams, graph.

    by Pseudogiant-xr · MCP server

    Listed on: Official MCP Registry, PyPI (MCP servers) · Describes nearly the same job

  • meho

    Connect Claude Code to a MEHO backplane over the mcp-remote stdio shim and load the MEHO-first operating discipline as skills.

    by evoila Group · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • claude-meister

    Claude Code is great, but treating every prompt with full context is too expensive. I built Claude_Meister as an MCP plugin to dynamically route tasks and score memory, dropping…

    by Mintsolester · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-relay

    Let local Claude Code sessions talk to each other in natural language.

    by Innestic · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-bridge-mcp io.github.rahuljava2807/claude-bridge-mcp

    Pipes Claude Code session output into Claude Chat — no more copy-paste between tools

    by rahuljava2807 · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • mcp io.github.briefroom/mcp

    briefroom stdio MCP server — expose the briefroom CLI to Claude Code, Codex, and other agents.

    by briefroom · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

pseudolife-memory

In its own words, on Community GitHub marketplaces:

Wires the Pseudolife-MCP daemon into Claude Code: session briefing + identity hooks, /dream and /memory-status commands. MCP transport is registered separately (installer shim or claude mcp add).

com.clauderecall/recall

In its own words, on Official MCP Registry:

Persistent memory for Claude Code and Codex. Search and re-inject context from any session.

How to run each

pseudolife-memory

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

com.clauderecall/recall As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio recall -- npx -y @clauderecallhq/cli

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: pseudolife-memory · What it can do: com.clauderecall/recall · 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