sqlglass

io.github.S-CurveLabsPublished by GitHub account S-CurveLabsv0.1.0Updated Oct 28, 2026

SQL Server / Azure SQL for agents: real schema, lint, read-only runs, plans, write previews.

VerifiedSTDIODesktop onlyDatabases

Overview

AI-generated overview

Local MCP server that gives an assistant SQL Server and Azure SQL access: real schema, linting, read-only queries, plans and write previews.

What you can do
  • Inspect the real schema of SQL Server and Azure SQL databases
  • Lint SQL statements before running them
  • Run read-only queries and review execution plans
  • Preview write statements without applying them
  • Use connection definitions from a sqlglass.toml configuration file
When to use it
Useful when an assistant needs to work against SQL Server or Azure SQL databases and you want it to see actual schema, check queries before execution, and preview writes rather than change data directly.
Requirements
Runs as a local process, installed from the sqlglass PyPI package, so a Python environment is needed. Connections are defined in a sqlglass.toml file, located via the SQLGLASS_CONFIG environment variable or found in the workspace or user data folder. Desktop only; no authentication is declared.
Before you install
The configuration file holds database connection definitions, so treat it as sensitive. Write operations are described as previews only, but confirm that no tool actually applies changes before pointing it at production data. Queries and schema details are sent to the database server you configure.

Installation

In SourceWeft

  1. Open sqlglass in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.