Skip to content

Latest commit

 

History

212 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

omni-sql logo

omni-sql

One focused SQL workspace for every database.

A modern, open-source desktop SQL IDE for developers working across
PostgreSQL, MySQL, MariaDB, SQL Server, and Oracle.

Download omni-sql · Quick start · Database support

Runs locally · No account required · No separate runtime or database client to install

CI status Quality gate status Latest release MIT license

Explore schemas, complete SQL, inspect results, and analyze PostgreSQL execution plans

Early-stage software · Installers currently available for Windows x64 and Linux amd64

One IDE instead of a tool for each database

omni-sql brings query writing, schema exploration, execution, and results into one consistent desktop workspace. It is built for developers who move between database engines and want useful SQL intelligence without sending their schema to a hosted service.

What makes omni-sql different

Why it matters
Five native database adapters Use the same workflow with PostgreSQL, MySQL, MariaDB, SQL Server, and Oracle.
CTE-aware autocomplete Complete CTE names and projected columns alongside metadata-backed tables and columns.
Dialect intelligence Turn supported dialect diagnostics into database-compatible SQL through editor quick fixes.
Local desktop workflow Connections, metadata, queries, and results stay in the desktop application; no account is required.
Safety-minded editing Inline row edits are enabled only when primary-key checks establish a safe update path.
Ready-to-run installers Release packages bundle the required runtimes; users do not install Node.js, Java, Rust, or vendor client SDKs.

From connection to result

  1. Connect to one of the supported databases.
  2. Explore schemas, tables, columns, keys, indexes, functions, and definitions.
  3. Write in a Monaco-powered editor with metadata and CTE-aware completion.
  4. Run and analyze statements, results, messages, exports, and supported execution plans.

Database support

Database Connection Metadata autocomplete Query execution
PostgreSQL
MySQL
MariaDB
SQL Server
Oracle
Generic JDBC 🧪 Experimental Basic Limited

Generic JDBC uses a driver JAR, JDBC URL, and driver class supplied by the user. Plans, indexes, definitions, and row edits are not currently available for generic JDBC. See the database support guide for connection details and limitations.

Install

Download the package for your platform from the latest GitHub release.

Platform Package Status
Windows 10/11 x64 .exe installer Available
Debian/Ubuntu amd64 .deb package Available
macOS, ARM, AppImage, RPM Not packaged yet

Release assets include a SHA256SUMS file so downloads can be verified. End users do not need to install Node.js, Java, Rust, a database client, or a vendor client SDK.

omni-sql is early-stage software. Test it with development data before using it against important environments, and please report unexpected behavior.

Quick start

  1. Install the package for your platform.
  2. Open omni-sql and create a connection.
  3. Select a database type, enter the connection details, and choose Test connection.
  4. Configure SSL and schema settings when needed, then connect.
  5. Browse metadata or open a SQL tab and start writing.
  6. Run the selection or current statement, then inspect, filter, sort, page, or export the results.

Need help connecting? Read Database support or Troubleshooting.

Features in action

Complete columns projected by a CTE

CTE column autocomplete

omni-sql combines database metadata with the SQL in the editor to suggest columns projected by common table expressions.

Adapt SQL through a dialect quick fix

PostgreSQL dialect-transpilation quick fix Transpiled PostgreSQL query

Supported diagnostics can offer a quick fix that rewrites the statement for the active database dialect without leaving the editor.

Positioning

omni-sql is intentionally a focused SQL IDE, not a full database administration suite. It is a good fit when you value a consistent cross-database editor, local operation, CTE-aware completion, and guarded data edits. Mature tools such as DBeaver and DataGrip cover broader administration and ecosystem needs; omni-sql focuses on a smaller, modern workflow and is free and open source.

Choose omni-sql when you want… Consider a broader tool when you need…
One editor across five major relational databases Deep vendor-specific administration
CTE and metadata-aware SQL completion A large plugin ecosystem or enterprise support
A local desktop app with no account Built-in data modeling, migration, or team features
An MIT-licensed project you can inspect and contribute to An established, long-supported product

MCP integration

omni-sql includes a local MCP server that lets compatible AI clients work with the SQL tab you already have open. An assistant can read the active statement and its database context, inspect schema metadata and indexes, explain a query without executing it, or prepare an edit for review.

Review an SQL edit proposed through MCP before applying it

AI client  ──MCP/STDIO──▶  local omni-sql bridge  ──▶  active desktop tab
                                                        │
                                                        └─ proposed edits require approval
Tool What it does
getActiveSql Reads the SQL and dialect from the active tab.
getActiveConnectionContext Reads safe connection context without credentials.
getSchemaSummary Lists schemas, relations, and columns available to the active connection.
getTableIndexes Inspects indexes for one table.
explainSql Produces a non-executing query plan.
getLatestSqlExecutionError Reads the latest execution error from the active tab.
proposeSqlEdit Opens a before/after proposal that you can apply or reject in omni-sql.

The default transport is local STDIO. The generated launcher configuration is available from the MCP item in the status bar after the backend is ready. Copy its command and args exactly into your MCP client; runtime paths are temporary and are regenerated whenever omni-sql starts.

The integration cannot execute SQL, read passwords or connection strings, access files, or bypass the approval dialog. See the MCP guide for Codex, Claude Desktop, and ChatGPT Desktop setup, optional Streamable HTTP transport, verification steps, limits, and the complete security model.

Roadmap

  • ✅ Native PostgreSQL, MySQL, MariaDB, SQL Server, and Oracle adapters
  • ✅ CTE-aware autocomplete
  • 🧪 Generic JDBC (experimental)
  • 📋 ODBC
  • 📋 MongoDB (deferred to v2)
  • 📋 More installer formats and platforms

Documentation

Built with Tauri, React, Fluent UI, Monaco Editor, TypeScript, Rust, and Kotlin.

Help the project grow

If omni-sql is useful to you, star the repository to help other developers discover it. You can report a bug, share a database compatibility result, or suggest a focused improvement. Pull requests are welcome—please read CONTRIBUTING.md first.

License

MIT

About

Open-source desktop SQL IDE with CTE-aware autocomplete for PostgreSQL, MySQL, MariaDB, SQL Server, and Oracle.

Topics

Resources

Contributing

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages