What is the key difference between Memocall and Scrivener MCP?

Memocall belongs to the Knowledge & Memory category with local stdio execution, while Scrivener MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Memocall or Scrivener MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Memocall and Scrivener MCP free or paid?

Memocall operates under a Free / Open Source model (No auth required). Scrivener MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Memocall lists 5 tools with 2 views and 2 GitHub stars. Scrivener MCP lists 6 tools with 16 views and 52 GitHub stars.

Can I use both Memocall and Scrivener MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Memocall vs Scrivener MCP

In-depth architectural comparison of the Memocall and Scrivener MCP 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

Memocall

Knowledge & Memory · Local stdio

Quality: 61/100 (Good) | Auth: No auth required

Scrivener MCP

Knowledge & Memory · Local stdio

Quality: 61/100 (Good) | Auth: No auth required

Verdict Summary: Choose Memocall if you need specialized Knowledge & Memory tools running via a local process. Choose Scrivener MCP 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 Memocall when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: list_sessions, search_sessions, load_session.

Explore Memocall Details

Choose Scrivener MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Scrivener 3 document access and editing, Deterministic writing analysis, Keyword and offline semantic search.

Explore Scrivener MCP Details

Feature & Specification Comparison

Specification	Memocall baodq06 Knowledge & Memory	Scrivener MCP writerslogic Knowledge & Memory
Summary	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	Connect Scrivener 3 writing projects to Claude and other AI assistants. 47 tools for document management, writing analysis, semantic search, character/plot memory, and content enhancement. Progressive skill loading, relationship engine with HMS triplets, and JS fallback for offline semantic search. npm i -g scrivener-mcp
Category & Scope

Tools & Capabilities Breakdown

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

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Memocall Configuration

mcpServers (Claude Desktop / Cursor)

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

Scrivener MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "writerslogic-scrivener-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "scrivener-setup"
      ]
    }
  }
}

Frequently Asked Questions

Memocall is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Scrivener MCP belongs to Knowledge & Memory using local stdio subprocess. Select Memocall when you need capabilities focused on knowledge & memory and Scrivener MCP when you require tools for knowledge & memory.

More alternatives to Memocall More alternatives to Scrivener MCP Knowledge & Memory category hub