IWE vs Screvi

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

Explore Screvi Details

Feature & Specification Comparison

Specification	IWE Knowledge & Memory	S Screvi Knowledge & Memory
Summary	Markdown knowledge base as agent memory. Runs against the notes directory it is started in.	Search and organize your reading library of highlights, saved articles, notes and tags.
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": {
    "screvi": {
      "url": "https://screvi.com/mcp"
    }
  }
}

Related MCP Server Comparisons