Qdrant MCP vs MCP SQLite (jparkerweb)
Both are databases & vector stores MCP servers, and we ran both through the same test (roundtrip) in each app. Qdrant MCP passed 4 of 4 apps we tested it in; MCP SQLite (jparkerweb) passed 4 of 4.
Test results side by side
| Qdrant MCP | MCP SQLite (jparkerweb) | |
|---|---|---|
| Claude Code | Passed 2026-10-20 | Passed 2026-10-15 |
| Cursor | Passed 2026-10-20 | Passed 2026-10-15 |
| Claude Desktop | Passed 2026-10-19 | Passed 2026-10-18 |
| ChatGPT (Codex) | Passed 2026-10-20 | Passed 2026-10-19 |
| Tools exposed (protocol check) | 2 tools | 8 tools |
| GitHub stars | 1,549 | 129 |
| License | Apache-2.0 | MIT |
| Last push | 2026-09-04 | 2026-04-05 |
Results from our own harness runs, dated per cell. Stars and last push from GitHub at our last data refresh. We don’t pick a winner here: which one fits depends on your app and setup.
What each does
Qdrant MCP: Qdrant's official server: store and semantically search memories in a Qdrant collection, locally or on Qdrant Cloud.
MCP SQLite (jparkerweb): Reads and writes a local SQLite database: tables, schema, inserts, updates and custom queries.
