Marketplace for trusted AI agent skills

Skill Detail

Let agents draft and manage Bdash SQL queries through MCP

Connect Bdash's SQL workspace to MCP clients so an agent can list configured data sources and write SQL into the active query editor for supervised analysis.

Data Extraction & TransformationMCP
Data Extraction & Transformation MCP Security Reviewed
⭐ 1.5k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill let-agents-draft-and-manage-bdash-sql-queries-through-mcp Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
View source
At a glance
Tools required
Bdash desktop app, bundled Bdash MCP server, Node.js, Claude Code or another MCP-compatible client
Install & setup
Install Bdash from the project website or GitHub Releases. For MCP use, build or use the bundled MCP server, then add it to the MCP host with command node and args pointing to src/mcp/dist/server.js for development or /Applications/Bdash.app/Contents/Resources/mcp/server.js for the macOS app.
Author
bdash-app
Publisher
Organization
Last updated
Jul 19, 2026
Quick brief

Use Bdash when an agent needs to help with lightweight SQL analysis while the human keeps control of the desktop SQL client. The operator configures Bdash data sources, registers the bundled MCP server with Claude Code or another MCP host, and lets the agent list data sources and write candidate SQL into Bdash’s editor for review, charting, sharing, and execution. The boundary is supervised query drafting and SQL-workspace handoff through Bdash MCP, not general database administration or a generic SQL client listing.

How it works

What this skill actually does

Inputs and prerequisites: Bdash desktop app, bundled Bdash MCP server, Node.js, Claude Code or another MCP-compatible client.

Setup notes: Install Bdash from the project website or GitHub Releases. For MCP use, build or use the bundled MCP server, then add it to the MCP host with command node and args pointing to src/mcp/dist/server.js for development or /Applications/Bdash.app/Contents/Resources/mcp/server.js for the macOS app.

Source and verification boundary: use https://github.com/bdash-app/bdash as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.