mcp-sqlserver
Related Servers
Alternatives to mcp-sqlserver
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server that connects AI assistants to Microsoft SQL Server databases, enabling schema exploration and read-only queries safely.495 npm4MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI assistants to query and manage Microsoft SQL Server databases using natural language.184 npm5MIT
- -licenseNot gradedqualityCmaintenanceAn MCP server that bridges AI assistants with SQL databases, enabling natural language querying across multiple database types with built-in optimization and security.3-
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for Microsoft SQL Server that enables AI agents to safely explore and query SQL Server databases.623 npmMIT
- AlicenseNot gradedqualityCmaintenanceCross-platform MCP server for SQL Server that enables AI assistants to explore schemas, relationships, and run read-only queries via natural language.1MIT
- AlicenseAqualityNot gradedmaintenanceEnables AI assistants to interact with both local SQL Server and Azure SQL Database through natural language, supporting queries, data manipulation, and schema operations with built-in security features.82,887 npm1-
TDQS
Scored across 38 tools
Each tool has a clear, distinct purpose, covering different aspects of SQL Server management like schema comparison, query execution, performance monitoring, and code generation. No two tools appear to do the same thing, and descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., describe_table, get_indexes, execute_query). This makes it easy for agents to predict and understand the function of each tool.
With 38 tools, the server is overly heavy for typical MCP usage. While the scope is broad, this many tools can overwhelm agents and slow down selection. A more focused set of 15-25 would be more appropriate.
The tool set covers a wide range of SQL Server operations: discovery, querying, mutation, monitoring, maintenance, and code generation. Minor gaps exist (e.g., no DDL operations like create/alter table or kill session), but the core needs are well addressed.