GoSQLX
Infrastructure · tested 2026-09-27 · by the Hlido desk, not the vendor
In short: A fast, well-presented multi-dialect SQL parsing SDK for Go with a genuinely agent-first MCP surface — but its headline performance and traction numbers are vendor-asserted and, in one case, don't reconcile.
5 PASS · 0 FAIL of 5 public-surface claims
Quick answer
GoSQLX scores 75/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-09-27). STEADY (75) because the product is coherent, actively presented, open-source (Apache-2.0), and offers a real, keyless agent-integration path via MCP alongside a working in-page playground that demonstrated the core parse Pricing: Open source (free entry point documented).
GoSQLX is a developer library, not an AI product, yet it earns its place in an agent register: it ships a keyless, no-install remote MCP server (mcp.gosqlx.dev) exposing seven SQL tools — parse, format, validate, lint, analyze, injection-detect, list-dialects — to Claude, Cursor, or any MCP client, which is exactly the kind of narrow, composable capability agents can consume without ceremony. The public surface is strong: the in-page playground actually parsed a multi-table JOIN into a full AST during our capture, so the core function is demonstrable rather than merely claimed, and the project spreads across a Go SDK, CLI, VS Code extension, GitHub Lint Action, and WASM under Apache-2.0. Where it should be read with caution is the numbers. The marquee throughput figure (1.38M ops/sec, sub-microsecond latency) and the chart beating vitess and pg_query are self-reported benchmarks on the author's own Apple M4 hardware, and the dialect-coverage percentages are self-graded QA. More pointedly, the homepage advertises "1.2k GitHub Stars" while Hlido's scout recorded 111 stars for the same repository — a gap the public surface does not explain. None of this makes GoSQLX a weak tool; the design is coherent and the agent path is real. It does mean the performance and popularity claims are inputs to verify, not conclusions to trust, and Hlido ran no hands-on behavioral test of the MCP tools or SDK.
Why STEADY
STEADY (75) because the product is coherent, actively presented, open-source (Apache-2.0), and offers a real, keyless agent-integration path via MCP alongside a working in-page playground that demonstrated the core parse function. It is held below the top band because the review is a public-surface (medium-confidence) assessment with no hands-on behavioral run, every performance and coverage figure is vendor self-reported, and the homepage's advertised star count (1.2k) does not reconcile with the 111 stars Hlido's scout recorded — a traction discrepancy a buyer must resolve independently. VITAL is unreachable without hands-on behavioral testing Hlido did not perform.
Public-surface checklist
- PASS Homepage loads (required) — https://gosqlx.dev/ returned title 'GoSQLX - Production-Ready SQL Parsing SDK for Go'
- PASS Primary value prop (required) — 'Parse SQL at the speed of Go — Production-ready SQL parsing with zero-copy tokenization, object pooling, and multi-dialect support'
- PASS Cta present (required) — 'Get Started' and 'Try Playground' primary CTAs
- PASS Pricing or access — Open source (Apache-2.0 per repo badges); MCP server documented as free/keyless, no API key required. No paid pricing surface present.
- PASS Evidence or demo — Live in-page playground parsed a multi-table JOIN into a full AST ('Parsed in 78.80ms'); benchmarks and changelog pages linked
What we saw
4 screenshots captured by the Hlido engine during the reviewed run (run-79cf746840c262b9-gosqlx-dev). Our own captures — not vendor marketing material.
What it does well
- Ships a genuinely agent-first surface: a keyless, no-install remote MCP server (mcp.gosqlx.dev) exposing 7 SQL tools to Claude, Cursor, or any MCP client
- The in-page playground actually parsed a multi-table JOIN query into a complete AST during Hlido's capture — the core function is demonstrable, not just asserted
- Broad multi-dialect support presented clearly: PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite, Snowflake, and ClickHouse
- Multiple distribution channels — Go SDK, CLI, VS Code extension, GitHub Lint Action, and WASM — plus docs, changelog, and benchmarks pages
- Open source under Apache-2.0 with a clean, well-organised developer site and a simple, honest example API
What it fails at
- Headline throughput (1.38M ops/sec, <1µs latency) is a vendor self-reported benchmark on the author's Apple M4 hardware — Hlido did not reproduce it
- The comparative chart beating vitess, pg_query, and sqlparser is unsourced beyond "BenchmarkParse, Apple M4, Go 1.26"
- Homepage traction is inconsistent: it advertises "1.2k GitHub Stars" while Hlido's scout recorded 111 stars for the repository, unexplained on the public surface
- Per-dialect coverage percentages (80%–100%) are self-graded QA figures with no external validation
- No hands-on behavioral run of the MCP tools or SDK, so runtime correctness, thread-safety, and race-free claims remain asserted rather than confirmed here
Red flags
- The homepage advertises "1.2k GitHub Stars" but Hlido's scout recorded 111 stars for the same repository (ajitpratap0/GoSQLX) on 2026-08-26. A traction figure a buyer cannot reconcile from the public surface should be independently verified before it is relied upon.
Best for
- Go developers who need an embeddable, multi-dialect SQL parser, formatter, and linter
- Agent builders who want SQL parsing, validation, and injection-detection tools available over MCP without provisioning an API key
- Teams building SQL tooling — linters, analyzers, IDE integrations — on top of a shared AST
- Workflows that need SQL security scanning (injection detection with severity classification) as a component
Not recommended for
- Teams that require independently reproduced performance benchmarks before adoption
- Non-Go stacks needing a native library (the MCP server and WASM build only partially bridge this)
- Buyers who treat published star/traction counts as a due-diligence signal — the figures here do not reconcile
- Production use where correctness must be verified by hands-on testing rather than vendor QA claims
Pricing & access
- ModelOpen source
- Free entry pointYes — a free tier or open-source edition is documented
- Pricing findable on the public surfacePASS Open source (Apache-2.0 per repo badges); MCP server documented as free/keyless, no API key required. No paid pricing surface present. (tested 2026-08-28)
Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-28.
Related agents
Agent relevance
API CLI MCP SDK Behavioral-testable
Primary agent path is a keyless, no-install remote MCP server (https://mcp.gosqlx.dev/mcp) exposing 7 SQL tools (parse_sql, format_sql, validate_sql, lint_sql, analyze_sql, detect_injection, list_dialects) consumable by Claude, Cursor, or any MCP client. Beyond MCP, GoSQLX ships as a Go SDK (github.com/ajitpratap0/GoSQLX), a CLI, a VS Code extension, a GitHub Lint Action, and a WASM build, plus an interactive web playground. It is a developer library rather than an AI product, but the MCP surface makes its parsing/validation/injection-detection capabilities directly agent-consumable.
Agent-friendly score: 8/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.
Evidence
- GoSQLX is a production-ready, multi-dialect SQL parsing SDK for Go (v1.14.0), 'Parse SQL at the speed of Go' with zero-copy tokenization and object pooling — source (2026-09-27) verified
- Documents a keyless, no-install remote MCP server (claude mcp add --transport http gosqlx https://mcp.gosqlx.dev/mcp) exposing 7 SQL tools: parse_sql, format_sql, validate_sql, lint_sql, analyze_sql, detect_injection, list_dialects, for Claude, Cursor, or any MCP client — source (2026-09-27) verified
- Performance of 1,379,878+ ops/sec with <1µs latency, benchmarked on Apple M4, Go 1.26, outperforming vitess/pg_query/sqlparser — source (2026-09-27)
- Traction stat '1.2k GitHub Stars' — source (2026-09-27)
- Supports 8 SQL dialects with coverage from 80% (Oracle) to 100% (Snowflake, 87/87 QA) — source (2026-09-27)



