# MS SQL Server MCP Server v2.3.5 🚀 **Model Context Protocol (MCP) server** for Microsoft SQL Server - compatible with Claude Desktop, Cursor
Most database access work still happens through a UI a human drives. MS SQL Server MCP server moves it into the conversation instead. # MS SQL Server MCP Server v2.3.5 🚀 Model Context Protocol (MCP) server for Microsoft SQL Server - compatible with Claude Desktop, Cursor, Windsurf and VS Code.
The server publishes 10 tools. What each one is for:
mssql_connect_database — Nomssql_disconnect_database — Nomssql_connection_status — ✅mssql_run_sql_query — ⚠️ Nomssql_list_schema_objects — ✅mssql_describe_table_columns — ✅mssql_read_table_rows — ✅mssql_execute_stored_procedure — ⚠️ Nomssql_list_databases — ✅Transport — The Transport tool exposed by this serverConfiguration is passed through the environment: DB_SERVER, DB_DATABASE, DB_USER, DB_PASSWORD, DB_ENCRYPT, DB_TRUST_SERVER_CERTIFICATE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MS SQL Server's toolset — mssql_connect_database, mssql_disconnect_database, mssql_connection_status and 7 more — is a fair guide to whether it matches your workflow. It is maintained by bymcs; 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 |
|---|---|
| mssql_connect_database | No |
| mssql_disconnect_database | No |
| mssql_connection_status | ✅ |
| mssql_run_sql_query | ⚠️ No |
| mssql_list_schema_objects | ✅ |
| mssql_describe_table_columns | ✅ |
| mssql_read_table_rows | ✅ |
| mssql_execute_stored_procedure | ⚠️ No |
| mssql_list_databases | ✅ |
| Transport | The Transport tool exposed by this server. |
{
"mcpServers": {
"mssql-mcp-bymcs": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"DB_SERVER": "your-value",
"DB_DATABASE": "your-value",
"DB_USER": "your-value",
"DB_PASSWORD": "your-value",
"DB_ENCRYPT": "your-value",
"DB_TRUST_SERVER_CERTIFICATE": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| DB_SERVER | Configuration value read at startup. | Optional |
| DB_DATABASE | Configuration value read at startup. | Optional |
| DB_USER | Configuration value read at startup. | Optional |
| DB_PASSWORD | Configuration value read at startup. | Optional |
| DB_ENCRYPT | Configuration value read at startup. | Optional |
| DB_TRUST_SERVER_CERTIFICATE | 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.