Summary
One explorer for whatever database happens to be behind the JDBC URL.
Because it goes through JDBC, the same tools cover SQLite on a laptop and Oracle in a data centre - and it will tell you which dialect it reached, which is usually what decides whether the SQL you wrote runs. The insight memo turns an exploration session into something readable afterwards.
What it is
A database explorer built on Spring AI MCP that connects over JDBC. It lists and describes tables, runs queries, reports which dialect it is talking to, and keeps a running memo of the insights found along the way.
What you get
- Table names with their type, schema and remarks
- A table described in full: columns, primary keys, foreign keys and indexes
- A SQL query executed against the connected database, with results returned
- Database information - SQL dialect, keywords, product name - so the query is written for the right dialect
- Business insights recorded into a memo resource as the analysis goes
- A data-explorer prompt that offers dashboards and then runs the queries to build the one you choose
Requirements
A JDBC-reachable database - SQLite, PostgreSQL, Oracle, H2 and MySQL are the supported variants - and a JVM to run it on, since it is a Spring AI application.
Setup effort
One command — docker pull ghcr.io/mikechao/jdbc-explorer:latest