What is the key difference between Nexusmem and Wyrm?

Nexusmem belongs to the Knowledge & Memory category with local stdio execution, while Wyrm belongs to the Knowledge & Memory category with local stdio execution.

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

Nexusmem operates under a Free / Open Source model (No auth required). Wyrm operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Nexusmem lists 0 tools with 0 views and 12 GitHub stars. Wyrm lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Nexusmem and Wyrm 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

Nexusmem vs Wyrm

In-depth architectural comparison of the Nexusmem and Wyrm 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

Nexusmem

Knowledge & Memory · Local stdio

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

Wyrm

Knowledge & Memory · Local stdio

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

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

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

Feature & Specification Comparison

Specification	N Nexusmem Knowledge & Memory	W Wyrm Knowledge & Memory
Summary	Local-first memory for AI coding agents: shell history with exit codes, git diffs, docs, MCP.	Persistent local-first memory for AI agents: ground truths, failure firewall, recall over MCP.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Nexusmem Tools (0)

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

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

Nexusmem Configuration

mcpServers (Claude Desktop / Cursor)

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

Wyrm Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Nexusmem More alternatives to Wyrm Knowledge & Memory category hub

Related MCP Server Comparisons

Popular comparisons with Nexusmem

Popular comparisons with Wyrm

Wyrm vs Moxie Docs MCP