⚡ exasol-quickstart
Run Exasol with AI — in one command.
A full Exasol analytics database, an LLM-ready MCP server, and JSON-native SQL — set up the right way for your OS, in minutes.
⚡ Get started
▶️ Try it — runs once, nothing installed:
pipx run exasol-quickstart
…or, if you prefer uv:
uvx exasol-quickstart
📌 Keep it — installs the command so you can run it again later:
pipx install exasol-quickstart && exasol-quickstart
…or, with uv:
uv tool install exasol-quickstart && exasol-quickstart
Every form detects your OS, provisions Exasol the right way, and prints the endpoints. No flags. No multi-step setup.
🎁 What you get
exasol-quickstart -> three services on one shared network:
+----------------------+ +----------------------+ +----------------------+
| Exasol (database) | | MCP server | | JSON Tables |
| 127.0.0.1:8563 | | :4896/mcp | | JSON -> SQL |
+----------------------+ +----------------------+ +----------------------+
| Component | Endpoint | Purpose |
|---|---|---|
| 🗄️ Exasol (database) | 127.0.0.1:8563 — sys / exasol |
the Exasol SQL engine |
| 🤖 MCP Server | http://127.0.0.1:4896/mcp |
connect Claude / any MCP client to the database |
| 📦 JSON Tables | exasol-quickstart json-tables ... |
ingest JSON and query it as SQL |
Web UI: https://127.0.0.1:8443
✅ Requirements
The only thing you always need is Python 3.9+ with pipx:
python -m pip install --user pipx
python -m pipx ensurepath # then reopen the terminal
From there, exasol-quickstart picks how Exasol runs, per platform:
| Operating system | How Exasol runs | Docker |
|---|---|---|
| 🪟 Windows | Exasol Nano, in a container | required (no native Windows engine exists) |
| 🍎 macOS (Apple Silicon) | Exasol Personal, in a native VM | not required (experimental) |
| 🐧 Linux | Exasol Nano, in a container (native install planned) | required for now |
The container path is fully tested today; the macOS native path is experimental and not yet validated end to end.
🛠️ Usage
exasol-quickstart # full stack: database + MCP + JSON Tables
exasol-quickstart --no-json-tables # database + MCP only
exasol-quickstart --dry-run # print the plan, change nothing
exasol-quickstart --base <name> # force a base: nano-docker | personal | nano-native
exasol-quickstart json-tables --help # run the JSON Tables CLI
Ingest some JSON:
docker cp data.json exasol-quickstart-json-tables:/workspace/data.json
exasol-quickstart json-tables ingest-and-wrap --input /workspace/data.json --name demo
# then query it: SELECT * FROM "EJT_DEMO_VIEW"."demo";
Stop & remove everything:
docker rm -f exasol-quickstart-db exasol-quickstart-mcp exasol-quickstart-json-tables
🧩 How it works
exasol-quickstart is a single front-door command that detects the platform and assembles the stack:
- With Docker — Exasol Nano (database), the official
exasol/mcp-serverimage, and a JSON Tables sidecar run as containers on a shared network. Tested end to end, including ingest. - Without Docker — macOS uses Exasol Personal (a native VM); Linux uses a native Nano install (planned). The add-ons run as isolated host environments.
MCP Server and JSON Tables have incompatible pyexasol requirements, so each runs in isolation — a separate container, or a separate host environment — never a shared Python environment.
Metadata
Release files for exasol-quickstart 0.3.14
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| exasol_quickstart-0.3.14.tar.gz | 11.9 kB | With provenance | Details for exasol_quickstart-0.3.14.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| exasol_quickstart-0.3.14-py3-none-any.whl | Python 3 | none | any | Details for exasol_quickstart-0.3.14-py3-none-any.whl |
Total release size: 23.4 kB
Release files / exasol_quickstart-0.3.14.tar.gz
| Download URL | exasol_quickstart-0.3.14.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24ea62cba75459445673107e398ca8f7c192fcae7f7aeebcc1d0b38d1f32c055
|
|
BLAKE2b-256 checksum How to use checksums |
8a1671139d01e357eb996a8e1c6c71110c119d2320aaab07778b55e38f4823b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 26, 2026.
Transparency logRelease files / exasol_quickstart-0.3.14-py3-none-any.whl
| Download URL | exasol_quickstart-0.3.14-py3-none-any.whl |
|---|---|
| Size | 11.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2425ecb28907e101fc9430ff316ae7fea29e00683733e6e684b474689b29975e
|
|
BLAKE2b-256 checksum How to use checksums |
795bfd447a7c45123d00e790642dc2d13a2d2f9cf2d3f5901c437e6e73211229
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 26, 2026.
Transparency logSecurity for exasol-quickstart 0.3.14
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for exasol_quickstart-0.3.14.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.