A configurable **Model Context Protocol (MCP) server** for Microsoft SQL Server integration with Claude Code and other MCP clients. Enables AI
MCP Ms Sql Server MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Ms Sql Server directly instead of describing what you should do. A configurable Model Context Protocol (MCP) server for Microsoft SQL Server integration with Claude Code and other MCP clients. Enables AI assistants to securely interact with SQL Server databases through project-based configurations.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Once MCP Ms Sql Server is connected, these are the calls the assistant has available:
ListConfigurations — Show all available project configurationsSwitchConfiguration — Switch to a different project configurationGetCurrentConfiguration — View current configuration detailsTestConnection — Test database connectivityExecuteQuery — Run SELECT queries within allowed schemaGetSchemaInfo — Explore database structure and objectsGetTableInfo — Get table metadata and sample dataInsertRecords — Insert new records with transaction supportUpdateRecords — Update existing records (requires WHERE clause)DeleteRecords — Delete records (requires WHERE clause)BuildQuery — Generate SQL queries from natural languageAnalyzeQueryPerformance — Analyze query execution plansYou will need 2 environment variables: MCP_CONFIG_NAME, DB_PASSWORD. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Ms Sql Server's toolset — ListConfigurations, SwitchConfiguration, GetCurrentConfiguration and 11 more — is a fair guide to whether it matches your workflow. It is maintained by 0xhubed; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| ListConfigurations | Show all available project configurations |
| SwitchConfiguration | Switch to a different project configuration |
| GetCurrentConfiguration | View current configuration details |
| TestConnection | Test database connectivity |
| ExecuteQuery | Run SELECT queries within allowed schema |
| GetSchemaInfo | Explore database structure and objects |
| GetTableInfo | Get table metadata and sample data |
| InsertRecords | Insert new records with transaction support |
| UpdateRecords | Update existing records (requires WHERE clause) |
| DeleteRecords | Delete records (requires WHERE clause) |
| BuildQuery | Generate SQL queries from natural language |
| AnalyzeQueryPerformance | Analyze query execution plans |
| GetDatabasePerformanceStats | Database performance metrics |
| DiscoverData | Search tables/columns by patterns |
| Variable | Description | Required |
|---|---|---|
| MCP_CONFIG_NAME | Configuration value read at startup. | Optional |
| DB_PASSWORD | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.