By creamac
Alias-based MSSQL broker for Claude Code. Cross-platform: Task Scheduler / systemd / launchd. Three auth modes: SQL / Windows Auth / Azure AD SPN. 14 MCP tools — schema introspection (list_objects, get_definition, get_table_schema, get_dependencies, find_in_definitions, find_in_columns, get_proc_params, compare_definitions), data (preview_table, execute_sql), runtime (get_server_info, get_active_queries, list_databases, list_aliases) — plus connection pool, master.key encryption, and three auth modes.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Add a new MSSQL connection alias (interactive)
Diff the source code of an object across two aliases (or two databases)
Install the mcp-sqlbroker service (Windows / macOS / Linux)
List all configured SQL connection aliases
Remove an SQL connection alias
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.
5 minutes from zero to your first SQL query.
| 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) |
/plugin marketplace add creamac/sqlbroker-plugin
/plugin install sqlbroker@creamac/sqlbroker-plugin
/reload-plugins
/sqlbroker:install
Picks the right deploy script for your OS and runs it elevated.
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).
/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.
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.
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="...").
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:
.claude.json, restart Claude CodeWith 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
# ...
npx claudepluginhub creamac/sqlbroker-plugin --plugin sqlbrokerComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.