Repository navigation
omni-sql v0.23.0
omni-sql v0.23.0
- MCP: agents can now work on more than the active connection. A new
listConnectionstool returns the connections exposed to MCP with their dialect, MCP access level and environment (for example Staging or Production), andgetActiveConnectionContextnow includes the environment too.executeSql,getSchemaSummary,getTableIndexesandexplainSqlaccept an optionalconnectionId. - MCP approval dialog: SQL proposed for execution now has a Run on connection selector. It starts on the connection suggested by the agent (or the active one), you can switch to any connection that allows MCP access, and the query runs on the one you pick. The dialog shows the environment, warns about Production and when the connection is not the active one, and blocks running write SQL on read-only connections.
- MCP approval dialog: suggested SQL is now shown with the editor's syntax colors instead of plain text.
- Connections with MCP access set to Off are never listed to the agent or usable through MCP.
- MCP standalone mode:
--standalone(orOMNI_SQL_MCP_STANDALONE=1) starts the MCP server over STDIO without the desktop app, so registries and clients can list its tools and schemas; every tool call reports that the desktop is not running. A Dockerfile for this mode is included inpackages/mcp-server.
Full Changelog: v0.22.4...v0.23.0