Connect Mssql MCP Server
Microsoft SQL Server database connectivity with dynamic, request-level credentials.
Data last scanned today · Reviewed today
Overview
Connect Mssql MCP Server provides an stdio-based bridge for executing SQL queries, retrieving table structures, and inspecting stored procedures or view definitions within Microsoft SQL Server environments. Its core architecture requires database connection parameters, such as IP and credentials, to be provided dynamically with each individual request, enabling flexible access across multiple databases. The server operates in a read-only mode by default to prioritize data integrity, with write capabilities requiring an explicit --enable-write flag during startup. It includes configuration templates for various AI development environments and supports usage via both local builds and npx execution.
Our verdict
With a security score of 27/100, this tool is categorized as high-risk. This classification reflects that it is community-maintained rather than official vendor software, and its authentication mechanisms and read-only implementation have not yet undergone editorial review. It is best suited for development or local sandboxed environments rather than sensitive production systems where rigorous security auditing is mandatory.
- Supports dynamic connection credentials on a per-request basis
- Defaults to read-only mode for enhanced security
- Requires only two direct dependencies, reducing supply-chain complexity
- Includes readily available configuration templates for multiple AI clients
- Security score of 27/100 indicates high risk
- Lacks third-party editorial or security review
- Community-maintained project with a single contributor
- No official verification of authentication security
Setup
{
"mcpServers": {
"connect-mssql-mcp": {
"args": [
"-y",
"connect-mssql-mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| query | 执行 SQL（默认只读） | medium |
| get_table_structure | 查看表结构 | low |
| get_procedure_content | 读取存储过程定义 | low |
| get_view_definition | 读取视图定义 | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›How do I enable write operations for this server?
By default, the server is read-only. You must include the --enable-write flag when starting the server to permit write operations.
›How are database credentials handled?
The server does not store credentials. Connection parameters, including IP, user, and password, must be provided dynamically with every individual request.
›Does the server support encrypted connections?
Yes, it is recommended to enable TLS by setting the encrypt option to true when configuring your connection in production environments.
›What tools are available for inspecting the database schema?
You can use get_table_structure to view table schemas, get_procedure_content to read stored procedure definitions, and get_view_definition to retrieve view definitions.
Changelog
- Securityv1.1.0
2026-02-28
Badge
Maintain this server? Add the live badge to your README.