query
Run a SQL query; the connection (connectionString, or host, port, database, username, password, encrypt, trustServerCertificate) is passed with each call.
LABSCO SUMMARY
One query tool, and the connection travels with each call.
No connection details go in the client config: every call carries a connection string, or a host, username and password, so one server can reach more than one SQL Server. It is a single tool. The database, table and schema tools in the project's docs are not available, and the statement you send runs as written, with no filtering, so connect as a login whose permissions you are comfortable with.
What it is
A SQL Server client over MCP. It runs SQL against a connection passed with each call — a connection string, or a host, username and password. The project's docs also describe tools for listing databases and tables and for describing a table, but the server only provides query.
What you get
- query — run a SQL statement against the connection given in the same call (a connection string, or host, port, database, username and password, with encrypt and trustServerCertificate); the rows come back as JSON
Requirements
Node.js and a clone of the repository, built with npm run build; the client runs build/src/index.js with node. The npm package called mssql-mcp-server is a different project. Connection details do not go in the client config: each query carries a connection string, or a host, username and password, with encrypt and trustServerCertificate for TLS.
Setup effort
Build from source — git clone https://github.com/c0h1b4/mssql-mcp-server.git
USE CASES
01
Finding your way around a server
Query sys.databases, then INFORMATION_SCHEMA.TABLES in the database you want.
02
Writing a query against a table you have not seen
Query INFORMATION_SCHEMA.COLUMNS for the table first, then write SQL that uses what came back.
03
Running a query safely
Connect as a login with only the permissions the query needs, since the statement runs exactly as sent.
04
Checking a table before an insert
Query sys.triggers and sys.foreign_keys for the table so the write does not surprise you.
1 tool
Listed in project code.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool registered in the project's code. The project's docs also describe list_databases, list_tables and describe_table, but the server only provides query. To list databases or describe a table, send the SQL through query instead: sys.databases, INFORMATION_SCHEMA.TABLES or INFORMATION_SCHEMA.COLUMNS.
Requires
- Node.js 20
- Git
- A SQL Server you can reach
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
Clone the repository and install its dependencies.
TERMINAL
git clone https://github.com/c0h1b4/mssql-mcp-server.git
cd mssql-mcp-server
npm installBuild it:
TERMINAL
npm run buildThe build writes the server to build/src/index.js. In the Claude Desktop configuration, <YOUR_PATH_TO_MSSQL_MCP_SERVER> is the folder of your clone.
Connection details are not read from the environment. Give the assistant a connection string, or a host, username and password, and it passes them with each query.
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mssql": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MSSQL_MCP_SERVER>/build/src/index.js"
]
}
}
}
