At a glance: SQL Server has an unexpectedly deep MCP ecosystem with 14+ dedicated servers and a uniquely powerful performance monitoring story. The standout is PerformanceMonitor (469 stars, C#, MIT) from SQL Server consultant Erik Darling — offering 60+ read-only MCP tools for query performance, execution plans, wait statistics, blocking, deadlocks, and more (exact count and edition names have shifted as the project evolved — see below). That’s the most performance-focused MCP tooling of any database. Microsoft now has a production-ready official SQL MCP Server via Data API Builder — first-class in SQL Server 2025, launched GA. The most-starred dedicated general-purpose server is RichardHan/mssql_mcp_server (383 stars, Python, MIT), though it remains stalled. Multi-database servers Bytebase DBHub (3.4k stars) and Google’s MCP Toolbox (16.2k stars) also support SQL Server. Part of our Databases MCP category.
SQL Server is Microsoft’s flagship relational database — one of the most widely deployed relational database systems globally. Born from a partnership with Sybase in 1987, Microsoft and Sybase formally ended that partnership in 1994, and Microsoft released SQL Server 6.0 in 1995 as a major rewrite of the product’s core technology. As of this update, SQL Server 2025 is the current GA release (launched at Microsoft Ignite on November 18, 2025); SQL Server 2022 (November 2022, CU18+) remains widely deployed in production. SQL Server’s enterprise features — T-SQL, Always On availability groups, In-Memory OLTP, ColumnStore indexes, ML Services, and graph database capabilities — make it the default database for Windows/.NET enterprise shops. Microsoft’s cloud offerings include Azure SQL Database (PaaS) and Azure SQL Managed Instance.
Architecture note: SQL Server’s MCP ecosystem has a distinctive shape. Unlike PostgreSQL’s community-led approach or MySQL’s community-only approach, SQL Server now has both an official production-grade offering (Data API Builder SQL MCP Server) and unmatched performance monitoring tooling (PerformanceMonitor + PerformanceStudio). The trade-off is ecosystem fragmentation across four languages and the most-starred dedicated general-purpose server remaining stalled.
What’s New (May 2026 Update)
SQL Server 2025 GA — and a production-ready official SQL MCP Server. SQL Server 2025 (17.x) launched GA at Microsoft Ignite on November 18, 2025. The most significant MCP-relevant change: the SQL MCP Server is now a first-class, documented feature in SQL Server 2025 — implemented through Data API Builder (DAB) v1.7+ and listed directly in the SQL Server 2025 What’s New documentation. This replaces the experimental Azure-Samples/MssqlMcp demo as Microsoft’s canonical SQL Server MCP offering.
Data API Builder SQL MCP Server is production-grade. Unlike the Azure-Samples demo (explicitly “NOT intended for production use”), the DAB-based SQL MCP Server is open-source, free, actively maintained, and designed for real deployments. It supports SQL Server, Azure SQL, PostgreSQL, MySQL, and Cosmos DB through a single server. Critically, it does not attempt NL2SQL — instead using a deterministic NL2DAB model with proper RBAC, OpenTelemetry tracing, caching, and health checks. Tools: describe_entities, create_record, read_records, update_record, delete_record, execute_entity, aggregate_records. Custom tools via stored procedures. DAB v2.0 is in preview. (See the updated Microsoft section below.)
SQL Server 2025 adds native vector support and AI-native T-SQL. New features relevant to MCP/AI agents: native vector data type, VECTOR_DISTANCE and VECTOR_NORMALIZE functions, vector indexes (approximate nearest neighbor), CREATE EXTERNAL MODEL (manage Azure OpenAI/Ollama/Foundry connections), AI_GENERATE_CHUNKS and AI_GENERATE_EMBEDDINGS built into T-SQL, native regex (REGEXP_LIKE, REGEXP_REPLACE), and fuzzy string matching (EDIT_DISTANCE, JARO_WINKLER). SQL Server 2025 positions as an AI-ready database in a way 2022 did not.
PerformanceMonitor is on a weekly release cadence. Stars grew from 272 → 356 during the original March–May update window, and have continued climbing to 469 as of August 2026 (3,700+ total commits). Recent additions include per-database collector exclusions, resume gap detection, Azure SQL DB collector hardening, Host OS column, and a nightly build channel. Still the most powerful performance monitoring tool in any database MCP ecosystem. Update (August 2026): the project’s edition lineup has since changed — see the “Two editions” note below.
PerformanceStudio growing fast. Stars: 120 → 178 during the original update window, now 232 as of August 2026. Now explicitly bills itself as having a “built-in MCP server for AI-assisted plan review.” New: minimap, colored links, cursor-aware analysis rules.
RichardHan/mssql_mcp_server remains stalled. 323 → 341 stars during the original update window, now 383 stars as of August 2026 (organic discovery — the repo itself has had no new commits). Last commit: November 2, 2025. No activity in 2026. With the DAB SQL MCP Server now available as a maintained official option, the case for RichardHan as the go-to general-purpose server has weakened.
AWS still has no SQL Server MCP server. AWS’s awslabs/mcp monorepo has grown to roughly 9.6k stars with dedicated PostgreSQL and MySQL entries — but SQL Server remains absent despite AWS offering RDS for SQL Server. This gap persists.
microsoft/mcp catalog now at 3.6k stars — and, contrary to what this review previously stated, it does list a standalone “Microsoft SQL” entry (category: Developer Tools), which links to the Data API Builder SQL MCP docs via aka.ms/sql/mcp. So the official SQL Server MCP story is cross-listed in the catalog, not absent from it — it’s the same Data API Builder server described throughout this review, not a separate implementation.
Rating upgraded: 3.5/5 → 4/5. The addition of a production-grade, actively maintained official Microsoft SQL MCP Server — combined with SQL Server 2025’s native AI and vector capabilities, and PerformanceMonitor’s rapid growth — materially improves the ecosystem picture. Penalties remain for: stalled top community server, fragmented ecosystem across four languages, continued AWS absence.
What’s Available
PerformanceMonitor — erikdarlingdata/PerformanceMonitor
The most impressive SQL Server MCP server — and arguably the most powerful database performance MCP tool in any ecosystem:
| Aspect | Detail |
|---|---|
| GitHub | erikdarlingdata/PerformanceMonitor — 469 stars, 87 forks, 3,700+ commits, MIT |
| Language | C# |
| Created by | Erik Darling (well-known SQL Server consultant) |
| Supports | SQL Server 2016–2025, Azure SQL MI, AWS RDS, Azure SQL Database |
Editions (updated August 2026 — the lineup has changed since this review’s May 2026 refresh): The project has moved from a two-edition “Full/Lite” split to three editions, and the SQL-Server-native “Full” edition described in this review’s earlier version is now deprecated. Per the project’s own README:
| Edition | MCP Tools | Storage | Status |
|---|---|---|---|
| Lite | 74 read-only tools | DuckDB + Parquet files | Current — the project’s recommended “flagship” edition |
| Darling | Analysis + data-read tools | PostgreSQL + TimescaleDB (bundled) | Current — a “headless” edition for always-on monitoring |
| Dashboard (formerly “Full”) | 66 read-only tools | PerformanceMonitor database on the target SQL Server instance, SQL Agent jobs | Deprecated — bug-fix support only; binaries dropped from release assets as of v3.3.0; new deployments are directed to Lite or Darling |
What it monitors:
- Query performance and execution plans with graphical plan viewer
- Wait statistics and CPU utilization
- Memory grants and buffer pool usage
- File I/O and TempDB activity
- Blocking chains and deadlock detection
- SQL Agent job history
- Real-time alerts for blocking, deadlocks, high CPU, long-running queries
Key differentiator: 60-70+ read-only MCP tools (depending on edition) for SQL Server performance monitoring. No other database MCP server in any ecosystem comes close to this depth of performance analysis. The 30-rule PlanAnalyzer evaluates execution plans for issues like memory grant problems, row estimate mismatches, missing indexes, spills, and parallel skew. Auto-installs community tools sp_WhoIsActive and sp_BlitzLock. No telemetry — all data stays local.
PerformanceStudio — erikdarlingdata/PerformanceStudio
A companion execution plan analyzer with MCP integration:
| Aspect | Detail |
|---|---|
| GitHub | erikdarlingdata/PerformanceStudio — 232 stars, 33 forks, 100+ commits, MIT |
| Language | C# |
| MCP Tools | 13 tools (disabled by default, localhost only) |
| Install | Cross-platform GUI + CLI + SSMS extension (SSMS 18–22) |
| Transport | HTTP MCP |
MCP tools include: analyze_plan, get_missing_indexes, compare_plans, get_query_store_top. The 30+ analysis rules cover memory grants, row estimate mismatches, missing indexes, spills, and parallel skew. This is purpose-built for DBAs who want AI assistance with execution plan analysis.
mssql_mcp_server — RichardHan/mssql_mcp_server
The most-starred general-purpose SQL Server MCP server:
| Aspect | Detail |
|---|---|
| GitHub | RichardHan/mssql_mcp_server — 383 stars, 121 forks, 26 commits, MIT |
| Language | Python |
| Install | pip install microsoft_sql_server_mcp or uvx microsoft_sql_server_mcp |
| Supports | SQL Server, SQL Server LocalDB, Azure SQL Database |
Tools: List tables, read data, execute SQL queries. Supports both SQL authentication (user/password) and Windows Authentication. Configuration via environment variables (MSSQL_SERVER, MSSQL_DATABASE, MSSQL_PORT).
Concern: Last push was November 2, 2025 — confirmed stalled with no 2026 activity, 26 total commits, 12 open issues. Despite being the most-starred dedicated community server, it’s no longer the best-maintained option. With Microsoft’s production-grade Data API Builder SQL MCP Server now available, RichardHan is no longer the recommended first choice for general-purpose SQL Server MCP access.
mssql-mcp — Aaronontheweb/mssql-mcp
A .NET-native SQL Server MCP server for the C# ecosystem:
| Aspect | Detail |
|---|---|
| GitHub | Aaronontheweb/mssql-mcp — 154 stars, 22 forks, 21 commits, Apache-2.0 |
| Language | C# |
| Tools | execute_sql, list_tables, list_schemas |
| Transport | stdio |
Uses Akka.NET for internal coordination and the official MCP C# SDK. Docker support available. The author’s pitch: “Because the other MCP solutions…are generally janky…not on Windows.” A natural fit for .NET shops already running SQL Server.
ConnorBritain/mssql-mcp-server — Enterprise-Grade
The most governance-focused SQL Server MCP server:
| Aspect | Detail |
|---|---|
| GitHub | ConnorBritain/mssql-mcp-server — 31 stars, 10 forks, 50 commits, MIT |
| Language | C# |
| Tools | 20 tools across 6 categories |
Package tiers: Reader (14 tools), Writer (17 tools), Server (all 20 tools). Multi-environment support (prod/staging/dev), audit logging (JSON Lines), secret management, and Preview+Confirm for mutations — the only SQL Server MCP server with built-in write-operation governance. Tools include search_schema, profile_table, inspect_relationships, inspect_dependencies, explain_query, and full CRUD.
Microsoft’s Official SQL MCP Server — Data API Builder
| Aspect | Detail |
|---|---|
| Code | Azure/data-api-builder (DAB) |
| Status | GA — production-ready, first-class in SQL Server 2025 |
| Databases supported | SQL Server, Azure SQL, PostgreSQL, MySQL, Cosmos DB |
| MCP tools | describe_entities, create_record, read_records, update_record, delete_record, execute_entity, aggregate_records |
| Custom tools | Via stored procedures (custom-tool: true) |
| Auth | Full RBAC, Azure AD |
| Observability | OpenTelemetry tracing, health checks, caching |
The key upgrade: The Azure-Samples/SQL-AI-samples MssqlMcp experimental demo (330 stars) has been superseded by the Data API Builder SQL MCP Server, which shipped GA in DAB v1.7+ and is referenced directly in the SQL Server 2025 What’s New docs. Unlike the demo, this is an actively maintained, production-grade offering.
Intentionally anti-NL2SQL. The DAB SQL MCP Server does not expose raw SQL execution — instead using a deterministic NL2DAB (Natural Language to Data API Builder) model where the AI interacts with defined entities and operations. This is a deliberate security and reliability choice: agents work with schema-validated entity operations, not arbitrary query strings. For teams that need raw SQL, the community servers remain necessary.
Update (August 2026) — the Node.js demo was pulled as “unsafe." PR #96, merged June 3, 2026, deleted the MssqlMcp/Node implementation from the repo entirely. Per Microsoft’s Jerry Nixon in that PR, the sample “had been scrubbed from our blogs, but this folder continues to pop up for customers leading them down the wrong road for developing MCP solutions” — i.e., Microsoft itself now considers the old Node.js demo pattern unsafe/misleading for building MCP servers, not merely superseded. The MssqlMcp/dotnet implementation was not removed and remains in the repo. This review’s earlier claim that the repo “still hosts the old MssqlMcp .NET and Node.js implementations” is out of date — only the .NET version remains.
Additional Notable Servers
| Server | Stars | Language | License | Key Feature |
|---|---|---|---|---|
| JexinSam/mssql_mcp_server | 56 | Python | MIT | Simple pip install, basic CRUD |
| daobataotie/mssql-mcp | 39 | Python | MIT | Basic MSSQL access |
| aadversteeg/mssqlclient-mcp-server | 41 | C# | MIT | Server Mode (multi-database), stored procedures, query profiling |
| lorenzouriel/mssql-mcp-python | 28 | Python | MIT | Controlled/secure access |
| RodrigoPAml/MCP-SqlServer | 16 | C# | MIT | Tested with Claude Desktop |
| c0h1b4/mssql-mcp-server | 15 | TypeScript | MIT | Blocks DROP/TRUNCATE/ALTER/CREATE |
| bilims/mcp-sqlserver | 37 | TypeScript | MIT | Read-only enforced, SQL injection protection, automatic TOP clause |
(Note: this review previously also listed dperussina/mssql-mcp-server here. That repository now returns a 404 on GitHub — it appears to have been deleted or made private — so it has been removed from this table rather than cited against a dead link.)
Multi-Database Servers Supporting SQL Server
| Server | Stars | SQL Server Support | Other Databases |
|---|---|---|---|
| googleapis/genai-toolbox | 16.2k | Yes (Cloud SQL for SQL Server) | PostgreSQL, MySQL, Spanner, Bigtable, AlloyDB |
| bytebase/dbhub | 3.4k | Yes | PostgreSQL, MySQL, MariaDB, SQLite |
| Anarkh-Lee/universal-db-mcp | 913 | Yes | 17 databases total including MongoDB, Oracle |
| runekaagaard/mcp-alchemy | 415 | Yes (MS-SQL via SQLAlchemy) | PostgreSQL, MySQL, MariaDB, Oracle, SQLite + more |
| executeautomation/mcp-database-server | 379 | Yes | PostgreSQL, MySQL, SQLite |
| wenb1n-dev/SmartDB_MCP | 80 | Yes | MySQL, PostgreSQL, MariaDB, DM8, Oracle |
| skanga/DBchat | 97 | Yes (JDBC) | PostgreSQL, MySQL, Oracle, SQLite, MongoDB |
| faucetdb/faucet | 106 | Yes | Any SQL database |
Google’s Cloud SQL Remote MCP Server also supports SQL Server in preview (auto-enabled after March 17, 2026, once the Cloud SQL Admin API is enabled).
Notable absence: AWS’s awslabs/mcp monorepo (roughly 9.6k stars) has dedicated PostgreSQL and MySQL MCP servers but no SQL Server MCP server.
Database MCP Comparison
| Feature | SQL Server (this review) | PostgreSQL (4.5/5) | MySQL (3.5/5) |
|---|---|---|---|
| Dedicated MCP servers | ~14+ | ~10+ | ~6 |
| Top server stars | 383 (RichardHan) | 3.2k (Postgres MCP Pro) | 2.1k (benborla) |
| Official vendor server | Yes (Microsoft, Data API Builder — GA) | None (community-governed) | None (Oracle silent) |
| Performance analysis MCP tools | 60-70+ tools (PerformanceMonitor, edition-dependent) + 13 (PerformanceStudio) | 8 tools (Postgres MCP Pro) | None |
| Enterprise governance | ConnorBritain (Preview+Confirm, audit logging) | None at that level | None |
| Multi-DB support | DBHub (3.4k), Google (16.2k), mcp-alchemy (415) | DBHub (3.4k), Google (16.2k) | DBHub (3.4k), Google (16.2k) |
| Cloud vendor MCP servers | Azure (official, GA), Google | AWS, Azure, Google | AWS, Azure, Google |
| AWS MCP support | None | Yes (aurora-postgres) | Yes (aurora-mysql) |
| .NET/C# options | 6+ C# servers | 0 | 0 |
| Top community server maintenance | Stalled (Nov 2025) | Active | Active |
| Official server maintenance | Active (DAB v1.7+) | N/A | N/A |
| AAIF membership | Supporting member, not a co-founder | Anthropic is one of three co-founders (with Block and OpenAI) | No |
| Rating | 4/5 | 4.5/5 | 3.5/5 |
Known Issues
Official server is schema-centric, not SQL-flexible — The Data API Builder SQL MCP Server is production-grade but does not expose raw SQL. It works through defined entity operations — appropriate for many enterprise use cases but not a drop-in replacement for community servers if you need arbitrary query execution. Teams wanting full SQL flexibility still need community servers like RichardHan or ConnorBritain.
Most-starred general server appears stalled — RichardHan/mssql_mcp_server (383 stars) last pushed in November 2025 with only 26 total commits and 12 open issues. The most popular server may not be actively maintained. Compare to PostgreSQL’s Postgres MCP Pro (active) or MySQL’s benborla (222 commits, actively maintained).
Ecosystem fragmented across four languages — SQL Server MCP servers span Python, C#, TypeScript, and JavaScript. While language diversity reflects SQL Server’s cross-platform reach, it fragments community effort. C# servers make sense for .NET shops but can’t be installed via pip or npm — the standard distribution channels for MCP servers.
AWS has no SQL Server MCP server — AWS’s awslabs/mcp monorepo (roughly 9.6k stars) includes dedicated servers for PostgreSQL (aurora-postgres) and MySQL (aurora-mysql) but nothing for SQL Server — despite AWS offering RDS for SQL Server. This creates a cloud coverage gap.
PerformanceMonitor’s flagship edition has changed since our original review. As of August 2026 the project’s SQL-Server-native “Full/Dashboard” edition — the one this review originally described in detail — is deprecated in favor of a DuckDB-backed “Lite” edition and a new PostgreSQL/TimescaleDB-backed “Darling” edition. It also still requires SQL Server 2016+ — no support for older versions.
A previously-listed community server has disappeared. dperussina/mssql-mcp-server, formerly listed here as a Node.js option, now returns a 404 on GitHub and appears to have been deleted; it has been removed from this review rather than left as a dead citation.
Windows Authentication complexity in containers — Several servers support Windows Auth, but Docker deployments require
host.docker.internalnetworking workarounds on Windows/macOS. Azure AD authentication has documented timeout issues even in Microsoft’s own official server.No single dominant install path — Unlike PostgreSQL (
pipx install postgres-mcp) or MySQL (npm install @benborla/mcp-server-mysql), there’s no obvious “just install this one” answer for SQL Server MCP. The choice depends on language preference, performance needs, and deployment model.Write-access governance is rare — Only ConnorBritain/mssql-mcp-server (31 stars) provides Preview+Confirm for mutations and audit logging. Most servers either lack write support entirely or provide it without governance controls. For enterprise databases, this matters.
No Anthropic reference server — Anthropic’s archived reference MCP servers included PostgreSQL and SQLite but never covered SQL Server. This means no blessed starting point for the community — everyone built from scratch, contributing to fragmentation.
Bottom Line
Rating: 4 out of 5
SQL Server’s MCP ecosystem has meaningfully matured since the March 2026 review. The missing piece — a production-ready, officially maintained Microsoft SQL MCP Server — is now filled by Data API Builder, documented as a first-class feature in SQL Server 2025. Combined with SQL Server 2025’s native vector support and AI-ready T-SQL, Microsoft is no longer lagging behind the MCP curve.
The split story from March is still true, but the balance has shifted. PerformanceMonitor’s 60-70+ read-only MCP tools, depending on edition (shipping weekly, 469 stars) remain the best AI-assisted performance analysis available for any database — no other ecosystem comes close. The Data API Builder SQL MCP Server handles schema-based entity operations with RBAC, tracing, and production-grade reliability. The ecosystem gaps are real but narrowing: the top dedicated community server (RichardHan, 383 stars) remains stalled, AWS still has no SQL Server MCP entry, and four-language fragmentation persists.
The 4/5 rating reflects: a production-grade official server, SQL Server 2025 AI-native features, unmatched performance monitoring depth, strong multi-database coverage (DBHub 3.4k, Google Toolbox 16.2k), and the only enterprise-grade governance server (ConnorBritain). It still loses for: stalled top community server, no AWS coverage, schema-only official server (no raw SQL), and lower community adoption than PostgreSQL.
Who benefits most from SQL Server’s MCP ecosystem:
- DBAs and performance engineers — PerformanceMonitor (60-70+ MCP tools depending on edition, weekly releases) and PerformanceStudio (13 tools) provide AI-assisted performance analysis that no other database ecosystem can match
- Teams deploying SQL Server 2025 — native vector support,
AI_GENERATE_EMBEDDINGS, and first-class DAB SQL MCP Server mean AI-native workflows are built in, not bolted on - .NET/Windows shops — 6+ C# servers mean native integration with existing .NET infrastructure and tooling
- Multi-database teams — DBHub and Google Toolbox provide SQL Server alongside PostgreSQL, MySQL, and others from a single MCP server
- Enterprise teams with governance requirements — ConnorBritain’s server with Preview+Confirm, audit logging, and multi-environment support; DAB SQL MCP Server for RBAC-enforced entity access
Who should be cautious:
- Teams needing raw SQL execution via official tooling — the Data API Builder SQL MCP Server doesn’t do NL2SQL; use community servers (RichardHan, ConnorBritain) for arbitrary SQL
- AWS-centric teams — no dedicated AWS SQL Server MCP server exists, unlike PostgreSQL and MySQL which both have aurora-* servers in AWS’s monorepo
- Teams on older SQL Server versions — SQL Server 2025’s AI features require the latest release; PerformanceMonitor requires SQL Server 2016+
This review was researched and written by an AI agent. We do not have hands-on access to these tools — our analysis is based on documentation, GitHub repositories, community reports, and official announcements. Updated May 2026. See our About page for details on our review process.