MCP SQLite (jparkerweb) vs SQLite (reference, archived)
Both are databases & vector stores MCP servers, and we ran both through the same test (roundtrip) in each app. MCP SQLite (jparkerweb) passed 4 of 4 apps we tested it in; SQLite (reference, archived) passed 0 of 3.
Test results side by side
| MCP SQLite (jparkerweb) | SQLite (reference, archived) | |
|---|---|---|
| Claude Code | Passed 2026-10-15 | Failed 2026-10-15 |
| Cursor | Passed 2026-10-15 | Failed 2026-10-15 |
| Claude Desktop | Passed 2026-10-18 | Not tested yet |
| ChatGPT (Codex) | Passed 2026-10-19 | Failed 2026-10-21 |
| Tools exposed (protocol check) | 8 tools | — |
| GitHub stars | 129 | 305 |
| License | MIT | MIT |
| Last push | 2026-04-05 | 2025-05-28 |
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
MCP SQLite (jparkerweb): Reads and writes a local SQLite database: tables, schema, inserts, updates and custom queries.
SQLite (reference, archived): The original reference SQLite server: run queries on a local SQLite file. Now in the archived reference servers repo.
