MCP Server for SQL Server using node-mssql
MCP Node Mssql MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP Server for SQL Server using node-mssql.
See the official Cursor docs for more information.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Once MCP Node Mssql is connected, these are the calls the assistant has available:
Cursor — See the official Cursor docs for more informationWindsurf — See the official Windsurf docs for more informationInstallation — The Installation tool exposed by this serverBuild — The Build tool exposed by this serverYou will need 8 environment variables: DB_HOST, DB_PORT, DB_USERNAME, DB_PASSWORD, DB_DATABASE, DB_ENCRYPT, DB_ENABLE_ARITH_ABORT, DB_TRUST_SERVER_CERTIFICATE. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Node Mssql's toolset — Cursor, Windsurf, Installation and 1 more — is a fair guide to whether it matches your workflow. It is maintained by cwilby; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Node Mssql's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Cursor | See the [official Cursor docs](https://docs.cursor.com/context/model-context-protocol) for more information. |
| Windsurf | See the [official Windsurf docs](https://codeium.com/docs/windsurf/mcp) for more information. |
| Installation | The Installation tool exposed by this server. |
| Build | The Build tool exposed by this server. |
{
"mcpServers": {
"mssql": {
"command": "npx",
"args": [
"-y",
"mcp-node-mssql"
],
"env": {
"DB_HOST": "localhost",
"DB_PORT": "1433",
"DB_USERNAME": "<username>",
"DB_PASSWORD": "<password>",
"DB_DATABASE": "<database>",
"CONNECTION_TIMEOUT": 600000,
"REQUEST_TIMEOUT": 300000
"DB_ENCRYPT": "false",
"DB_ENABLE_ARITH_ABORT": "false",
"DB_TRUST_SERVER_CERTIFICATE": "false",
"TRUSTED_CONNECTION": "false"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DB_HOST | Endpoint or connection string the server talks to. | Optional |
| DB_PORT | Configuration value read at startup. | Optional |
| DB_USERNAME | Configuration value read at startup. | Optional |
| DB_PASSWORD | Configuration value read at startup. | Optional |
| DB_DATABASE | Configuration value read at startup. | Optional |
| DB_ENCRYPT | Configuration value read at startup. | Optional |
| DB_ENABLE_ARITH_ABORT | 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.