Memocall MCP Server

Recall past Claude Code conversations from any project as clean, compact Markdown.

Local serverstdioTypeScript

What is the Memocall MCP server?

If you already use Memocall, the memocall mcp server is the piece that lets your assistant work with it directly. Recall past Claude Code conversations from any project as clean, compact Markdown.

What the server does

An MCP server that lets Claude Code recall the context of your past conversations — from any project — on demand.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • list_sessions — Your recent conversations across all projects, grouped by directory. "What was I working on?"
  • search_sessions — Find a past conversation by keyword (matches titles + first messages + paths)
  • load_session — Load one conversation as compact Markdown — by id or query. Optionally a turn window via turns
  • session_outline — A cheap map of one conversation: the numbered list of your prompts. Great for huge sessions
  • search_in_session — Return only the turns within one conversation that match a keyword

Installation

Installation goes through your MCP client rather than a global install: point it at memocall on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Where it fits

Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Memocall's toolset — list_sessions, search_sessions, load_session and 2 more — is a fair guide to whether it matches your workflow. It is maintained by baodq06; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
list_sessionsYour recent conversations across all projects, **grouped by directory**. "What was I working on?"
search_sessionsFind a past conversation by keyword (matches titles + first messages + paths).
load_sessionLoad one conversation as compact Markdown — by id or query. Optionally a turn window via turns.
session_outlineA cheap **map** of one conversation: the numbered list of your prompts. Great for huge sessions.
search_in_sessionReturn only the turns **within** one conversation that match a keyword.

How to install the Memocall MCP server

{
  "mcpServers": {
    "memocall": {
      "command": "npx",
      "args": ["-y", "memocall"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Memocall to list sessions.
  • Use Memocall to search sessions.
  • Use Memocall to load session.

Frequently asked questions

It connects Memocall to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (list_sessions, search_sessions, load_session, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Memocall directly.