MCP Server Qdrant vs MCP Redis
A side-by-side look at the MCP Server Qdrant and MCP Redis MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Qdrant for databases work as a local process; choose MCP Redis for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server Qdrant when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
QDRANT_URL, QDRANT_API_KEY, QDRANT_LOCAL_PATH, COLLECTION_NAME, EMBEDDING_PROVIDER, EMBEDDING_MODEL, QDRANT_SEARCH_LIMIT, QDRANT_READ_ONLY. - You want tools like
information, metadata, collection_name.
Choose MCP Redis when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
string, hash, list.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 79/100 · Great | 81/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | other |
| Pricing | Free | Free |
| Required env vars | QDRANT_URLQDRANT_API_KEYQDRANT_LOCAL_PATHCOLLECTION_NAMEEMBEDDING_PROVIDEREMBEDDING_MODELQDRANT_SEARCH_LIMITQDRANT_READ_ONLY | None listed |
| Verified owner | Verified | Verified |
| GitHub stars | 1,552 | 638 |
| Directory activity | 6 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | 4 | 8 |
| Full listing | View MCP Server Qdrant | View MCP Redis |
Tools & capabilities
MCP Server Qdrant tools 4
informationmetadatacollection_namequery
MCP Redis tools 8
stringhashlistsetstreamsJSONdocsMCP_DOCS_SEARCH_URL
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.
MCP Server Qdrant
{
"mcpServers": {
"qdrant-mcp-server-qdrant": {
"command": "uvx",
"args": [
"mcp-server-qdrant"
],
"env": {
"QDRANT_URL": "YOUR_QDRANT_URL_HERE",
"QDRANT_API_KEY": "YOUR_QDRANT_API_KEY_HERE",
"QDRANT_LOCAL_PATH": "YOUR_QDRANT_LOCAL_PATH_HERE",
"COLLECTION_NAME": "YOUR_COLLECTION_NAME_HERE",
"EMBEDDING_PROVIDER": "YOUR_EMBEDDING_PROVIDER_HERE",
"EMBEDDING_MODEL": "YOUR_EMBEDDING_MODEL_HERE",
"QDRANT_SEARCH_LIMIT": "YOUR_QDRANT_SEARCH_LIMIT_HERE",
"QDRANT_READ_ONLY": "YOUR_QDRANT_READ_ONLY_HERE"
}
}
}
}
MCP Redis
{
"mcpServers": {
"redis-mcp-redis": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/redis/mcp-redis.git@0.2.0",
"redis-mcp-server"
]
}
}
}
Frequently asked questions
MCP Server Qdrant is categorized under Databases and uses a local stdio subprocess. MCP Redis belongs to Databases and uses a local stdio subprocess. Pick MCP Server Qdrant for databases work and MCP Redis for databases.
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.
MCP Server Qdrant is listed as free. Auth: api key required. MCP Redis is listed as free. Auth: other. 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-mcp-server-qdrant and redis-mcp-redis as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Qdrant has a quality signal of 79/100 (Great) with 6 views, 0 installs and 1,552 GitHub stars. MCP Redis has 81/100 (Excellent) with 7 views, 0 installs and 638 GitHub stars.