Skip to main content
Glama
is-jvelez

mssql-mcp

by is-jvelez

Related Servers

Alternatives to mssql-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for SQL Server database introspection that enables Claude to explore and query databases via tools like listing objects and executing SELECT queries.
      20
      1
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      A read-only MCP server for SQL Server and PostgreSQL that enables exploring and querying databases (schemas, tables, views, procedures, indexes, foreign keys) and running arbitrary SELECT queries.
      37
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes SQL Server databases to Claude, allowing natural language queries with tools to list tables, describe schemas, and run read-only SELECT statements.
      -
    • F
      license
      A
      quality
      D
      maintenance
      MCP server for connecting to SQL Server in readonly mode. Allows any MCP client to explore the schema and run SELECT queries against a SQL Server database.
      6
      -
    • 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
    • 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
      -

    TDQS

    B3.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource type (tables, views, triggers, SPs) or action (list, get definition, get dependencies, run query). get_table_definition and get_object_definition are separated clearly for tables vs. code objects. No overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: list_* for enumerating objects, get_* for retrieving definitions/dependencies, and run_select_query for queries. The naming is predictable and uniform.

    Tool Count5/5

    With 8 tools, the server is well-scoped for its purpose: browsing database metadata and running read-only queries. Each tool earns its place and the count is neither too thin nor overwhelming.

    Completeness5/5

    The tool set covers the full read-only lifecycle: listing all object types, retrieving table schemas and code definitions, analyzing dependencies, and executing SELECT queries. There are no obvious gaps for the stated domain of database exploration.

    Maintenance

    ActivityStale
    ResponsivenessNo issues