About MSSQL LocalDB MCP
MSSQL LocalDB MCP is a Rust MCP server for managing SQL Server Express LocalDB on Windows. It supports local development tasks such as running T-SQL, discovering database files, attaching them, and inspecting schemas without an external runtime.
Key features
- 01Manage LocalDB instances
- 02Run T-SQL scripts
- 03Find and attach database files
- 04Inspect database schemas
- 05Single Rust binary
Use cases
- 01Running scripts against a local database
- 02Attaching an MDF found in a project
- 03Inspecting a LocalDB schema
MCP support
The server exposes LocalDB management, SQL execution, database discovery, and schema inspection tools to MCP clients. Destructive actions require explicit confirmation.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEmssql-localdb-mcp
Rust MCP server for SQL Server Express LocalDB on Windows. Gives AI agents (Claude Desktop, Claude Code, and any MCP client) full control over LocalDB instances: create/manage instances, run any T-SQL script, find loose database files in project folders and attach them, introspect schema.
Status: MVP (Phase 1) functional and tested against real LocalDB — see
docs/PLANNING.mdfor the roadmap and current phase.
Why
Existing MCP tools for SQL Server assume an already-configured remote server and require an external runtime (Python, .NET, Node). This project is:
- Single Rust binary, no external runtime, no Docker.
- LocalDB-focused: local dev workflow — find a loose
.mdfin a project folder, attach it, run a script, no need to open SSMS. - Windows-only by design, not a generic multi-database abstraction.
Requirements
- Windows with SQL Server Express LocalDB installed (
SqlLocalDB.exeonPATH). - A compatible MCP client (Claude Desktop, Claude Code, etc.).
Installation
Via MCP Registry
Published on the official MCP Registry as io.github.hermessilva/mssql-localdb-mcp. Install through any MCP client that supports the registry.
Via VS Code extension
The vscode-extension/ directory packages the server as a VS Code extension that registers it automatically through the MCP provider API (VS Code 1.101+), with the Windows binary bundled — nothing to download or configure by hand. Build the .vsix locally with:
./build-vsix.ps1 # bumps the build segment; -Version x.y.z or -NoBump to control it
code --install-extension .\mssql-localdb-mcp-1.0.1-win32-x64.vsix
The extension has its own version line, independent from Cargo.toml — the crate version is what
the vX.Y.Z tag and the MCP Registry publish.
Via Claude Code plugin
The claude-plugin/ directory in this repo is a self-contained Claude Code plugin (bundles the Windows binary directly, no separate download). Load it directly with:
claude --plugin-dir path\to\LocalDB-MCP\claude-plugin
Submitted to the claude-community marketplace for review — once approved, install it with claude plugin marketplace add anthropics/claude-plugins-community followed by claude plugin install mssql-localdb-mcp@claude-community.
From source
Requires Rust and LocalDB installed.
git clone https://github.com/hermessilva/LocalDB-MCP.git
cd LocalDB-MCP
cargo build --release
Binary at target\release\mssql-localdb-mcp.exe.
Configure config.toml
db_scan_folder requires at least one explicitly allowed root — without it, the tool refuses to run. Create %APPDATA%\mssql-localdb-mcp\config.toml:
# Windows paths in TOML need single quotes (literal string) — double
# quotes interpret \U... as a unicode escape and break parsing.
scan_allowlist = ['C:\Users\YourUser\source\repos']
scan_max_depth = 6
default_query_timeout_secs = 30
default_max_rows = 1000
Configure in your MCP client
Claude Desktop / Claude Code (claude_desktop_config.json or equivalent):
{
"mcpServers": {
"mssql-localdb": {
"command": "C:\\path\\to\\LocalDB-MCP\\target\\release\\mssql-localdb-mcp.exe"
}
}
}
Claude Code via CLI:
claude mcp add mssql-localdb -- "C:\path\to\LocalDB-MCP\target\release\mssql-localdb-mcp.exe"
After that, the agent has access to the localdb_*, sql_*, and db_* tools — see docs/MCP_SPEC.md for the full list.
Documentation
docs/PLANNING.md— roadmap, phases, scope of each milestone.docs/ARCHITECTURE.md— modules, technical decisions, data flow.docs/MCP_SPEC.md— exact contract of every tool/resource/prompt exposed.docs/SECURITY.md— threat model and guardrails.CLAUDE.md— guide for AI agents working in this repository.CONTRIBUTING.md— how to contribute.CHANGELOG.md— change history.
Security — read before using
- Windows Integrated Authentication only (no SQL Auth).
- Every destructive action (DROP, TRUNCATE, DELETE, ALTER, etc.) requires explicit confirmation (
confirm: true) — never executes silently. - Database discovery (
db_scan_folder) only scans folders explicitly allowed inconfig.toml(allowlist). - Full detail in
docs/SECURITY.md.
License
MIT.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.