Rms Memory MCP vs Scrivener MCP

In-depth architectural comparison of the Rms Memory 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.

Which MCP Server Should You Choose?

Choose Rms Memory 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: Local project-isolated Markdown vaults, LanceDB vector and Tantivy full-text retrieval, Optional Tree-sitter code indexing.

Explore Rms Memory 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.

Feature & Specification Comparison

Specification	Rms Memory MCP max-ramas Knowledge & Memory	Scrivener MCP writerslogic Knowledge & Memory
Summary	Local-first persistent memory for AI coding agents. Hybrid vector + full-text search (LanceDB + Tantivy), separate Markdown and Tree-sitter code indexes, per-project isolated vaults shared across IDEs (Cursor, Zed, Claude Code, Codex), bounded recall with abstain-on-low-confidence.	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

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

{
  "mcpServers": {
    "max-ramas-rms-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "max-ramas-rms-memory-mcp"
      ]
    }
  }
}

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

Related MCP Server Comparisons