What is the key difference between Exomem and Loreweave?

Exomem belongs to the Knowledge & Memory category with local stdio execution, while Loreweave belongs to the Knowledge & Memory category with local stdio execution.

How do I install Exomem or Loreweave 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 Exomem and Loreweave free or paid?

Exomem operates under a Free / Open Source model (No auth required). Loreweave operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Exomem lists 0 tools with 1 views and 10 GitHub stars. Loreweave lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Exomem and Loreweave 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

Exomem vs Loreweave

In-depth architectural comparison of the Exomem and Loreweave 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

Exomem

Knowledge & Memory · Local stdio

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

Loreweave

Knowledge & Memory · Local stdio

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

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

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

Feature & Specification Comparison

Specification	Exomem Knowledge & Memory	Loreweave Knowledge & Memory
Summary	Local Markdown/Obsidian knowledge substrate for MCP agents with governed memory and hybrid search.	Durable agent memory over a markdown vault: bitemporal facts, timelines, hybrid graph search.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Exomem Tools (0)

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

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

Exomem Configuration

mcpServers (Claude Desktop / Cursor)

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

Loreweave Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Exomem More alternatives to Loreweave Knowledge & Memory category hub