Labsco
MCP SERVER

SQL Analyzer

by j4c0bs

Check SQL before it runs, move it between dialects, and read back exactly which tables and columns a query touches.

Data Platform: Pipelines, Warehousing, BI & Governance
Summary
A syntax check for SQL an assistant just wrote.

The failure mode this addresses is a plausible-looking query that is wrong for your engine. Because nothing connects to a database, the check is safe to run on statements you have not decided to trust yet — and the same parse tells you which tables the query would have touched.

What it is

Static SQL analysis built on SQLGlot. It parses a statement without connecting to any database, so validation, dialect conversion and reference extraction all happen before anything executes.

What you get
  • Syntax validation with the line and column of the error when there is one
  • Conversion of a statement from one SQL dialect to another
  • Every table and CTE a query references
  • Every column reference in the query
  • Dialect-aware parsing, so 'valid' means valid for the engine you named
Requirements

Uvx on your PATH. No database connection and no credentials — it reads the SQL text, not your data.