Skip to main content
Glama
Sign In
sql-server-mcp

sql-server-mcp

by ahaugerud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to sql-server-mcp

No user-submitted related servers found.

    Related Servers

    • mssql-mcp

      MCopin
      A
      license
      Not graded
      quality
      D
      maintenance
      Local MCP server for running ad hoc T-SQL queries against SQL Server databases, read-only by default with security safeguards.
      1,382 npm
      MIT

    • powerbi-mcp-proxy

      AviHack
      A
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that proxies MCP clients to Power BI, using your own Entra tenant and Azure subscription. It enables DAX queries, workspace listing, and dataset management while preserving user-specific row-level security.
      2
      MIT

    • intune-mcp

      sdkamer
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only local MCP server that lets harnesses query Microsoft Intune devices, policies, apps, enrollment, and RBAC using the signed-in user's delegated Microsoft Graph access.
      Apache 2.0

    • @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
      63 npm
      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
    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.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: `query` for capped inline SELECTs, `export_query` for uncapped file output, `list_databases` for database enumeration, and `search_schema` for metadata lookup. The `query` vs `export_query` overlap is explicitly resolved by the description telling agents to prefer `export_query` for large results.

    Naming Consistency4/5

    Three tools follow a clear verb_noun pattern (`list_databases`, `search_schema`, `export_query`), while `query` is a bare verb/noun that slightly breaks the pattern. The deviation is minor and still readable in context.

    Tool Count5/5

    Four tools is well-scoped for a read-only SQL server interface, with each tool covering a distinct essential workflow: querying, exporting, listing databases, and searching schema metadata. Nothing feels redundant or missing at the count level.

    Completeness4/5

    The surface covers core read-only workflows well, including capped queries, large exports, database listing, and schema discovery via INFORMATION_SCHEMA. Minor gaps exist around dedicated table listing or describe-table convenience tools, but `search_schema` provides a workable path for those needs.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources