What is the key difference between MCP AutoMem and Memdocs?

MCP AutoMem belongs to the Knowledge & Memory category with local stdio execution, while Memdocs belongs to the Knowledge & Memory category with local stdio execution.

How do I install MCP AutoMem or Memdocs 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 MCP AutoMem and Memdocs free or paid?

MCP AutoMem operates under a Free / Open Source model (No auth required). Memdocs operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

MCP AutoMem lists 0 tools with 0 views and 64 GitHub stars. Memdocs lists 0 tools with 0 views and 1 GitHub stars.

Can I use both MCP AutoMem and Memdocs 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

MCP AutoMem vs Memdocs

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

MCP AutoMem

Knowledge & Memory · Local stdio

Quality: 43/100 (Fair) | Auth: No auth required

Memdocs

Knowledge & Memory · Local stdio

Quality: 36/100 (Fair) | Auth: No auth required

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

Explore MCP AutoMem Details

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

Explore Memdocs Details

Feature & Specification Comparison

Specification	M MCP AutoMem Knowledge & Memory	M Memdocs Knowledge & Memory
Summary	Graph-vector memory for AI assistants using FalkorDB and Qdrant	Git-native project memory for AI assistants with enterprise-grade audit compliance
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

MCP AutoMem Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Memdocs Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

MCP AutoMem Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-automem": {
      "command": "npx",
      "args": [
        "-y",
        "@verygoodplugins/mcp-automem"
      ]
    }
  }
}

Memdocs Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "memdocs": {
      "command": "uvx",
      "args": [
        "memdocs"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to MCP AutoMem More alternatives to Memdocs Knowledge & Memory category hub