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.
A SQL Server client with schema listing, stored-procedure lookup and explicit transaction control.
- 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.
A reachable SQL Server instance and five environment variables — DB_HOST, DB_PORT, DB_USERNAME, DB_PASSWORD and DB_DATABASE.
One command plus a key — npx -y mcp-node-mssql, then supply credentials