mcp-server-mssql
This server provides a Model Context Protocol (MCP) interface for safe, structured access to Microsoft SQL Server databases, allowing LLM agents to inspect schemas and perform CRUD operations. All queries are parameterized and validated against the live schema to prevent SQL injection, and all operations are logged.
list_tables: List all user tables in the database, with an optional schema name filter.get_table_schema: Retrieve column names, data types, nullability, and defaults for a specific table.read_table_rows: Query rows with optional column selection, WHERE filters (supporting operators like>=,=, etc.), ORDER BY (ASC/DESC), and LIMIT/OFFSET pagination.create_table_records: Insert one or more rows, with column and value validation against the live schema.update_table_records: Update rows matching specified filter conditions; returns the number of affected rows.delete_table_records: Delete rows matching specified filter conditions; returns the number of affected rows.
It is designed to integrate with MCP clients like Claude Desktop or Claude Code, connecting via stdio.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-server-mssql list all tables in the database"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-server-mssql
A Model Context Protocol server that gives LLM agents safe, structured access to Microsoft SQL Server: schema inspection plus row-level CRUD, every operation parameterized and logged.
Built because agents working against real business databases need more than "run this SQL string" — they need typed tools with predictable failure modes.
How it works
flowchart LR
A[MCP client<br/>Claude Desktop / Claude Code] -- stdio --> B[mcp-server-mssql]
B --> C[connection pool<br/>mssql driver]
C --> D[(SQL Server)]
B -. structured logs .-> E[logs/]The server connects to a single database configured via environment variables and exposes six tools. All queries are parameterized — table and column names are validated against the live schema before any statement runs, so an agent cannot inject through identifiers.
Related MCP server: MCP Databases Server
Tools
Tool | What it does |
| List all user tables in the configured database |
| Column names, types, nullability, and defaults for a table |
| Read rows with optional column selection, WHERE filters, ORDER BY, and LIMIT |
| Insert one or more rows (column/value validated against schema) |
| Update rows matching a filter; returns affected count |
| Delete rows matching a filter; returns affected count |
Example interaction
User: "Which customers signed up this month?"
Agent calls
list_tables→ findsCustomers→ callsget_table_schema {"table_name": "Customers"}→ seesCreatedAt datetime2→ callsread_table_rows {"table_name": "Customers", "filters": {"CreatedAt": {">=": "2026-07-01"}}, "limit": 50}→ answers with the rows.
Setup
Requires Node.js 18+ and network access to a SQL Server instance.
git clone https://github.com/TerraCo89/mcp-server-mssql.git
cd mcp-server-mssql
npm install
cp .env.example .env # fill in connection details
npm run buildConfiguration (environment variables)
Variable | Required | Notes |
| yes / no | Port defaults to 1433 |
| yes | SQL auth credentials |
| yes | Single database per server instance |
| no | TLS options |
| no |
|
Use with Claude Desktop / Claude Code
{
"mcpServers": {
"mssql": {
"command": "node",
"args": ["/path/to/mcp-server-mssql/dist/server.js"],
"env": {
"MSSQL_HOST": "localhost",
"MSSQL_USER": "agent_reader",
"MSSQL_PASSWORD": "...",
"MSSQL_DATABASE": "MyDb"
}
}
}
}Tip: point it at a least-privilege SQL login — the server can only do what the login can.
Development
npm run dev # ts-node with live reload
npm test # jest test suite (src/*.test.ts, tests/)
npm run build # emit dist/Docker: docker build -t mcp-server-mssql . then run with the same environment variables.
License
Available Tools
3 toolsget_table_schemaB
Gets the schema of a specific table
Inputs: table_name (required), schema.
list_tablesC
Lists all tables in the database
Inputs: schema.
read_table_rowsB
Reads rows from a table with optional filtering and pagination
Inputs: table_name (required), columns, filters, limit, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: listing tables, getting schema, and reading rows. There is no ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern: list_tables, get_table_schema, read_table_rows.
With 3 tools, the server is slightly underpopulated but still reasonable for a focused read-only database schema and data access tool.
The server lacks essential database operations such as writing, updating, deleting rows, or running arbitrary SQL queries, making it incomplete for typical use cases.
Maintenance
Related MCP Connectors
Hosted SQL Server MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
PostgreSQL, MySQL, and SQL Server in one session. 26 read-only MCP tools for AI agents.
Text-to-SQL MCP server: read-only queries on PostgreSQL, MySQL and SQL Server with your real schema
An agent-native database over MCP: shared, validated, structured records in every AI chat.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables AI agents to interact with Microsoft SQL Server databases through secure, intelligent database operations. This server provides comprehensive CRUD capabilities, schema introspection, stored procedure execution, transaction management, and bulk opera1,243 npm47MIT
- FlicenseNot gradedqualityDmaintenanceEnables LLMs and agents to interact with relational databases (SQL Server, MySQL, PostgreSQL) through MCP tools. Supports executing queries, inserting records, listing tables, and exposing database schemas with secure credential management.-
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Microsoft SQL Server databases through query execution, schema discovery, CRUD operations, stored procedures, and data export with built-in safety controls.1877 PyPIApache 2.0
- AlicenseAqualityDmaintenanceEnables AI models to interact with MS SQL Server databases through a standardized interface. Supports executing SQL queries with parameters, listing tables, and describing table schemas.395 npmMIT