Archivist AI vs Memocall — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Archivist AI vs Memocall
In-depth architectural comparison of the Archivist AI and Memocall MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Archivist AI
Knowledge & Memory · Remote HTTP/SSE
Quality: 53/100 (Good) | Auth: No auth required
Memocall
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Archivist AI if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Memocall if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Archivist AI when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Official remote MCP server for Archivist AI TTRPG campaign memory: characters, sessions, and more.
Recall past Claude Code conversations from any project. Lists and searches your sessions, then loads one on demand as clean, compact Markdown — with outline, turn-range, and in-session search for large sessions. Read-only over local /.claude transcripts; collapses tool calls to stay under the context cap. npx -y memocall
Archivist AI is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Memocall belongs to Knowledge & Memory using local stdio subprocess. Select Archivist AI when you need capabilities focused on knowledge & memory and Memocall when you require tools for knowledge & memory.
Get a session by ID. Optionally include related beats and moments.
get_session_cast_analysis
Get cast analysis: talk-share breakdown and core session metrics.
get_session_transcript
Get the cleaned transcript for a game session, including utterances, full text, and aggregate stats.
get_session_handout
Get the generated session handout for a game session, including summary, outlines, spotlights, and notable moments.
patch_session
Partial update (title, session_date, summary, image). Explicit-link contract for wikilinks.
update_session
Full update (PUT). Explicit-link contract for wikilinks.
+68 more tools listed on main page
Memocall Tools (5)
list_sessions
List your recent Claude Code conversations across ALL projects, grouped by project directory. Use this to answer 'what sessions have I worked on recently?' or to find a past session before loading it. Returns each session's title, date, turn count, and id.
search_sessions
Search your past Claude Code conversations (across all projects) by keyword — matches session titles, first messages, and project paths. Use when the user refers to a past conversation by topic (e.g. 'the session where we set up the license system'). Returns matching sessions with their ids.
load_session
Load the context of a past Claude Code conversation as compact Markdown (human turns, collapsed tool-call summaries, and assistant replies — tool outputs are elided). Provide either a session `id` (from list_sessions/search_sessions) or a free-text `query` to find it. Use this to pull a previous conversation's context into the current session. For a very large session, either pass `turns` to load a specific window (turn numbers come from session_outline), or prefer session_outline / search_in_session.
session_outline
Get a quick MAP of a past Claude Code conversation: the numbered list of the user's prompts, one line each. Very cheap even for huge sessions. Use this to see what a session covered, or to find which turn numbers to then load with load_session's `turns`. Identify the session by `id` or free-text `query`.
search_in_session
Find specific turns WITHIN one past Claude Code conversation by keyword — returns only the matching turns (with their turn numbers). Use when the user asks what was decided or discussed about a topic inside a known or large session (e.g. 'what did we decide about retries in that session'). Pick the session by `id` or `session` (free-text); `query` is the keyword to find inside it.