L
laaielichter/Gulliver
Test on tiny data before you run on giant data.
★ 2·updated 2026-11-18
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 2 ★ · laaielichter/Gulliver · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 2 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
laaielichter/Gulliver;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
Gulliver
Excerpted from the repository README (abridged)
Test on tiny data before you run on giant data.
An open-source MCP server and CLI that gives AI agents a dress rehearsal for SQL: estimate the cost, fix the slow parts, rehearse on 1% → 3% → 10% of the data, predict what 100% will do, and only run the full query inside a budget.
Website ·
Quick start ·
Install ·
Auto-fix ·
Guards ·
CI ·
Compare ·
FAQ ·
Roadmap
Works with Claude Code , Codex , Cursor , Gemini CLI , Claude Desktop, VS Code, Windsurf and any MCP client, on DuckDB , Postgres , BigQuery and Snowflake .
> New in 0.4.0: data quality checks you define once in gulliver.toml and run in CI with
> gulliver check --all, gulliver lint --baseline so an existing repo only sees new findings, gulliver prune,
> gulliver calibration, gulliver receipt --list, column-level gulliver diff, lint rules GV016-GV018, and
> refusal of bad budgets, unknown config keys and out-of-range flags instead of silently misreading them. See the
> changelog.
> In 0.3.0: a read-only gate that also blocks side-effect functions, SQL hidden in strings and file
> access, with DuckDB sandboxed in the engine. A result guard for personal data and prompt injection in rows. A
> runaway guard for loops and per-agent budgets. Lint for CI (SARIF, pre-commit), gulliver fix --verify,
> gulliver top, and gulliver review with a GitHub Action. One breaking change in 0.3.0: DuckDB can no
> longer read files outside the database folder and the current folder unless you allow them
> (details).
A real recording of the CLI on the demo database (script: docs/demo.sh).
> In Gulliver's Travels, Gulliver visits Lilliput, a land of tiny people, and Brobdingnag, a land of giants.
> Gulliver does the same with your data: it tries your query in Lilliput first, and only walks into Brobdingnag
> when it knows what will happen there.
## Why
Agents write SQL that works on a small table and breaks on a big one. They do not know that events has
5 billion rows, that a join multiplies rows, or that a forgotten partition filter scans every day since 2019.
Benchmarks score agents on is the answer right, never on what did it cost or does it still work at 100x.
One unlucky query can burn a monthly budget.
Gulliver sits between the agent and the warehouse:
| Step | Tool | What happens |
| 1 | gulliver_inspect | Which tables are big? Rows, bytes, partitions, columns. Metadata only, free. |
| 2 | gulliver_preflight | Bytes, rows and money before running, plus scale lint (15 rules), the read-only gate and the budget gate. When a safe rewrite exists, the answer already contains the fixed SQL (autofix). |
| 3 | gulliver_rehearse | Runs the query on 1%, 3% and 10% samples, fits a growth curve and predicts the full run with a confidence range. Catches joins that multiply rows. |
| 4 | gulliver_run | Runs the full query only inside the budget. Otherwise answers needs_rehearsal or needs_approval. The rows come back marked as untrusted data, with secrets masked and personal data flagged. |
| 5 | gulliver_receipt | Markdown proof for the human: what was estimated, rehearsed, approved and run, and predicted vs actual. |
Every answer has a status and a next_step, so even small models know what to do next.
An open-source MCP server and CLI that gives AI agents a dress rehearsal for SQL: estimate the cost, fix the slow parts, rehearse on 1% → 3% → 10% of the data, predict what 100% will do, and only run the full query inside a budget.
Website ·
Quick start ·
Install ·
Auto-fix ·
Guards ·
CI ·
Compare ·
FAQ ·
Roadmap
Works with Claude Code , Codex , Cursor , Gemini CLI , Claude Desktop, VS Code, Windsurf and any MCP client, on DuckDB , Postgres , BigQuery and Snowflake .
> New in 0.4.0: data quality checks you define once in gulliver.toml and run in CI with
> gulliver check --all, gulliver lint --baseline so an existing repo only sees new findings, gulliver prune,
> gulliver calibration, gulliver receipt --list, column-level gulliver diff, lint rules GV016-GV018, and
> refusal of bad budgets, unknown config keys and out-of-range flags instead of silently misreading them. See the
> changelog.
> In 0.3.0: a read-only gate that also blocks side-effect functions, SQL hidden in strings and file
> access, with DuckDB sandboxed in the engine. A result guard for personal data and prompt injection in rows. A
> runaway guard for loops and per-agent budgets. Lint for CI (SARIF, pre-commit), gulliver fix --verify,
> gulliver top, and gulliver review with a GitHub Action. One breaking change in 0.3.0: DuckDB can no
> longer read files outside the database folder and the current folder unless you allow them
> (details).
A real recording of the CLI on the demo database (script: docs/demo.sh).
> In Gulliver's Travels, Gulliver visits Lilliput, a land of tiny people, and Brobdingnag, a land of giants.
> Gulliver does the same with your data: it tries your query in Lilliput first, and only walks into Brobdingnag
> when it knows what will happen there.
## Why
Agents write SQL that works on a small table and breaks on a big one. They do not know that events has
5 billion rows, that a join multiplies rows, or that a forgotten partition filter scans every day since 2019.
Benchmarks score agents on is the answer right, never on what did it cost or does it still work at 100x.
One unlucky query can burn a monthly budget.
Gulliver sits between the agent and the warehouse:
| Step | Tool | What happens |
| 1 | gulliver_inspect | Which tables are big? Rows, bytes, partitions, columns. Metadata only, free. |
| 2 | gulliver_preflight | Bytes, rows and money before running, plus scale lint (15 rules), the read-only gate and the budget gate. When a safe rewrite exists, the answer already contains the fixed SQL (autofix). |
| 3 | gulliver_rehearse | Runs the query on 1%, 3% and 10% samples, fits a growth curve and predicts the full run with a confidence range. Catches joins that multiply rows. |
| 4 | gulliver_run | Runs the full query only inside the budget. Otherwise answers needs_rehearsal or needs_approval. The rows come back marked as untrusted data, with secrets masked and personal data flagged. |
| 5 | gulliver_receipt | Markdown proof for the human: what was estimated, rehearsed, approved and run, and predicted vs actual. |
Every answer has a status and a next_step, so even small models know what to do next.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/laaielichter-gulliver/)
- Source
- awesome · https://github.com/laaielichter/Gulliver
- Browse by field
- MCP servers
- Traction
- 2 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.