MCP server for SQL Server Express LocalDB on Windows: manage instances, run T-SQL, discover DBs
Runs on your machine from its package; the steps are below.
At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Distributed as an MCP bundle (`https://github.com/hermessilva/LocalDB-MCP/releases/download/v0.1.0/mssql-localdb-mcp-0.1.0-win64.mcpb`) — download it and import the bundle in your MCP client.
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.
Existing MCP tools for SQL Server assume an already-configured remote server and require an external runtime (Python, .NET, Node). This project is:
.mdf in a project folder, attach it, run a script, no need to open SSMS.SqlLocalDB.exe on PATH).Published on the official MCP Registry as io.github.hermessilva/mssql-localdb-mcp. Install through any MCP client that supports the registry.
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.
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.
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.
config.tomldb_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
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.
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.confirm: true) — never executes silently.db_scan_folder) only scans folders explicitly allowed in config.toml (allowlist).docs/SECURITY.md.MIT.