Summary
One connector, and the database question stops being which client.
ODBC is already the layer that makes databases interchangeable. Putting a model behind the Driver Manager means the DSN you have configured is the one it queries — and against Virtuoso the same connection carries SPARQL and SPASQL, not only SQL.
What it is
A thin TypeScript layer over node-odbc that routes calls to your machine's ODBC Driver Manager. What it can reach is whatever your ODBC connectors can reach — the examples lean toward the Virtuoso connector, but the path is generic.
What you get
- Schemas and tables listed, table names filtered, and any table described
- Queries executed against the DSN, returned as data or as Markdown
- SPARQL queries, and SPASQL — SQL and SPARQL in one statement
- The OpenLink AI Layer reached over the same ODBC connection
Requirements
A recent Node.js, unixODBC configured with a working DSN, and the MCP SDK packages installed. The DSN name, its user, the password and ODBCINI go in a .env file beside the server; using the OpenLink AI Layer additionally takes an LLM API key.