DBHub vs Qdrant MCP
Both are databases & vector stores MCP servers, and we ran both through the same test (roundtrip) in each app. DBHub passed 4 of 4 apps we tested it in; Qdrant MCP passed 4 of 4.
Test results side by side
| DBHub | Qdrant MCP | |
|---|---|---|
| Claude Code | Passed 2026-10-21 | Passed 2026-10-20 |
| Cursor | Passed 2026-10-21 | Passed 2026-10-20 |
| Claude Desktop | Passed 2026-10-22 | Passed 2026-10-19 |
| ChatGPT (Codex) | Passed 2026-10-22 | Passed 2026-10-20 |
| Tools exposed (protocol check) | 2 tools | 2 tools |
| GitHub stars | 3,673 | 1,549 |
| License | MIT | Apache-2.0 |
| Last push | 2026-10-13 | 2026-09-04 |
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
DBHub: Lightweight database MCP server from Bytebase for Postgres, MySQL, SQL Server, MariaDB, Oracle and SQLite, built to keep token use low.
Qdrant MCP: Qdrant's official server: store and semantically search memories in a Qdrant collection, locally or on Qdrant Cloud.
