sqlx-dsh
Verified@ottermind/sqlx-dsh Β· v0.1.22 Β· LicenseRef-Chat2DB
OtterMind SQLX tools for DeepSeek Harness: list datasources, test connections, execute SQL and open local result pages.
Install
dsh plugin add @ottermind/sqlx-dsh Confirm the layer applied with dsh --profile default --dump-config β see the install guide.
Source
Creators
Readme
@ottermind/sqlx-dsh
Native SQLX tools for DeepSeek Harness. The plugin registers six defineTool tools and calls the
sqlx CLI for each one, so encrypted credentials, TLS policy, worker downloads and local result
pages stay CLI responsibilities.
Install
dsh plugin --profile <profile> add @ottermind/sqlx-dsh
cordis.patch.yml is declared as dsh.bundle.patch, so installing the package appends the plugin
row to the profile's bundle stack; no profile file edits are needed. Remove it with
dsh plugin --profile <profile> remove @ottermind/sqlx-dsh.
Requirements
- DeepSeek Harness 0.1.5 or later, including the 0.2.0 release candidates.
@deepseek-ai/dsh-tools(peer dependency) β bundled with dsh, and the profile installer runs pnpm withautoInstallPeers: false, so nothing extra is installed. The peer range covers>=0.1.5-rc.1 <0.2.0,>=0.1.6-alpha.1 <0.2.0-0and>=0.2.0-rc.1 <0.3.0-0; the plugin uses onlydefineToolandctx.tools.register, which are unchanged in 0.2.- The
sqlxCLI 0.1.15 or later. The plugin looks forSQLX_BIN, thensqlxonPATH, then the official user-level installation (~/.local/bin/sqlx,%LOCALAPPDATA%\Programs\SQLX\sqlx.exe, orSQLX_INSTALL_DIR), and when none of them exists it installs the CLI itself withnpx -y @ottermind/sqlx@latest --target dsh. Adding the plugin is therefore the only setup step.
Tools
| Tool | Purpose | May modify data |
|---|---|---|
sqlx_datasource_list |
List saved datasources (no secrets) | no |
sqlx_datasource_show |
Show one datasource by UUID or unique name | no |
sqlx_datasource_test |
Test connectivity; executes no SQL | no |
sqlx_datasource_setup |
Start adding a datasource the user finishes in a browser page; returns that page's URL | adds a connection |
sqlx_datasource_setup_status |
Report the outcome of a browser setup; read-only | no |
sqlx_sql_execute |
Execute statements, return the table-shaped result with a preview (full returns every row) |
yes |
sqlx_results_rows |
Read one page of a stored result; read-only | no |
sqlx_sql_view |
Execute once, return a local result-page URL | yes |
sqlx_prefetch |
Download components ahead of a first query (all fetches every one) |
downloads only |
The two execution tools describe the authorization rule themselves: run them only after the user authorized that exact operation and scope. Results are never replayed automatically.
Unlike the MCP server, these definitions carry no approval metadata: defineTool has no annotation
field, so the rule above is a description the model is asked to follow rather than something dsh
enforces. A deployment that needs an enforced prompt can gate the two execution tools from a
tools/pre-execute handler.
Credentials
Save credentials in the SQLX data directory (sqlx datasource add --connection-stdin, or the local
sqlx ui page). A datasource created with --username-env/--password-env reads environment
variables at execution time, and a harness started from a GUI usually cannot see your shell
environment.
Links
- Repository: https://github.com/OtterMind/sqlx
- Integration guide: https://github.com/OtterMind/sqlx/blob/main/integrations/README.md