What is the key difference between Conversation Handoff MCP and Scrivener MCP?

Conversation Handoff MCP 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 Conversation Handoff MCP 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 Conversation Handoff MCP and Scrivener MCP free or paid?

Conversation Handoff MCP 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?

Conversation Handoff MCP lists 11 tools with 3 views and 6 GitHub stars. Scrivener MCP lists 6 tools with 16 views and 52 GitHub stars.

Can I use both Conversation Handoff MCP 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

Conversation Handoff MCP vs Scrivener MCP

In-depth architectural comparison of the Conversation Handoff MCP 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

Conversation Handoff MCP

Knowledge & Memory · Local stdio

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

Scrivener MCP

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Conversation Handoff MCP 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 Conversation Handoff 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: handoff_save, handoff_list, handoff_load.

Explore Conversation Handoff MCP 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	Conversation Handoff MCP Knowledge & Memory	Scrivener MCP writerslogic Knowledge & Memory
Summary	Hand off conversation context between Claude Desktop projects and across MCP clients. Memory-based, no file clutter.	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

Conversation Handoff MCP Tools (11)

handoff_save

Save a conversation handoff for later retrieval. Use this to pass conversation context to another AI or project. ## Long conversations (>~100KB) If the conversation is large, **save the first chunk with this tool**, then call `handoff_append` repeatedly with the remaining chunks. Doing one giant `handoff_save` can fail with an XML parse / tool-input error because Claude Code encodes tool arguments as XML internally and very large strings can break that encoding. ## Format Selection - **structured** (default): Organize content using the template below. Much faster — reduces output tokens to ~5-20% of the original conversation. Best for most handoffs. - **verbatim**: Save the complete word-for-word conversation. Use only when exact wording matters (e.g., legal text, precise error messages). ## Structured Template (for format="structured") ``` ## Key Decisions - [Decision]: [Rationale] ## Implementation Details [What was built/changed, with relevant code snippets] ## Code Changes [Files modified with brief description] ## Open Issues - [Issue]: [Status/Context] ## Next Steps - [ ] Action item ``` Omit sections that don't apply. Add custom sections if needed.

handoff_list

List all saved handoffs with summaries. Returns lightweight metadata without full conversation content. Opens interactive UI if supported.

handoff_load

Load a specific handoff by key. Returns full conversation content.

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).

Conversation Handoff MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "conversation-handoff-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "conversation-handoff-mcp"
      ]
    }
  }
}

Scrivener MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Conversation Handoff MCP More alternatives to Scrivener MCP Knowledge & Memory category hub