Summary

Small, and it gets the encoding question right.

Most database servers assume UTF-8 and leave you stuck when an older SQL Server instance is not; exposing the character set as a setting is what makes this one work against legacy databases. Everything else is deliberately plain — six variables in a config file and it connects.

What it is

A Python server that connects an MCP client to Microsoft SQL Server. Connection details are passed as environment variables from the client config, and setup instructions are given for Cline.

What you get

A connection to a Microsoft SQL Server instance from your MCP client
Host, port, user, password and database all set in the client config
An explicit character set setting, so legacy encodings such as CP936 work as well as UTF-8
Runs from a checkout with `uv sync` and `uv run mssql-mcp-server`

Requirements

`uv` and a checkout of the repository. Six environment variables in the client config: `MSSQL_SERVER`, `MSSQL_PORT` (1433 for a default instance), `MSSQL_USER`, `MSSQL_PASSWORD`, `MSSQL_DATABASE` and `MSSQL_CHARSET`. The charset value is case-sensitive — a wrong case there is the likely cause of a connection that will not open. Give it a database login scoped to what the assistant should see. Version 0.1.0.