SQLX database tools: list saved datasources, show or test a connection, execute SQL and open a local result page, with the sqlx CLI installed on first use.
Install
# from npm (prebuilt)
dsh plugin --profile web add @ottermind/sqlx-dsh
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:OtterMind/sqlx#path:/integrations/dsh
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
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
Links
More in this category
DayuanJiang/next-ai-draw-io#dsh-plugin★ 36685
Draws draw.io diagrams in DeepSeek Harness through the next-ai-drawio MCP server: the link in the reply opens a live preview in the right sidebar, you can edit the diagram by hand, and each AI change is a version you can restore. Node.js 18+; npx downloads the MCP server on first use.
Tencent/WeKnora#dsh-weknora★ 36302
Four read-only tools over a WeKnora knowledge base: list knowledge bases, hybrid passage search, reassemble one document's chunks in order, and WeKnora's own cited RAG or ReAct-agent answer with a resumable session id.
superdesigndev/treg★ 7042
Tool catalog for agents: search ~2,600 external endpoints (SEO and SERP, backlinks, social, people and company enrichment, ad libraries, scraping) by the task you want done, read each one's parameters and per-call price, then call it with the credential injected server-side. Ships the skill plus an MCP row that stays disabled until TREG_TOKEN is set.
T-Auto/dsh-ops★ 5074
Provides bash, PowerShell 7, and high-performance Rust tools for DSH on Windows to reduce token usage.
sixtysevenlf/dsh-blender-plugin★ 1575
Lets a DSH agent drive a local Blender over a direct TCP channel with 15 tools: viewport frames, custom-angle renders, Python execution, headless and job offload, transaction rollback, and a planning layer of 228 ops across 34 families.
TencentCloudBase/CloudBase-AI-Toolkit#dsh-plugin★ 1155
Tencent CloudBase backend for DeepSeek Harness — scaffold and deploy full-stack apps from chat, render query results as table cards with paging, sorting and CSV export, preview a deployment on its domain, and call the CloudBase MCP toolset (`mcp__cloudbase__*`) with device-code login.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.