What is the key difference between Zipmem MCP and Moxie Docs MCP?

Zipmem MCP belongs to the Knowledge & Memory category with local stdio execution, while Moxie Docs MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Zipmem MCP or Moxie Docs 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 Zipmem MCP and Moxie Docs MCP free or paid?

Zipmem MCP operates under a Free / Open Source model (No auth required). Moxie Docs MCP operates under a Freemium model (API Key required).

Which MCP server has more tools and community activity?

Zipmem MCP lists 3 tools with 2 views and 0 GitHub stars. Moxie Docs MCP lists 12 tools with 21 views and 2 GitHub stars.

Can I use both Zipmem MCP and Moxie Docs 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

Zipmem MCP vs Moxie Docs MCP

In-depth architectural comparison of the Zipmem MCP and Moxie Docs 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

Zipmem MCP

Knowledge & Memory · Local stdio

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

Moxie Docs MCP

Knowledge & Memory · Local stdio

Quality: 82/100 (Excellent) | Auth: API Key required

Verdict Summary: Choose Zipmem MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Moxie Docs 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 Zipmem 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).
You have access to required keys: CLAUDE_PROJECT_DIR.
Primary tools included: zipmem_load_memory, zipmem_save_and_compact, zipmem_checkpoint.

Explore Zipmem MCP Details

Choose Moxie Docs MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
Primary tools included: moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.

Explore Moxie Docs MCP Details

Feature & Specification Comparison

Specification	Zipmem MCP ahmetakyurt Knowledge & Memory	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory
Summary	Local-first long-term memory for terminal AI agents (Claude Code et al.) via Anchored Compacting. Stores blueprints, code anchors (file→line→concept), and distilled lessons in a single JSON under .zipmem/, restoring full cross-session project context at near-zero token cost. No DB, no API keys, no embeddings. npx zipmem-mcp	MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Tools & Capabilities Breakdown

Zipmem MCP Tools (3)

zipmem_load_memory

Load this project's compressed long-term memory. CALL THIS FIRST, at the very start of every session, before doing anything else. Returns architectural blueprints, file-coordinate anchors, and lessons learned from previous sessions so you regain full context at near-zero token cost.

zipmem_save_and_compact

Compress the current session and merge it into long-term memory. CALL THIS when the user signals they are done (exit/quit/goodbye/wrap up) OR when you sense your context window is nearing capacity. Provide your work as structured sections: blueprints (verbatim architecture/schemas/decisions), anchors (file coordinates instead of raw code), and lessons (distilled bug fixes). Never include raw code blocks — use anchors.

zipmem_checkpoint

Stage incremental progress for crash-safety. Call this PERIODICALLY during a session — after each meaningful unit of work (a feature wired up, a bug fixed, a decision made) — so that an abrupt exit (Ctrl+C, a closed terminal, a crash) never loses more than the last few steps. It is cheap and does NOT finalize the session: pass the same structured fields as save_and_compact (blueprints/anchors/lessons + a running summary). The data is buffered durably and folded into memory automatically on the next session if the current one ends without a clean compaction.

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

Zipmem MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ahmetakyurt-zipmem-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "zipmem-mcp"
      ],
      "env": {
        "CLAUDE_PROJECT_DIR": "YOUR_CLAUDE_PROJECT_DIR_HERE"
      }
    }
  }
}

Moxie Docs MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "moxie-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "moxie-docs"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Zipmem MCP More alternatives to Moxie Docs MCP Knowledge & Memory category hub