Recall MCP Server

by clauderecall Your server? Claim it

local only

Recall runs on your own machine — the client starts it, so there is no endpoint to ping.

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

—

Installs / week

not published

—

Stars

on GitHub

—

Last commit

from GitHub

—

License

language unknown

Nothing serious here today

Today is the operative word: we check Recall every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Alternatives to Recall

same job, measured the same way

Recall

by clauderecallhq

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

167 installs/wk local only

Claude Memory Manager

by nyxtoolsdev

Cross-session memory for Claude Code — context capture, semantic search, recall

160 installs/wk local only

Repomemory

by danielguru

Persistent memory for AI coding agents. Hybrid search, auto-session capture, context routing.

85 installs/wk local only

Claudex

by kunwar-shah

Persistent memory + FTS5 search MCP server for Claude Code conversation history.

82 installs/wk local only

Longmem

by marerem

Persistent cross-project memory for Cursor and Claude Code using local semantic search.

69 installs/wk local only

Memex

by pragneshbagary

Persistent session memory for Claude Code. Local SQLite, no LLMs, no network.

124 installs/wk local only

Melchizedek

by louis49

Persistent memory for Claude Code — offline, single-file, hybrid search.

58 installs/wk local only

Memory MCP

by yuvalsuede

Persistent memory + git snapshots for Claude Code. Never lose context or code.

122 installs/wk local only

Recall — questions

Answers built from our own checks of this server.

Why is there no uptime for Recall?

Recall runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone.