commit-transaction
Commit a transaction
LABSCO SUMMARY
A multi-statement change becomes reversible from the same conversation that issued it.
start-transaction hands back an ID that commit-transaction and rollback-transaction take, which is what makes a sequence of writes something you can abandon rather than repair. The introspection surface is deliberately narrow — tables and stored procedures, by list or by name — enough to write a query against, not a schema browser. Everything runs as the account in DB_USERNAME, so that account's permissions are the real boundary on what any of it can do.
What it is
A SQL Server client with schema listing, stored-procedure lookup and explicit transaction control.
What you get
- SQL statements executed against the configured database.
- The full table list, and any single table by name.
- The stored procedure list, and any single procedure by name.
- Transactions you drive yourself: start one, then commit or roll it back by its transaction ID.
Requirements
A reachable SQL Server instance and five environment variables — DB_HOST, DB_PORT, DB_USERNAME, DB_PASSWORD and DB_DATABASE.
Setup effort
One command plus credentials — npx -y mcp-node-mssql, then supply credentials
USE CASES
01
Reading what a stored procedure actually does before calling it
Names rarely describe the side effects. The definition settles what a procedure touches.
02
Making a multi-statement change you can still back out of
The transaction ID ties the statements together, so an unexpected result ends in a rollback rather than a repair script.
03
Orienting yourself in a database nobody documented
The table list gives you the map and a single table gives you the detail, which is usually enough to write the first query.
8 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get-stored-procedure
Get a specific stored procedure by name
get-stored-procedures
Get a list of all stored procedures in the database
get-table
Get a specific table by name
get-tables
Get a list of all tables in the database
query
Query the database with a SQL statement
rollback-transaction
Rollback a transaction
start-transaction
Start a new transaction
BEFORE YOU INSTALL
What to know first
Tools you get
8 tools when we connected. Five tools inspect schema and stored procedures, three drive transactions, and all writes go through the query tool, which runs any SQL you pass. No read-only switch is documented.
Requires
- npx on PATH
- DB_USERNAME in your environment
- DB_PASSWORD in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y mcp-node-mssqlMCP Clients
Cursor, Windsurf
JSON
{
"mcpServers": {
"mssql": {
"command": "npx",
"args": [
"-y",
"mcp-node-mssql"
],
"env": {
"DB_HOST": "localhost",
"DB_PORT": "1433",
"DB_USERNAME": "<YOUR_DB_USERNAME>",
"DB_PASSWORD": "<YOUR_DB_PASSWORD>",
"DB_DATABASE": "<YOUR_DB_DATABASE>",
"CONNECTION_TIMEOUT": 600000,
"REQUEST_TIMEOUT": 300000,
"DB_ENCRYPT": "false",
"DB_ENABLE_ARITH_ABORT": "false",
"DB_TRUST_SERVER_CERTIFICATE": "false",
"TRUSTED_CONNECTION": "false"
}
}
}
}Cursor — Local build, Windsurf — Local build
TERMINAL
git clone https://github.com/cwilby/mcp-node-mssql.git
cd mcp-node-mssql
npm install
npm run buildReference your local build; <YOUR_PATH_TO_LOCAL>/mcp-node-mssql is the full path of your clone:
JSON
{
"mcpServers": {
"mssql": {
"command": "node",
"args": [
"<YOUR_PATH_TO_LOCAL>/mcp-node-mssql/dist/index.js"
],
"env": {
"DB_HOST": "localhost",
"DB_PORT": "1433",
"DB_USERNAME": "<YOUR_DB_USERNAME>",
"DB_PASSWORD": "<YOUR_DB_PASSWORD>",
"DB_DATABASE": "<YOUR_DB_DATABASE>",
"CONNECTION_TIMEOUT": 600000,
"REQUEST_TIMEOUT": 300000,
"DB_ENCRYPT": "false",
"DB_ENABLE_ARITH_ABORT": "false",
"DB_TRUST_SERVER_CERTIFICATE": "false",
"TRUSTED_CONNECTION": "false"
}
}
}
}
