Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
DBATOOLS_SAFE_MODE=<value> MAX_OUTPUT_ROWS=<value> COMMAND_TIMEOUT_SECONDS=<value> PWSH_EXE=<value> claude mcp add io.github.dataplat-dbatools-mcp-server -- npx -y dbatools-mcp-server@0.5.0รันในเทอร์มินัล
{ "mcpServers": { "io.github.dataplat-dbatools-mcp-server": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "DBATOOLS_SAFE_MODE": "<value>", "MAX_OUTPUT_ROWS": "<value>", "COMMAND_TIMEOUT_SECONDS": "<value>", "PWSH_EXE": "<value>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดA Model Context Protocol (MCP) server for the dbatools PowerShell module.
Exposes dbatools commands as MCP tools so AI assistants (GitHub Copilot, Claude, etc.) can discover, explain, and execute dbatools commands directly — with all metadata sourced from dbatools' own comment-based help.
list_dbatools_commands — search commands by verb, noun, keyword, or risk levelget_dbatools_command_help — full normalized help (synopsis, parameters, examples) from Get-Help -Fullinvoke_dbatools_command — execute any dbatools command with safe parameter validation, risk gating, and structured JSON outputcheck_dbatools_environment — verify PowerShell + dbatools installation, index freshness, and version alignmentreadOnlyHint / destructiveHint / idempotentHint / openWorldHint so MCP clients (e.g. VS Code) can surface risk in the UI before a tool is even calleddbatools://command/{name} to read any command's full normalized help as structured JSON, independent of the chat-oriented tool responsesinvoke_dbatools_command reuses one long-lived pwsh process with dbatools pre-imported instead of spawning (and re-importing dbatools into) a fresh process on every callconfirm: true to executeSqlCredential: { username, password } for SQL auth instancespwsh)Install-Module dbatools -Scope CurrentUser
# 1. Clone the repo
git clone https://github.com/Dataplat/dbatools-mcp-server.git
cd dbatools-mcp-server
# 2. Install Node dependencies
npm install
# 3. Generate the help index from your local dbatools installation
npm run refresh-help
# 4. Build
npm run build
Then open the folder in VS Code — the .vscode/mcp.json file automatically registers the MCP server.
The included .vscode/mcp.json registers the server as a local STDIO MCP server.
Open this folder in VS Code and the server will appear in the GitHub Copilot MCP panel.
{
"servers": {
"dbatools": {
"type": "stdio",
"command": "node",
"args": ["${workspaceFolder}/dist/server.js"],
"env": {
"DBATOOLS_SAFE_MODE": "true",
"MAX_OUTPUT_ROWS": "100",
"COMMAND_TIMEOUT_SECONDS": "60"
}
}
}
}
All settings are controlled via environment variables (set in .vscode/mcp.json or your shell):
The help index (generated/dbatools-help.json) is generated from your locally installed dbatools module.
Re-run whenever dbatools is updated:
Update-Module dbatools -Scope CurrentUser
npm run refresh-help
The server detects version mismatches at runtime and warns you when the index is stale.
Commands are automatically classified by verb:
Each risk tier maps to standard MCP tool annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint), so compatible clients can surface risk in their UI before a tool is even invoked. invoke_dbatools_command is a generic dispatcher that can run any command, so its annotation conservatively reflects the worst case (destructiveHint: true) — the actual per-command risk is still enforced at runtime by the safe-mode gate.
Besides the four tools, the server exposes every indexed command as an MCP resource at dbatools://command/{name} (e.g. dbatools://command/Get-DbaDatabase), returning the same normalized help record as structured JSON — useful for clients that browse/ground on resources rather than calling a tool. The browsable resource list excludes PowerShell aliases (e.g. Attach-DbaDatabase, an alias for Mount-DbaDatabase) since they just forward to another command's help.
By default, invoke_dbatools_command reuses a single long-lived pwsh process with dbatools pre-imported, instead of spawning a fresh process (and re-importing dbatools) on every call. This removes the ~1-2s+ process-startup and module-import cost from every invocation after the first.
A couple of things to be aware of:
Connect-DbaInstance) within a PowerShell session. With a persistent session, that caching is now visible across tool calls within one MCP server run, where previously every call was fully isolated. Each individual script still runs in its own scope, so plain variables never leak between calls — only dbatools' own internal caching behavior is affected.Set DBATOOLS_PERSISTENT_SESSION=false to disable this and go back to one fresh process per call.
For SQL-auth-only instances (e.g. Docker), pass credentials via the SqlCredential parameter:
{
"SqlInstance": "localhost,1433",
"SqlCredential": { "username": "<SqlLogin>", "password": "YourPassword" }
}
dbatools-mcp-server/
├── src/
│ ├── server.ts # MCP server entry point, tool/resource definitions
│ ├── powershell.ts # One-shot PowerShell process runner, health checks, version detection
│ ├── powershell-session.ts # Persistent PowerShell session (long-lived process, dbatools pre-imported)
│ ├── help-indexer.ts # Help manifest loader and command search
│ ├── tool-registry.ts # Risk classification, tool annotations, safe argument builder
│ └── types.ts # Shared TypeScript interfaces
├── scripts/
│ └── refresh-help.ps1 # Generates generated/dbatools-help.json
├── generated/ # Help index (gitignored, generated locally)
├── .vscode/
│ └── mcp.json # VS Code MCP local server registration
└── dist/ # Compiled output (gitignored)
Contributions are welcome! Please open an issue first for significant changes.
This project follows the same community spirit as dbatools.
MIT — © 2026 DataPlat contributors
MCP server for dbatools — exposes SQL Server management commands as MCP tools
{ "mcpServers": { "io.github.dataplat-dbatools-mcp-server": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "DBATOOLS_SAFE_MODE": "<value>", "MAX_OUTPUT_ROWS": "<value>", "COMMAND_TIMEOUT_SECONDS": "<value>", "PWSH_EXE": "<value>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: DBATOOLS_SAFE_MODE, MAX_OUTPUT_ROWS, COMMAND_TIMEOUT_SECONDS, PWSH_EXE
Dbatools ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-09 MCP server for dbatools — exposes SQL Server management commands as MCP tools