sqlbroker

sqlbroker — Claude Code marketplace + plugin

Talk to MSSQL from Claude Code by alias name, never by credentials.

A local broker holds your SQL Server passwords in an encrypted file (master.key + AES-128-CBC + HMAC-SHA256). Claude calls databases by alias only — host, user, and password never enter the conversation. Cross-platform: Windows / macOS / Linux.

You:   "list databases on prod_main"
You:   "ดู proc ที่ชื่อมี _approve ใน billing_db บน prod_main"
You:   "select count(*) from t_orders where created_at > '2026-01-01' on staging_main"

The skill auto-activates on any DB-query intent and routes through the broker.

---

Quickstart

5 minutes from zero to your first SQL query.

0) Prerequisites per OS

OS	Need yourself	Auto-installed by deploy
Windows	Claude Code, admin shell access	embedded Python 3.13, ODBC Driver 18, Scheduled Task
macOS	Claude Code, python3 (brew install [email protected]), sudo	venv + pyodbc + pycryptodome, launchd plist. ODBC: brew install msodbcsql18 (manual)
Linux	Claude Code, python3 + python3-venv, sudo	venv + pyodbc + pycryptodome, systemd unit. ODBC: install msodbcsql18 from Microsoft repo (manual)

1) Install the plugin (every OS)

/plugin marketplace add creamac/sqlbroker-plugin
/plugin install sqlbroker@creamac/sqlbroker-plugin
/reload-plugins

2) Install the local service

/sqlbroker:install

Picks the right deploy script for your OS and runs it elevated.

• Windows — UAC dialog → Yes. Embedded Python + ODBC + Scheduled Task all auto-installed.
• macOS / Linux — sudo password. Uses your system python3, registers launchd plist or systemd unit.

The script ends by patching ~/.claude.json with the MCP wiring (auto-confirm with -AutoWire / --auto-wire).

3) Add your first connection

/sqlbroker:add prod_main

Claude collects host / user / db / policy in chat (policy via the AskUserQuestion form). Then it prints one command for you to run in your own terminal — getpass prompts for the password there. Password never enters the chat or shell history.

4) Use it

Just ask Claude things like:

"list_databases ของ prod_main"
"select count(*) from t_orders where created_at > '2026-01-01' on staging_main"
"เช็ค proc ที่มี audit ใน billing_db บน prod_main"
"ดู definition ของ usp_FsData_Approve_Workflow บน prod_main"
"compare definition ของ usp_X ระหว่าง staging_main กับ prod_main"

The skill auto-routes to the right MCP tool — no need to remember tool names.

---

Why?

Problem 1 — credentials leak everywhere

Without a broker, every MSSQL connection from an AI agent looks like one of these:

// ~/.claude.json — 😱 plaintext password in config
"mssql_prod": {
  "command": "uvx",
  "args": ["--from", "microsoft-sql-server-mcp", "mssql_mcp_server"],
  "env": { "MSSQL_PASSWORD": "Hunter2!", ... }
}

# Or in a chat:
> "connect to 10.0.0.5 as appuser with password Hunter2! then run..."

Both leak credentials into config files, transcripts, and shell history. sqlbroker stores the passwords once, encrypted (master.key + Fernet), and exposes only alias names through MCP — execute_sql(alias="prod_main", query="...").

Problem 2 — one MCP server per database eats tokens & config

Without a broker, every database needs its own MCP server entry:

// ~/.claude.json — 5 DBs = 5 MCP servers
"mssql_prod":      { "command": "uvx", "args": [...], "env": { ... } },
"mssql_staging":   { "command": "uvx", "args": [...], "env": { ... } },
"mssql_uat":       { "command": "uvx", "args": [...], "env": { ... } },
"mssql_dev":       { "command": "uvx", "args": [...], "env": { ... } },
"mssql_reporting": { "command": "uvx", "args": [...], "env": { ... } },

Cost:

• Each MCP server's tool list is loaded into Claude context every session
• 5 servers × ~5 tools = ~25 tool descriptions in your context every turn
• 5 separate processes spawned by Claude Code on session start
• 5 places to rotate passwords when one changes
• Every new DB = edit .claude.json, restart Claude Code

With sqlbroker — one MCP server, unlimited aliases:

// ~/.claude.json — one entry, forever
"sqlbroker": { "command": "...\\run_stdio_proxy.bat" }

# Add as many DBs as you want — no MCP changes, no restart
/sqlbroker:add prod_main
/sqlbroker:add staging_main
/sqlbroker:add uat_main
/sqlbroker:add dev_main
/sqlbroker:add reporting
# ...