IWE vs Scrapiq

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

Feature & Specification Comparison

Specification	IWE Knowledge & Memory	S Scrapiq Knowledge & Memory
Summary	Markdown knowledge base as agent memory. Runs against the notes directory it is started in.	Any URL to clean text, markdown, or JSON for LLM/RAG pipelines.
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": {
    "scrapiq": {
      "command": "npx",
      "args": [
        "-y",
        "scrapiq"
      ]
    }
  }
}

Related MCP Server Comparisons