Log inSubmit server

Celiums Memory vs AgentRecall

A side-by-side look at the Celiums Memory and AgentRecall MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Celiums Memory logoCeliums MemoryKnowledge & Memory · Local subprocess (stdio)Cognitive memory engine with 5,100+ knowledge modules, circadian rhythm awareness, and emotional state tracking (PAD model). Hybrid search (PostgreSQL + Qdrant vectors + Valkey cache), per-user memory isolation, and multi-protocol support (MCP, REST, OpenAI, LangChain, A2A). npx @celiums/memory Website56GoodAuth: api key requiredAgentRecall logoAgentRecallKnowledge & Memory · Local subprocess (stdio)Persistent, compounding memory for AI agents across sessions. Uses the Intelligent Distance Protocol to surface the most contextually relevant past memories. Five tools: sessionstart, remember, recall, check, sessionend. npx agent-recall-mcp68GreatAuth: no auth required

Verdict: choose Celiums Memory for knowledge & memory work as a local process; choose AgentRecall for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Celiums Memory logoChoose Celiums Memory when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: SQLITE_PATH, DATABASE_URL, QDRANT_URL, VALKEY_URL, CELIUMS_API_KEY, PORT, CELIUMS_LLM_API_KEY, CELIUMS_LLM_BASE_URL.
Explore Celiums Memory

AgentRecall logoChoose AgentRecall when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like session_start, remember, recall.
Explore AgentRecall

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCeliums Memory logoCeliums MemoryAgentRecall logoAgentRecall
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal56/100 · Good68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNo auth required
PricingFreeFree
Required env varsSQLITE_PATHDATABASE_URLQDRANT_URLVALKEY_URLCELIUMS_API_KEYPORTCELIUMS_LLM_API_KEYCELIUMS_LLM_BASE_URLNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars23371
Directory activity 3 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listed5
Full listingView Celiums Memory View AgentRecall

Tools & capabilities

Celiums Memory tools

No tool names declared yet. Check the project README from the listing page.

AgentRecall tools 5

  • session_startLoads corrections, insights and `watch_for` warnings for the project
  • rememberSaves one fact; auto-routes to journal / palace room / corrections / awareness
  • recallRanked search across every store (RRF), with `useful` feedback that re-weights future ranking
  • checkMatches the plan against known corrections; returns `verdict: "blocked"` when one overrides it
  • session_endWrites the journal, promotes insights, records trajectory, optionally opens/closes a pipeline phase

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Celiums Memory

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "celiums-celiums-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@celiums/memory"
      ],
      "env": {
        "SQLITE_PATH": "YOUR_SQLITE_PATH_HERE",
        "DATABASE_URL": "YOUR_DATABASE_URL_HERE",
        "QDRANT_URL": "YOUR_QDRANT_URL_HERE",
        "VALKEY_URL": "YOUR_VALKEY_URL_HERE",
        "CELIUMS_API_KEY": "YOUR_CELIUMS_API_KEY_HERE",
        "PORT": "YOUR_PORT_HERE",
        "CELIUMS_LLM_API_KEY": "YOUR_CELIUMS_LLM_API_KEY_HERE",
        "CELIUMS_LLM_BASE_URL": "YOUR_CELIUMS_LLM_BASE_URL_HERE"
      }
    }
  }
}

AgentRecall

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "goldentrii-agentrecall": {
      "command": "npx",
      "args": [
        "-y",
        "agent-recall-mcp"
      ]
    }
  }
}

Frequently asked questions

Celiums Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. AgentRecall belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Celiums Memory for knowledge & memory work and AgentRecall for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Celiums Memory is listed as free. Auth: api key required. AgentRecall is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add celiums-celiums-memory and goldentrii-agentrecall as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Celiums Memory has a quality signal of 56/100 (Good) with 3 views, 0 installs and 23 GitHub stars. AgentRecall has 68/100 (Great) with 5 views, 0 installs and 371 GitHub stars.

Popular comparisons with Celiums Memory

Popular comparisons with AgentRecall