Skip to main content
Glama
elekto-com-br

Elekto MCP for SQL Server

Official
by elekto-com-br
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Elekto MCP for SQL Server

No user-submitted related servers found.

    Related Servers

    • @dudqls816/database-mcp

      gong-yeongbin
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Microsoft SQL Server that lets LLMs explore schema and execute read-only SELECT queries, with optional stored procedure execution when explicitly enabled.
      3
      41 npm
      MIT

    • DBMCP

      jesse-smith
      A
      license
      A
      quality
      D
      maintenance
      MCP server providing read-only access to SQL Server databases for AI assistants, enabling schema exploration, query execution, and foreign key inference with token-efficient TOON responses.
      9
      1
      MIT

    • mcp-sqlserver

      kyle66889
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server for Microsoft SQL Server that enables AI agents to safely explore and query SQL Server databases.
      785 npm
      MIT

    • mssql-mcp

      is-jvelez
      A
      license
      B
      quality
      C
      maintenance
      Read-only MCP server for exploring and analyzing SQL Server objects (tables, views, triggers, stored procedures) from Claude Code.
      8
      1,313 npm
      MIT
    • io.github.S-CurveLabs/sqlglass by S-CurveLabs

      io.github.S-CurveLabs/sqlglassofficial

      S-CurveLabs
      A
      license
      A
      quality
      C
      maintenance
      Enables safe read-only interaction with SQL Server and Azure SQL databases, providing schema exploration, query linting and analysis, query plan insights, write previews as SELECTs, and a versioned library of .sql queries via MCP.
      29
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: list_* tools are per object type, get_*_definition tools return text for specific object types, and dependency tools split cleanly into data (get_dependency_graph), diagram (generate_dependency_dot), and single-table usage (get_table_usage). The descriptions explicitly cross-reference overlapping-sounding tools (e.g., get_database_overview vs get_schema_summary, get_table_schema vs get_view_definition) to remove ambiguity.

    Naming Consistency5/5

    All 21 tool names use snake_case with a consistent verb_noun pattern (list_*, get_*, check_*, find_*, generate_*, compare_*, query_*). There is no mixing of camelCase or vague verb styles, making the set highly predictable.

    Tool Count4/5

    21 tools is on the heavy side for a typical MCP server, but the breadth of SQL Server introspection (databases, schemas, tables, views, procedures, functions, columns, dependencies, permissions, profiling, indexing, comparison) largely justifies each tool. A few pairs (e.g., list_procedures/list_functions, get_database_overview/get_schema_summary) could be merged with parameters, so the set is slightly over-scoped.

    Completeness4/5

    The read-only exploration surface is broad, covering major object types from listing through definition to usage and impact analysis. Notable gaps remain for triggers, synonyms, sequences, and other code objects, though agents can often work around these by querying system views with query_table.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources