MySQL MCP Server by xiangma9712
xiangma9712LABSCO SUMMARY
Small surface, three auth paths — the awkward part of SQL Server is the part it handles.
There is not much to it beyond list-and-query, which is the appeal: connecting is usually where SQL Server bridges fall over, and this one covers SQL, Windows and Azure AD credentials plus LocalDB and Azure SQL from the same config. The project's own advice is worth following — connect with a dedicated login with minimal permissions, never sa.
What it is
A small SQL Server bridge: list the tables, then run SELECT, INSERT, UPDATE or DELETE against the database in your connection settings.
What you get
- A list of the database's tables
- SQL execution — SELECT, INSERT, UPDATE and DELETE
- Three authentication paths: SQL authentication, Windows authentication, and Azure AD
- LocalDB and Azure SQL support, with encryption applied automatically for Azure
- A custom port when the server is not on the default
Requirements
MSSQL_SERVER and MSSQL_DATABASE are always required. SQL authentication adds MSSQL_USER and MSSQL_PASSWORD; Windows authentication uses MSSQL_WINDOWS_AUTH instead. MSSQL_PORT and MSSQL_ENCRYPT are optional. Your client starts it with uvx --from microsoft_sql_server_mcp mssql_mcp_server.
Setup effort
One command plus credentials — uvx --from microsoft_sql_server_mcp mssql_mcp_server, then supply credentials
USE CASES
01
Finding your way around an unfamiliar database
List the tables first, then query the ones that look relevant.
02
Answering a question that needs a join
Write the SELECT in the conversation and read the rows back.
03
Reaching an Azure SQL instance
Point it at the .database.windows.net host — encryption is applied for you.
04
Using your Windows login instead of a password
Set MSSQL_WINDOWS_AUTH and skip storing credentials in the config file.
BEFORE YOU INSTALL
What to know first
Requires
- uvx on PATH
- MSSQL_SERVER in your environment
- MSSQL_DATABASE in your environment
- MSSQL_USER and MSSQL_PASSWORD in your environment for SQL authentication, or MSSQL_WINDOWS_AUTH=true for Windows authentication
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx --from microsoft_sql_server_mcp mssql_mcp_serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mssql": {
"command": "uvx",
"args": [
"--from",
"microsoft_sql_server_mcp",
"mssql_mcp_server"
],
"env": {
"MSSQL_SERVER": "localhost",
"MSSQL_DATABASE": "<YOUR_MSSQL_DATABASE>",
"MSSQL_USER": "<YOUR_MSSQL_USER>",
"MSSQL_PASSWORD": "<YOUR_MSSQL_PASSWORD>"
}
}
}
}
