Skip to main content
Glama

MSSQL MCP Server

License: MIT TypeScript Node.js

A Model Context Protocol (MCP) server that enables AI assistants to interact with both local SQL Server and Azure SQL Database through natural language.

πŸš€ What Makes This Special?

This MCP server solves a critical limitation of existing solutions by supporting both local SQL Server and Azure SQL Database connections. While the original Azure-Samples implementation only works with Azure SQL Database, this enhanced version enables:

  • 🏠 Local Development: Connect to local SQL Server instances using username/password authentication

  • ☁️ Azure Cloud: Full Azure SQL Database support with Azure AD authentication

  • πŸ”„ Seamless Switching: Use the same tools for both environments

Quick Example:

You: "Show me all customers from New York"
AI: *securely queries your database and returns results in plain English*

You: "Create a table for storing product reviews"
AI: *generates and executes the appropriate CREATE TABLE statement*

πŸ“¦ Quick Start

Prerequisites

  • Node.js 18+

  • SQL Server (local) or Azure SQL Database

  • AI Assistant: Claude Desktop or VS Code Agent

Installation

git clone https://github.com/Nirmal123K/mssql-mcp.git
cd mssql-mcp-server
npm install && npm run build

Configuration

Local SQL Server:

export SERVER_NAME="localhost"
export DATABASE_NAME="your_database"
export SQL_USER="your_username"
export SQL_PASSWORD="your_password"
export TRUST_SERVER_CERTIFICATE="true"

Azure SQL Database:

export SERVER_NAME="your-server.database.windows.net"
export DATABASE_NAME="your_database"
# Uses Azure AD authentication (run 'az login' first)

βš™οΈ AI Assistant Setup

Claude Desktop

Add to claude_desktop_config.json:

Local SQL Server:

{
  "mcpServers": {
    "mssql": {
      "command": "node",
      "args": ["/path/to/mssql-mcp-server/dist/index.js"],
      "env": {
        "SERVER_NAME": "localhost",
        "DATABASE_NAME": "your_database",
        "SQL_USER": "your_username",
        "SQL_PASSWORD": "your_password",
        "TRUST_SERVER_CERTIFICATE": "true"
      }
    }
  }
}

Azure SQL Database:

{
  "mcpServers": {
    "mssql": {
      "command": "node",
      "args": ["/path/to/mssql-mcp-server/dist/index.js"],
      "env": {
        "SERVER_NAME": "your-server.database.windows.net",
        "DATABASE_NAME": "your_database",
        "READONLY": "true"
      }
    }
  }
}

VS Code Agent

Create .vscode/mcp.json with similar configuration using "type": "stdio".

Config Locations:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

πŸ“‹ Environment Variables

Variable

Required

Description

Example

SERVER_NAME

βœ…

SQL Server hostname

localhost or server.database.windows.net

DATABASE_NAME

βœ…

Target database name

MyDatabase

SQL_USER

πŸ”„

Username (local SQL Server only)

sa or myuser

SQL_PASSWORD

πŸ”„

Password (local SQL Server only)

MyPassword123!

READONLY

❌

Restrict to read-only operations

true or false (default)

TRUST_SERVER_CERTIFICATE

❌

Trust self-signed certificates

true or false (default)

πŸ”„ = Required for local SQL Server, not needed for Azure SQL Database

βœ… Verification

# Test the MCP server
echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}' | node dist/index.js

πŸ› οΈ Available Tools

Tool

Purpose

Example

read_data

Query data with SELECT

"Show customers from New York"

insert_data

Add new records

"Insert new product with price $99"

update_data

Modify existing data

"Update order status to shipped"

create_table

Create new tables

"Create table for reviews"

create_index

Add database indexes

"Create index on customer email"

drop_table

Remove tables

"Drop temporary table"

list_tables

Show all tables

"What tables exist?"

describe_table

Show table structure

"Describe customers table"

Security Features:

  • βœ… SQL injection prevention

  • βœ… Query validation and sanitization

  • βœ… Required WHERE clauses for updates

  • βœ… Read-only mode support

πŸ“š Documentation

For detailed information, see our comprehensive guides:

οΏ½ Credits and Attribution

Original Work

This project is a fork of the Azure-Samples/SQL-AI-samples repository, specifically building upon the MssqlMcp implementation created by Microsoft and the Azure team.

  • Original Repository: Azure-Samples/SQL-AI-samples

  • Original Authors: Microsoft Corporation and the Azure team

  • Original License: MIT License

  • Original Focus: Azure SQL Database with Azure AD authentication

Key Enhancement

This fork extends the original Azure-only MCP server to support local SQL Server databases with username/password authentication, making it accessible for:

  • 🏠 Local Development: Connect to local SQL Server instances

  • 🏒 On-Premises Deployments: Support enterprise SQL Server installations

  • πŸ”„ Hybrid Environments: Seamlessly switch between local and Azure databases

  • πŸš€ Broader Accessibility: Remove Azure dependency for local development

What We Added

Feature

Original Repository

This Fork

Azure SQL Database

βœ… Azure AD only

βœ… Azure AD support

Local SQL Server

❌ Not supported

βœ… Username/password auth

Authentication Methods

1 (Azure AD)

3 (Azure AD, SQL Server, Windows)

Target Audience

Azure users only

Local + Azure + On-premises

Development Setup

Requires Azure account

Works with local SQL Server

Acknowledgments

We are deeply grateful to Microsoft and the Azure team for creating the foundational architecture, security implementation, and tool design that made this enhanced version possible.

This enhanced version would not exist without their excellent foundational work.


License: MIT License - see LICENSE file for details.

Available Tools

8 tools
create_indexC

Creates an index on a specified column or columns in an MSSQL Database table

Inputs: columns (required), indexName (required), tableName (required), isClustered, +2 more.

create_tableC

Creates a new table in the MSSQL Database with the specified columns.

Inputs: columns (required), tableName (required).

describe_tableA

Describes the schema (columns and types) of a specified MSSQL Database table.

Inputs: tableName (required).

drop_tableC

Drops a table from the MSSQL Database.

Inputs: tableName (required).

insert_dataA

Inserts data into an MSSQL Database table. Supports both single record insertion and multiple record insertion using standard SQL INSERT with VALUES clause. FORMAT EXAMPLES: Single Record Insert: { "tableName": "Users", "data": { "name": "John Doe", "email": "john@example.com", "age": 30, "isActive": true, "createdDate": "2023-01-15" } } Multiple Records Insert: { "tableName": "Users", "data": [ { "name": "John Doe", "email": "john@example.com", "age": 30, "isActive": true, "createdDate": "2023-01-15" }, { "name": "Jane Smith", "email": "jane@example.com", "age": 25, "isActive": false, "createdDate": "2023-01-16" } ] } GENERATED SQL FORMAT:

  • Single: INSERT INTO table (col1, col2) VALUES (@param1, @param2)

  • Multiple: INSERT INTO table (col1, col2) VALUES (@param1, @param2), (@param3, @param4), ... IMPORTANT RULES:

  • For single record: Use a single object for the 'data' field

  • For multiple records: Use an array of objects for the 'data' field

  • All objects in array must have identical column names

  • Column names must match the actual database table columns exactly

  • Values should match the expected data types (string, number, boolean, date)

  • Use proper date format for date columns (YYYY-MM-DD or ISO format)

Inputs: data (required), tableName (required).

list_tableC

Lists tables in an MSSQL Database, or list tables in specific schemas

Inputs: parameters.

read_dataA

Executes a SELECT query on an MSSQL Database table. The query must start with SELECT and cannot contain any destructive SQL operations for security reasons.

Inputs: query (required).

update_dataB

Updates data in an MSSQL Database table using a WHERE clause. The WHERE clause must be provided for security.

Inputs: tableName (required), updates (required), whereClause (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: create_index (index creation), create_table (table creation), describe_table (schema inspection), drop_table (table deletion), insert_data (data insertion), list_table (table listing), read_data (data querying), and update_data (data modification). The tools cover different aspects of database operations without overlap.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., create_table, describe_table, drop_table, insert_data, list_table, read_data, update_data). The naming is uniform and predictable, making it easy for agents to understand the action and target resource.

    Tool Count5/5

    With 8 tools, this server is well-scoped for MSSQL database operations. Each tool serves a specific and necessary function in the domain, such as table management, data manipulation, and schema inspection, without being overly sparse or bloated.

    Completeness4/5

    The tool set provides strong coverage for core database operations, including table lifecycle (create, describe, list, drop), data CRUD (insert, read, update), and index creation. A minor gap exists with no explicit tool for deleting data (e.g., delete_data) or managing indexes beyond creation, but agents can work around this using update_data or other methods.

    Related MCP Connectors