tabularis — Desktop DB Client (AI + MCP Built-In)

Main

A productive way to use tabularis for day-to-day debugging:

1. Create one connection per environment (local / staging / prod read-replica) and name them clearly.
2. Use notebooks for “investigation threads”: keep the query, the result snippet, and the conclusion together.
3. When you need another engine (DuckDB, MongoDB, etc.), use the plugin mechanism the README describes—treat drivers as modular.
4. Keep “fast-safe defaults”: start with EXPLAIN, add LIMIT, and avoid heavy scans until you’ve narrowed the target tables and indexes.

If you enable AI features, keep prompts scoped to schema + query intent, not secrets or full data dumps.

FAQ

Q: Which databases does it support? A: The README lists PostgreSQL, MySQL/MariaDB, and SQLite as first-class supported drivers.

Q: Can I add other databases? A: Yes. The README describes a plugin system to add drivers such as DuckDB or MongoDB.

Q: Is AI required? A: No. AI features are optional per README; you can use it as a normal DB client.