Labsco
MCP SERVER

Microsoft SQL Server

by RichardHan

Query a SQL Server database — including Azure SQL and LocalDB — straight from the conversation.

Relational SQL Databases
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. Runs via uvx as microsoft_sql_server_mcp.

Setup effort

One command plus a key — uvx microsoft_sql_server_mcp, then supply credentials