IWE vs Sw Dev Knowledge Base MCP

In-depth architectural comparison of the IWE and Sw Dev Knowledge Base MCP 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

S

Choose Sw Dev Knowledge Base MCP 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 Sw Dev Knowledge Base MCP Details

Feature & Specification Comparison

Specification	IWE Knowledge & Memory	S Sw Dev Knowledge Base MCP Knowledge & Memory
Summary	Markdown knowledge base as agent memory. Runs against the notes directory it is started in.	Read-only offline MCP server over a curated Shopware developer knowledge base
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": {
    "sw-dev-knowledge-base-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "sw-dev-knowledge-base-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons