Summary
One server, and the driver decides which database it is.
Because it goes through ODBC, the same tool set covers whatever has a driver installed - the connection is a DSN, not a vendor. The two result formats matter more than they sound: JSONL when something has to parse the rows, Markdown when they are going into a report.
What it is
An ODBC server built on pyodbc, so it works against any database that has an ODBC driver. Alongside the usual schema and query tools it carries Virtuoso-specific ones: SPASQL queries and the support-AI stored procedures.
What you get
- Every schema name in the connected database
- Tables for a named schema or across all of them, plus a filter over table names by substring
- A table described in detail: column names and data types, nullability, primary and foreign keys
- Query results as JSONL when something downstream has to parse them
- Query results as a Markdown table when a person is going to read them
- A general database query tool alongside those
- SPASQL queries and Virtuoso support-AI procedures when the backend is Virtuoso
Requirements
Uv, a unixODBC runtime, and a configured ODBC DSN for the target database. The DSN name, user and password go in the environment alongside an API key the server expects.
Setup effort
Build from source — clone the repository and build it, then point your client at the binary