What is the key difference between WorkingMemory and Collective Memory?

WorkingMemory belongs to the Knowledge & Memory category with cloud HTTP/SSE execution, while Collective Memory belongs to the Knowledge & Memory category with local stdio execution.

How do I install WorkingMemory or Collective Memory 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 WorkingMemory and Collective Memory free or paid?

WorkingMemory operates under a Free / Open Source model (No auth required). Collective Memory operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

WorkingMemory lists 0 tools with 0 views and 0 GitHub stars. Collective Memory lists 0 tools with 0 views and 0 GitHub stars.

Can I use both WorkingMemory and Collective Memory 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.

How do I install WorkingMemory or Collective Memory in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are WorkingMemory and Collective Memory free to use, or do they require API keys?

WorkingMemory is listed under a Free / Open Source model with No auth required . Collective Memory operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both WorkingMemory and Collective Memory at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both workingmemory and collective-memory as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, WorkingMemory has a Quality Score of 42 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars. Collective Memory holds a Quality Score of 39 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

WorkingMemory vs Collective Memory

In-depth architectural comparison of the WorkingMemory and Collective Memory 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

WorkingMemory

Knowledge & Memory · Remote HTTP/SSE

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

Collective Memory

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose WorkingMemory if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Collective Memory 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 WorkingMemory when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore WorkingMemory Details

Choose Collective Memory 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 Collective Memory Details

Feature & Specification Comparison

Specification	W WorkingMemory Knowledge & Memory	C Collective Memory Knowledge & Memory
Summary	Persistent personal memory for AI assistants — save, search, and recall across every MCP client.	MCP server for persistent, semantic memory across AI sessions
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

WorkingMemory Tools (0)

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

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

WorkingMemory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "workingmemory": {
      "url": "https://workingmemory.ai"
    }
  }
}

Collective Memory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "collective-memory": {
      "command": "npx",
      "args": [
        "collective-memory"
      ]
    }
  }
}

Frequently Asked Questions

WorkingMemory is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Collective Memory belongs to Knowledge & Memory using local stdio subprocess. Select WorkingMemory when you need capabilities focused on knowledge & memory and Collective Memory when you require tools for knowledge & memory.

More alternatives to WorkingMemory More alternatives to Collective Memory Knowledge & Memory category hub Canonical compare URL

Related MCP Server Comparisons

Popular comparisons with WorkingMemory

Popular comparisons with Collective Memory

Collective Memory vs Moxie Docs MCP