What is the key difference between Mwe Mcp — Memory Wiki Engine and Locus?

Mwe Mcp — Memory Wiki Engine belongs to the Knowledge & Memory category with cloud HTTP/SSE execution, while Locus belongs to the Knowledge & Memory category with local stdio execution.

How do I install Mwe Mcp — Memory Wiki Engine or Locus 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 Mwe Mcp — Memory Wiki Engine and Locus free or paid?

Mwe Mcp — Memory Wiki Engine operates under a Free / Open Source model (No auth required). Locus operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Mwe Mcp — Memory Wiki Engine lists 0 tools with 0 views and 5 GitHub stars. Locus lists 0 tools with 1 views and 0 GitHub stars.

Can I use both Mwe Mcp — Memory Wiki Engine and Locus 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 Mwe Mcp — Memory Wiki Engine or Locus 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 Mwe Mcp — Memory Wiki Engine and Locus free to use, or do they require API keys?

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

Yes! MCP clients support multi-server orchestration. You can include both mwe-mcp-memory-wiki-engine and locus 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, Mwe Mcp — Memory Wiki Engine has a Quality Score of 41 /100 ( Fair ) with 0 views, 0 installs, and 5 GitHub stars. Locus holds a Quality Score of 36 /100 ( Fair ) with 1 views, 0 installs, and 0 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Mwe Mcp — Memory Wiki Engine vs Locus

In-depth architectural comparison of the Mwe Mcp — Memory Wiki Engine and Locus 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

Mwe Mcp — Memory Wiki Engine

Knowledge & Memory · Remote HTTP/SSE

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

Locus

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Mwe Mcp — Memory Wiki Engine if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Locus 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 Mwe Mcp — Memory Wiki Engine 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 Mwe Mcp — Memory Wiki Engine Details

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

Feature & Specification Comparison

Specification	M Mwe Mcp — Memory Wiki Engine Knowledge & Memory	L Locus Knowledge & Memory
Summary	Self-hosted multi-user memory for AI agents: a human-readable Markdown wiki with per-fragment ACL.	Hierarchical markdown memory palace for AI agents — structured palace navigation via MCP tools.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Mwe Mcp — Memory Wiki Engine Tools (0)

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

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

Mwe Mcp — Memory Wiki Engine Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mwe-mcp-memory-wiki-engine": {
      "url": "https://img.shields.io/badge/license-AGPL--3.0-blue.svg)](#license"
    }
  }
}

Locus Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "locus": {
      "command": "uvx",
      "args": [
        "locus-mcp"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Mwe Mcp — Memory Wiki Engine More alternatives to Locus Knowledge & Memory category hub Canonical compare URL