DoneThat vs IWE

In-depth architectural comparison of the DoneThat 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?

D

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

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

Feature & Specification Comparison

Specification	D DoneThat Knowledge & Memory	IWE Knowledge & Memory
Summary	Privacy-first work tracking with summaries, reports, coaching, and AI-ready long-term memory.	Markdown knowledge base as agent memory. Runs against the notes directory it is started in.
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": {
    "donethat": {
      "command": "npx",
      "args": [
        "-y",
        "donethat"
      ]
    }
  }
}

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

Related MCP Server Comparisons