Skip to main content
Glama
S-CurveLabs

io.github.S-CurveLabs/sqlglass

Official
by S-CurveLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to io.github.S-CurveLabs/sqlglass

No user-submitted related servers found.

    Related Servers

    • 多数据库 MCP Server

      CGAdmin544
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to securely query databases, list tables, inspect table schemas, and test connections across Oracle, SQL Server, MySQL, PostgreSQL, and SQLite using read-only SQL tools.
      4
      MIT

    • SqlAugur

      mbentham
      A
      license
      A
      quality
      B
      maintenance
      SQL Server MCP server with AST-based query validation, read-only safety, schema exploration, ER diagram generation, and DBA toolkit integration (First Responder Kit, DarlingData, sp_WhoIsActive).
      12
      6
      MIT

    • sql-explorer-mcp

      govern-agents
      A
      license
      Not graded
      quality
      F
      maintenance
      Read-only MCP server for SQL databases (SQL Server, Postgres, SQLite) with multi-server support and three-layer safety using AST validation and linting.
      MIT

    • mcp-sqlserver-readonly

      gbfeliped
      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

    • mssql-mcp-server

      ConnorBritain
      A
      license
      Not graded
      quality
      C
      maintenance
      Enterprise-grade MCP server for Microsoft SQL Server, enabling semantic schema discovery, table profiling, safe data operations with preview/confirm, and multi-environment support.
      33
      MIT

    • Database Assistant MCP Server

      vinycoolguy2015
      F
      license
      A
      quality
      C
      maintenance
      Enables read-only exploration and querying of PostgreSQL or MySQL databases via MCP, with schema discovery, safe SQL validation, natural language to SQL conversion, and CSV export.
      11
      1
      -
    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

    A3.7/5.0

    Scored across 29 tools

    Disambiguation5/5

    Every tool targets a distinct operation: schema discovery, query transformation, library management, DDL generation, and execution previews are cleanly separated. Even similar-looking tools like lint_sql vs lint_library or sample_table vs profile_table have clear boundaries. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tool names follow a consistent imperative verb_noun pattern in snake_case: list_*, build_*, lint_*, run_*, etc. Multi-word objects like find_join_path, rename_in_library, and preview_write are formatted the same way. There are no mixed casing styles or vague single-word verbs.

    Tool Count2/5

    At 29 tools, this far exceeds the comfortable working set, and the server would likely overwhelm an agent when deciding which tool to invoke. Several groups could be consolidated or split into separate servers (e.g., schema exploration, query library, SQL transformation, DDL generation). Each tool is purposeful, but the aggregate surface is too large.

    Completeness4/5

    The domain is well covered: schema introspection, query authoring and analysis, query-library CRUD with snapshots/undo, DDL script generation, and read-only execution plus write previews. Minor gaps exist such as no builders for functions/indexes and no MERGE preview, but these are niche and workable. Overall there are no dead-end workflows for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources