Qdrant Memory vs IWE
A side-by-side look at the Qdrant Memory and IWE MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Qdrant Memory for knowledge & memory work as a local process; choose IWE for knowledge & memory over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Qdrant Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
Choose IWE when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 36/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
Qdrant Memory tools
No tool names declared yet. Check the project README from the listing page.
IWE tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Qdrant Memory
{
"mcpServers": {
"qdrant-memory": {
"command": "uvx",
"args": [
"--from",
"qdrant-memory-mcp==0.1.2",
"qdrant-memory-mcp"
]
}
}
}
IWE
{
"mcpServers": {
"iwe": {
"url": "https://iwe.md/docs/agentic/mcp/"
}
}
}
Frequently asked questions
Qdrant Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. IWE belongs to Knowledge & Memory and uses a remote HTTP/SSE transport. Pick Qdrant Memory for knowledge & memory work and IWE for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Qdrant Memory has no declared pricing — check the project's own site. IWE has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add qdrant-memory and iwe as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Qdrant Memory has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. IWE has 48/100 (Fair) with 2 views, 0 installs and 1,755 GitHub stars.