A read-only MCP server for SQL Server that lets you safely analyze database internals without risking writes. You get schema inspection, stored procedure analysis, and performance monitoring capabilities through a stdio transport. Reach for this when you're troubleshooting query performance, documenting database structure, or need Claude to understand your SQL Server setup without granting modification privileges. The read-only constraint makes it safer to connect to production databases for diagnostic work. Good fit for DBAs and backend developers who want AI assistance with SQL Server analysis tasks while maintaining strict safety boundaries.
MSSQL_SERVER*SQL Server hostname or FQDN (e.g. <name>.database.windows.net for Azure SQL).
MSSQL_PORTTCP port (default 1433; set 0 for named instance with dynamic port).
MSSQL_DATABASEDefault database to connect to. Most tools also accept an override argument.
MSSQL_USER*SQL authentication login name.
MSSQL_PASSWORD*secretSQL authentication password. Quote values containing '#' in .env files.
MSSQL_ENCRYPTEncrypt the connection (true|false). Required true for Azure SQL.
MSSQL_TRUST_SERVER_CERTTrust self-signed certificates (true|false). Use true only for local dev.
ALLOWED_DATABASESComma-separated allowlist of databases the server may access. Empty = unrestricted.
ALLOWED_SCHEMASComma-separated allowlist of schemas for schema tools. Empty = unrestricted.
MAX_ROWSDefault row limit per safe query (default 100).
MAX_ROWS_LIMITHard cap on query rows (default 1000).
QUERY_TIMEOUT_MSQuery execution timeout in milliseconds (default 30000).
LOG_LEVELerror | warn | info | debug (default info).
hovecapital/read-only-local-postgres-mcp-server
cocaxcode/database-mcp
io.github.infoinlet-marketplace/mcp-mysql
io.github.cybeleri/database-admin
io.github.yash-0620/postgres-mcp-secured