Open-source desktop SQL workspace with 3 built-in database drivers and 16 shipped plugins, including SQL Server, DuckDB, ClickHouse and Redis. Built-in MCP server for Claude, Cursor and Devin, SQL notebooks and visual EXPLAIN.
What it is, and how people use it
Open-source desktop SQL workspace with 3 built-in database drivers and 16 shipped plugins, including SQL Server, DuckDB, ClickHouse and Redis. Built-in MCP server for Claude, Cursor and Devin, SQL notebooks and visual EXPLAIN. It sits on the MCP Servers shelf of the catalog, maintained by @TabularisDB.
Why builders keep it installedMCP Servers benefits
An MCP server gives your agent typed access to a browser, database, chart engine or cloud account. It acts through the server instead of hallucinating what the API would have returned.
Servers run on your machine or your cloud. Access is scoped per tool and can be cut mid-session, so credentials never live inside the model.
Cursor, Claude Desktop, Codex CLI and Windsurf all speak MCP. The config you write today keeps working when you switch editor or model.
Tool calls pass through the server, so you get a log of exactly what the agent read, wrote or clicked - the difference between a demo and something you'd run at work.
Contributorsloading from GitHub…
Languagesestimated from snapshot
- TypeScript 77.0%
- Shell 12.0%
- Rust 11.0%