Basalt MCP server
io.github.joshiii-xyz/basalt·v0.1.6·1 starsLocal SQL workspaces with bounded, recoverable writes for coding agents.
1 stars
Reviews
Write oneNobody has reviewed Basalt yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Basalt tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
How Basalt compares
Against every graded Databases MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 60% of 802 Databases servers
- GitHub stars
- 1
- more than 45% of 602 Databases servers
Install Basalt in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Basalt repository's README, as published. We do not edit it. Read it on GitHub
Basalt A CLI-first local SQL workspace for structured data and coding agents.
Basalt is an embedded SQL database and command-line application built from scratch in Rust. It provides a small library API, an interactive shell, durable storage, snapshot-isolated transactions, crash recovery, portable structured-data workspaces, and a stdio MCP server for local AI agents. It is not a SQLite-compatible replacement or a hosted database.
Highlights
aggregates, aliases, and transaction statements.
- SQL lexer and recursive-descent parser with expressions, joins, grouping,
indexes.
- Atomic statement execution with primary-key, UNIQUE, and user-created
state after a process crash.
- Snapshot-isolated transactions with optimistic conflict detection.
- Checksummed page snapshots and a write-ahead log that recovers committed
SQL dump import/export.
- Simple query planning with table scans, equality indexes, and range indexes.
- Interactive and scriptable CLI output in table, CSV, and JSON-lines formats.
- Portable workspaces with versioned metadata and atomic CSV, JSON/JSONL, and
exports, engine-bounded SQL, schema resources, and recoverable agent changes.
- Installable MCP server with typed SQL tools, bounded workspace imports and
Installation
Rust 1.88 or newer is required for a Cargo install.
cargo install basalt-db --lockedThe published package is named basalt-db; the installed command remains basalt. To install the current checkout instead, use cargo install --path . --locked.
Tagged releases include checksummed installers and prebuilt binaries for Linux, macOS, and Windows. See GitHub Releases for the current no-toolchain install. The latest tagged release is verified from its published installer and its checksums:
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/yoshiii-xyz/basalt/releases/latest/download/basalt-db-installer.sh | shTo run directly from a checkout:
cargo run --release -- app.basaltQuick start
Open a database and run SQL interactively:
$ basalt app.basalt
basalt> CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT NOT NULL);
basalt> INSERT INTO users VALUES (1, 'Ada');
basalt> SELECT * FROM users;
id | name
---+-----
1 | Ada
1 row(s)For a one-shot command:
basalt --json --command "SELECT * FROM users ORDER BY id;" app.basaltUse Database::in_memory() for an ephemeral database. Durable writes are appended to the WAL immediately; call checkpoint() to fold the current state into the snapshot and clear old WAL frames. A durable path is owned by one process at a time; cloned Database handles share that owner safely across threads, while a second process receives an "already open" error.
Workspaces
Use a workspace when an agent or script needs a disposable, local relational area for CSV, JSON, logs, issue exports, or fixtures:
basalt init .basalt-workspace
basalt workspace import --table issues .basalt-workspace issues.csv
basalt workspace inspect --json .basalt-workspace
basalt workspace query --json .basalt-workspace "SELECT * FROM issues ORDER BY id"
basalt workspace export .basalt-workspace issues issues.jsonlShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Basalt: common questions
- Is Basalt MCP server safe?
- Mostly: it is graded B (83/100). Read the Basalt safety report
- Does Basalt need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Basalt maintained?
- The last commit was 21 days ago (2026-10-15). The latest release is v0.1.6.
- What can I use instead of Basalt?
- Servers from other publishers that do the same job: Showboard MCP server, Mako MCP server and DBHub MCP server.
- How does Basalt compare with other Databases MCP servers?
- safety score 83/100 (higher than 60% of 802 Databases servers); github stars 1 (more than 45% of 602 Databases servers). Full comparison.
Alternatives to Basalt
Same job from other publishers: the closest match first, then the best rated.
ShowboardYour coding agent answers with dashboards: charts and tables from read-only SQL, Excel and CSV.not reviewedGrowingB- MakoExplore your databases, validate SQL, and build & publish data apps in your Mako workspace.not reviewedGrowingA
- DBHubToken-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLitenot reviewedWidely usedA
- MotherduckSQL analytics and data engineering for AI Assistants and IDEsnot reviewedEstablishedA
- KeboolaConnect your AI assistants to Keboola and expose your data, transformations, SQL queries, ...not reviewedEstablishedA