Skip to main content
Glama
mlsloynaz

mcp-sqlserver

by mlsloynaz

Related Servers

Alternatives to mcp-sqlserver

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables interaction with Microsoft SQL Server instances using Windows or SQL Server authentication via native ODBC drivers. It allows users to execute SQL queries, list tables, and inspect schemas across multiple configured database environments through natural language.
      3,162 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server for exploring on-premises, multi-instance Microsoft SQL Server estates from AI clients, with read-only enforcement and Windows authentication support.
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables users to connect to Microsoft SQL Server databases and run SQL queries, inspect schemas, and retrieve results through MCP client tools.
      -
    • F
      license
      A
      quality
      C
      maintenance
      A read-only MCP server for browsing and querying SQL Server databases, providing tools to list schemas, tables, describe columns, and execute safe SELECT queries with validated parameters.
      15
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Read-only SQL Server MCP server enabling safe database queries, table listing, and schema inspection with built-in security protections.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A read-only-by-default Model Context Protocol (MCP) server for Microsoft SQL Server with schema discovery, SELECT-only queries, execution-plan analysis, and opt-in writes per profile. Profile-based configuration serves multiple databases and servers from one toolset deployment.
      9
      MIT

    TDQS

    A3.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: describe_table provides metadata for a specific table, list_tables enumerates available tables, and query executes arbitrary SELECT queries. There is no overlap in functionality, and an agent can easily differentiate between them based on their descriptions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (describe_table, list_tables, query). While 'query' is a single word, it functions as a verb in this context and maintains readability without deviating from the clear, descriptive naming style used throughout.

    Tool Count3/5

    With only 3 tools, the set feels thin for a SQL Server interface, which typically involves more operations like data manipulation (INSERT, UPDATE, DELETE) or schema modifications. However, the tools are well-scoped for read-only database interactions, making it borderline but not severely inadequate.

    Completeness2/5

    The tool surface is significantly incomplete for a SQL Server domain, as it only supports read operations (SELECT, metadata queries) without any write capabilities (INSERT, UPDATE, DELETE) or schema management tools. This creates notable gaps that could lead to agent failures when full database interactions are required.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues