About MSSQL MCP Server
MSSQL MCP Server is an MCP server that lets AI assistants interact with Microsoft SQL Server databases in a structured way. It can list tables, read table contents and run SQL queries, with access set through environment variables. It suits developers who want models to reach MSSQL data under controlled permissions.
Key features
- 01Lists all tables in the database
- 02Runs read-only SELECT queries through query_sql
- 03Executes write and DDL statements through execute_sql
- 04Configures database access through environment variables
- 05Supports stdio and Streamable HTTP transports
- 06Provides Docker setup with ODBC drivers
Use cases
- 01Letting an AI assistant query data in an MSSQL database
- 02Browsing table structures from Claude Desktop or Cursor
- 03Giving a model read-only analysis access to a database
MCP support
MSSQL MCP Server runs as an MCP server and exposes table listing, read-only query and SQL execution tools to MCP clients, using tool annotations to mark read-only and destructive operations.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMSSQL MCP Server
MSSQL MCP Server is a Model Context Protocol (MCP) server that enables secure and structured interaction with Microsoft SQL Server (MSSQL) databases. It allows AI assistants to:
- List available tables
- Read table contents
- Execute SQL queries with controlled access
Built on MCP SDK v2 (2026-07-28 spec) with support for both stdio and Streamable HTTP transports.
Features
- Secure MSSQL Database Access through environment variables
- SQL Injection Protection with identifier validation
- Read-Only & Write Tools with appropriate MCP annotations
- Windows Authentication support via Trusted Connection
- Dual Transport — stdio (default) and HTTP
- Docker Support with pre-configured ODBC drivers
- Comprehensive Logging for monitoring queries and operations
Installation
pip install mssql-mcp-server
Configuration
Set the following environment variables to configure database access:
# Required
MSSQL_DATABASE=your_database
# Authentication (choose one):
# Option 1: SQL Server Authentication
MSSQL_USER=your_username
MSSQL_PASSWORD=your_password
# Option 2: Windows / Kerberos Authentication
Trusted_Connection=yes
# Optional
MSSQL_HOST=localhost # or use MSSQL_SERVER
MSSQL_DRIVER=SQL Server # default driver
TrustServerCertificate=no # default: no (set to yes for self-signed certs)
MCP_TRANSPORT=stdio # or "streamable-http" for Streamable HTTP
Available Tools
| Tool | Description | Annotations |
|---|---|---|
list_tables | List all tables in the database | Read-only, Idempotent |
query_sql | Execute read-only SELECT queries | Read-only, Idempotent |
execute_sql | Execute any SQL statement (SELECT, INSERT, UPDATE, DELETE, DDL) | Destructive |
Usage
With Claude Desktop
Add this configuration to claude_desktop_config.json:
{
"mcpServers": {
"mssql": {
"command": "uv",
"args": [
"--directory",
"path/to/mssql_mcp_server",
"run",
"mssql_mcp_server"
],
"env": {
"MSSQL_HOST": "localhost",
"MSSQL_USER": "your_username",
"MSSQL_PASSWORD": "your_password",
"MSSQL_DATABASE": "your_database"
}
}
}
}
With Cursor IDE
Add this to your .cursor/mcp.json:
{
"mcpServers": {
"mssql": {
"command": "uv",
"args": [
"--directory",
"path/to/mssql_mcp_server",
"run",
"mssql_mcp_server"
],
"env": {
"MSSQL_HOST": "localhost",
"MSSQL_USER": "your_username",
"MSSQL_PASSWORD": "your_password",
"MSSQL_DATABASE": "your_database"
}
}
}
}
With pip install (global)
{
"mcpServers": {
"mssql": {
"command": "mssql_mcp_server",
"env": {
"MSSQL_HOST": "localhost",
"MSSQL_USER": "your_username",
"MSSQL_PASSWORD": "your_password",
"MSSQL_DATABASE": "your_database"
}
}
}
}
With Docker
docker build -t mssql-mcp-server .
docker run -e MSSQL_HOST=host.docker.internal \
-e MSSQL_USER=your_username \
-e MSSQL_PASSWORD=your_password \
-e MSSQL_DATABASE=your_database \
mssql-mcp-server
Running as a Standalone Server
# Install dependencies
pip install -r requirements.txt
# Run the server (stdio)
python -m mssql_mcp_server
# Run with HTTP transport
MCP_TRANSPORT=streamable-http python -m mssql_mcp_server
Development & Testing
# Clone the repository
git clone https://github.com/JexinSam/mssql_mcp_server.git
cd mssql_mcp_server
# Set up a virtual environment
python -m venv venv
source venv/bin/activate # On Windows: venv\Scripts\activate
# Install development dependencies
pip install -r requirements-dev.txt
pip install -e .
# Run tests
pytest -v
# Test with MCP Inspector
uv run mcp dev src/mssql_mcp_server/server.py
Troubleshooting
"Program Not Found" Error
This usually means the mssql_mcp_server command is not in your PATH. Solutions:
- Use
uv(recommended): Configure your MCP client to useuv --directory path/to/mssql_mcp_server run mssql_mcp_server - Use full path: Find the install location with
pip show mssql-mcp-serverand use the scripts directory - Use
python -m: Run aspython -m mssql_mcp_server
MSSQL Driver Issues
The default driver is SQL Server (built into Windows). For Linux/macOS or newer features:
- Install Microsoft ODBC Driver 18
- Set
MSSQL_DRIVER="ODBC Driver 18 for SQL Server"
Connection Timeouts
If using MSSQL_SERVER from other projects, this server supports both MSSQL_HOST and MSSQL_SERVER env vars (with MSSQL_HOST taking priority).
Security Considerations
- Use a dedicated MSSQL user with minimal privileges.
- Never use root credentials or full administrative accounts.
- Restrict database access to only necessary operations (e.g. use
GRANT SELECTonly if the model should not modify data). ThereadOnlyHintanddestructiveHintannotations are for client UX; security is enforced entirely by your database credentials. - Enable logging and auditing for security monitoring.
- Regularly review permissions to ensure least privilege access.
Security Best Practices
For a secure setup:
- Create a dedicated MSSQL user with restricted permissions.
- Avoid hardcoding credentials—use environment variables instead.
- Restrict access to necessary tables and operations only.
- Enable SQL Server logging and monitoring for auditing.
- Review database access regularly to prevent unauthorized access.
For detailed instructions, refer to the MSSQL Security Configuration Guide.
⚠️ IMPORTANT: Always follow the Principle of Least Privilege when configuring database access.
License
This project is licensed under the MIT License. See the LICENSE file for details.
Contributing
We welcome contributions! To contribute:
- Fork the repository.
- Create a feature branch:
git checkout -b feature/amazing-feature - Commit your changes:
git commit -m 'Add amazing feature' - Push to the branch:
git push origin feature/amazing-feature - Open a Pull Request.
Need Help?
For any questions or issues, feel free to open a GitHub Issue or reach out to the maintainers.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.