Skip to main content
Glama
sql-mcp
by ohankay

Related Servers

Alternatives to sql-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to connect to SQL Server databases and execute arbitrary SQL operations, including queries, updates, table management, and script execution, through the Model Context Protocol.
      7
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to connect to Microsoft SQL Server for schema discovery, querying, stored procedures, DDL, performance diagnostics, and developer utilities with configurable security modes.
      35
      50 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables VS Code Copilot Chat and custom agents to perform MongoDB queries, writes, transactions, schema discovery, index and collection management, and administrative commands across multiple secure connection profiles without using mongosh or PowerShell.
      28
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to discover SQL Server connections from VS Code or Antigravity IDE, inspect databases, schemas, tables, views, and functions, and execute read-only T-SQL queries over stdio across multiple connections.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Microsoft SQL Server databases through a standardized interface. Supports executing SQL queries, browsing database schemas, and viewing table data with flexible authentication options for both local and Azure SQL databases.
      5
      MIT

    TDQS

    B3.2/5.0

    Scored across 30 tools

    Disambiguation4/5

    Each tool targets a distinct resource+action: connection management, query execution (execute_sql vs execute_procedure clearly separated), transaction control, metadata inspection, Agent jobs, and sessions. A few pairs have subtle overlap (list_jobs vs list_running_jobs, get_job vs get_job_history, update_job vs update_job_step), but descriptions sharpen the boundaries well.

    Naming Consistency4/5

    Almost entirely consistent verb_noun snake_case (list_connections, add_connection, create_job, delete_job_step, get_job_history, kill_session). The only deviation is transaction_status, which is noun-first, a minor blip in an otherwise predictable scheme.

    Tool Count3/5

    30 tools is heavy; the Agent-job surface alone consumes 14 tools (CRUD for jobs, steps, schedules, history, running). Each tool does something distinct, but the set is large enough that scope feels sprawling rather than tightly earned.

    Completeness4/5

    Broad and well-rounded: connection CRUD, arbitrary T-SQL, procedure execution, full transaction lifecycle, metadata (databases/objects/describe_table/definitions), full Agent job lifecycle, and session monitoring. Minor gaps exist (no dedicated query-plan/EXPLAIN, no user/permission or index-management helpers), but execute_sql can cover most of these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues