Connapse vs IWE

In-depth architectural comparison of the Connapse and IWE 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 Connapse 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).
• You have access to required keys: CONNAPSE_ADMIN_EMAIL, CONNAPSE_ADMIN_PASSWORD.
• Primary tools included: 11 MCP tools for containers, files, documents, and search, Semantic, keyword, and hybrid knowledge search, Container-isolated indexes.

Explore Connapse Details

Choose IWE 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).
• Primary tools included: Connects agents to a local Markdown notes directory, Reads and writes persistent project memory, Searches existing notes and prior decisions.

Feature & Specification Comparison

Specification	Connapse Destrayon Knowledge & Memory	IWE Knowledge & Memory
Summary	⃣ 🏠 🍎 🪟 🐧 - Self-hosted knowledge backend for AI agents with hybrid vector + keyword search, container-isolated indexes, and 11 MCP tools. .NET, Docker-ready.	Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
Category & Scope	Knowledge & Memory

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": {
    "destrayon-connapse": {
      "url": "http://localhost:5001/mcp"
    }
  }
}

{
  "mcpServers": {
    "iwe": {
      "url": "https://iwe.md/docs/agentic/mcp/"
    }
  }
}

Related MCP Server Comparisons