IWE vs Loci

In-depth architectural comparison of the IWE and Loci 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.

Which MCP Server Should You Choose?

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

L

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

Feature & Specification Comparison

Specification	IWE Knowledge & Memory	L Loci Knowledge & Memory
Summary	Markdown knowledge base as agent memory. Runs against the notes directory it is started in.	Cross-session memory and hybrid RAG over your notes and docs. Local-first, with cited answers.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

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

{
  "mcpServers": {
    "iwe": {
      "command": "npx",
      "args": [
        "-y",
        "@iwe-org/mcp"
      ]
    }
  }
}

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

Related MCP Server Comparisons