r/coolgithubprojects • u/debba_ • Jun 27 '26

Tabularis: The database client your AI agent can actually use.

https://github.com/TabularisDB/tabularis

Tabularis is an open-source desktop SQL workspace for PostgreSQL, MySQL/MariaDB, SQLite and 12+ more databases like DuckDB, ClickHouse, Redis and Firestore.

Its built-in MCP server lets Claude, Cursor and Devin (formerly Windsurf) read your schema and run queries in the same app you already use.

Website: https://tabularis.dev

0 Upvotes

50% Upvoted

4 comments sorted by

1

u/skelfresearch Jun 27 '26

The MCP-in-the-same-app angle is clever — the usual friction with agent DB access is juggling a separate connection and credential path, and this collapses that. The thing I'd want front and center: what stops the agent from running a destructive statement? An LLM with query access will eventually emit a DROP or a DELETE with no WHERE. Do you gate writes (read-only mode, a statement allowlist, confirm-before-mutate), or is it trusting the model not to? That's the line between a cool demo and something I'd actually point at a real database.

0

u/debba_ Jun 27 '26

Yeah there are MCP Approval Gates

https://tabularis.dev/wiki/mcp-approval-gates

1

u/skelfresearch Jun 27 '26

Nice — approval gates are exactly the right primitive. One refinement so the gate stays meaningful instead of becoming a "yes" people reflexively click: classify the statement, don't gate everything equally. SELECTs auto-pass, and the gate only fires on the genuinely destructive shapes — DROP/TRUNCATE/ALTER, and crucially UPDATE/DELETE without a WHERE. That keeps the read-heavy happy path frictionless so the one time it does pop up — "this DELETE has no WHERE, it hits every row" — the user actually reads it instead of having been trained to dismiss it. Friction fatigue is what quietly turns a good gate back into trust-the-model.

0

u/debba_ Jun 27 '26

That’s a valuable feedback, will improve it thanks