Engrava vs MCP Server Qdrant
A side-by-side look at the Engrava and MCP Server Qdrant MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Engrava for databases work as a local process; choose MCP Server Qdrant 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 Engrava when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 40/100 · Fair | 79/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | QDRANT_URLQDRANT_API_KEYQDRANT_LOCAL_PATHCOLLECTION_NAMEEMBEDDING_PROVIDEREMBEDDING_MODELQDRANT_SEARCH_LIMITQDRANT_READ_ONLY |
| Verified owner | Community listing | Verified |
| GitHub stars | 1 | 1,552 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Engrava | View MCP Server Qdrant |
Tools & capabilities
Engrava tools
No tool names declared yet. Check the project README from the listing page.
MCP Server Qdrant tools 4
informationmetadatacollection_namequery
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.
Engrava
{
"mcpServers": {
"engrava": {
"command": "uvx",
"args": [
"engrava-mcp"
]
}
}
}
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"
}
}
}
}
Frequently asked questions
Engrava is categorized under Databases and uses a local stdio subprocess. MCP Server Qdrant belongs to Databases and uses a local stdio subprocess. Pick Engrava for databases work and MCP Server Qdrant 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.
Engrava has no declared pricing — check the project's own site. MCP Server Qdrant is listed as free. Auth: api key required. 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 engrava and qdrant-mcp-server-qdrant as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Engrava has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. MCP Server Qdrant has 79/100 (Great) with 6 views, 0 installs and 1,552 GitHub stars.