MedXpert 图书馆连接器（通用版） vs IWE

In-depth architectural comparison of the MedXpert 图书馆连接器（通用版） 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?

M

Choose MedXpert 图书馆连接器（通用版） 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 MedXpert 图书馆连接器（通用版） 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	M MedXpert 图书馆连接器（通用版） Knowledge & Memory	IWE Knowledge & Memory
Summary	Local RAG MCP server for your own .md knowledge base: BM25 + local Ollama, offline, zero egress.	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": {
    "medxpert": {
      "command": "npx",
      "args": [
        "-y",
        "medxpert"
      ]
    }
  }
}

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

Related MCP Server Comparisons