What is the key difference between Collective Memory and Lex?

Collective Memory belongs to the Knowledge & Memory category with local stdio execution, while Lex belongs to the Knowledge & Memory category with local stdio execution.

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

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

Which MCP server has more tools and community activity?

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

Can I use both Collective Memory and Lex 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 Collective Memory or Lex 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 Collective Memory and Lex free to use, or do they require API keys?

Collective Memory is listed under a Free / Open Source model with No auth required . Lex 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 Collective Memory and Lex at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both collective-memory and lex 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, Collective Memory has a Quality Score of 39 /100 ( Fair ) with 0 views, 0 installs, and 0 GitHub stars. Lex holds a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Collective Memory vs Lex

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

Collective Memory

Knowledge & Memory · Local stdio

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

Lex

Knowledge & Memory · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

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

Choose Lex 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 Lex Details

Feature & Specification Comparison

Specification	C Collective Memory Knowledge & Memory	L Lex Knowledge & Memory
Summary	MCP server for persistent, semantic memory across AI sessions	Episodic memory and architectural policy for AI agents. Frames, Atlas, and Policy.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Collective Memory Tools (0)

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

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

Collective Memory Configuration

mcpServers (Claude Desktop / Cursor)

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

Lex Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "lex": {
      "command": "npx",
      "args": [
        "-y",
        "lex"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Collective Memory More alternatives to Lex Knowledge & Memory category hub

Related MCP Server Comparisons

Popular comparisons with Collective Memory

Popular comparisons with Lex

Lex vs Moxie Docs MCP