SQLite MCP Server vs Supabase MCP Server
Local file database versus hosted platform. The SQLite reference server gives Claude a zero-setup database for quick experiments and local analysis, but it is archived. The Supabase server targets a hosted Postgres platform with active maintenance. Pick SQLite for throwaway local work, Supabase when the data needs to live somewhere real.
GitHub data verified 2026-07-30 — objective fields only, no editorial scoring.
| SQLite MCP Server Lightweight SQLite database integration for local data management | Supabase MCP Server Full Supabase backend integration including auth, database, and storage | |
|---|---|---|
| GitHub stars | 293 | 2,843 |
| Forks | 165 | 389 |
| Open issues | 0 | 107 |
| Last commit | 2025-05-28 | 2026-07-29 |
| Maintenance status | Archived (read-only) | Actively maintained |
| License | MIT | Apache-2.0 |
| Language | TypeScript | TypeScript |
| Install | npx @modelcontextprotocol/server-sqlite | — |
| Author | Anthropic | Supabase |
| Official listing | Yes | No |
| Community votes | 0 | 0 |
| Copies from directory | 0 | 0 |
GitHub statistics are measured at repository level; servers that live in a shared monorepo show that repository's stats. This comparison is generated from directory data — no sponsored placement, see the curation policy.