SQL Server Analyst MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 37 installs a week from npm.
Read-only SQL Server Analyst MCP — safe schema, stored procedure, and performance analysis.
The linked repository no longer exists on GitHub — it was deleted or made private.
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add sql-server-analyst-mcp -e 'MSSQL_SERVER=<MSSQL_SERVER>' -e 'MSSQL_USER=<MSSQL_USER>' -e 'MSSQL_PASSWORD=<MSSQL_PASSWORD>' -- npx -y sql-server-analyst-mcp
{
"mcpServers": {
"sql-server-analyst-mcp": {
"command": "npx",
"args": [
"-y",
"sql-server-analyst-mcp"
],
"env": {
"MSSQL_PASSWORD": "<MSSQL_PASSWORD>",
"MSSQL_SERVER": "<MSSQL_SERVER>",
"MSSQL_USER": "<MSSQL_USER>"
}
}
}
}
[mcp_servers.sql-server-analyst-mcp]
command = "npx"
args = ["-y", "sql-server-analyst-mcp"]
env = { MSSQL_SERVER = "<MSSQL_SERVER>", MSSQL_USER = "<MSSQL_USER>", MSSQL_PASSWORD = "<MSSQL_PASSWORD>" }
{
"mcpServers": {
"sql-server-analyst-mcp": {
"command": "npx",
"args": [
"-y",
"sql-server-analyst-mcp"
],
"env": {
"MSSQL_PASSWORD": "<MSSQL_PASSWORD>",
"MSSQL_SERVER": "<MSSQL_SERVER>",
"MSSQL_USER": "<MSSQL_USER>"
}
}
}
}
{
"servers": {
"sql-server-analyst-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"sql-server-analyst-mcp"
],
"env": {
"MSSQL_PASSWORD": "<MSSQL_PASSWORD>",
"MSSQL_SERVER": "<MSSQL_SERVER>",
"MSSQL_USER": "<MSSQL_USER>"
}
}
}
}
Put your own values in place of
<MSSQL_SERVER> (SQL Server hostname or FQDN (e.g. <name>.database.windows.net for Azure SQL)), <MSSQL_USER> (SQL authentication login name), <MSSQL_PASSWORD> (SQL authentication password. Quote values containing '#' in .env files).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
MSSQL_PORT (TCP port (default 1433; set 0 for named instance with dynamic port)), MSSQL_DATABASE (Default database to connect to. Most tools also accept an override argument), MSSQL_ENCRYPT (Encrypt the connection (true|false). Required true for Azure SQL), MSSQL_TRUST_SERVER_CERT (Trust self-signed certificates (true|false). Use true only for local dev), ALLOWED_DATABASES (Comma-separated allowlist of databases the server may access. Empty = unrestricted), ALLOWED_SCHEMAS (Comma-separated allowlist of schemas for schema tools. Empty = unrestricted), MAX_ROWS (Default row limit per safe query (default 100)), MAX_ROWS_LIMIT (Hard cap on query rows (default 1000)), QUERY_TIMEOUT_MS (Query execution timeout in milliseconds (default 30000)), LOG_LEVEL (error | warn | info | debug (default info)).
MCP server for SQL Server: schema inspection, safe read-only queries, query plan analysis
PostgreSQL MCP server for schema, query, health, security, and performance analysis.
Read-only MCP server for Microsoft SQL Server — schema discovery, profiling, safe querying
MCP server for SAP SQL Anywhere 17: explore schemas and run read-only queries.
Read-only MCP server for the Archery SQL audit platform: production schema and release SQL checks
Read-only MCP server for evidence-based PostgreSQL performance auditing.
MCP server for one MySQL database: schema, read-only queries and guarded writes.
Read-only MCP to diff SQL Server/Azure SQL schema, procs, views, and tables between environments.
Answers built from our own checks of this server.