Summary
Same questions, different databases.
The value is not any one engine but not having to change how you ask. Connect Postgres and SQL Server side by side and explore both with the same calls.
What it is
An MCP server built on the Legion Query Runner that puts several database engines behind one set of operations. The engine is named by a DB_TYPE code, schemas are discovered without mapping, and the same calls work whichever database is behind them.
What you get
- One interface across PostgreSQL, MySQL, Microsoft SQL Server, Redshift and CockroachDB
- Several databases connected at once, with the user choosing which to query
- Schema discovery with no manual configuration or mapping
- Query execution and result handling identical on every engine
- Database operations exposed as MCP resources, tools and prompts
- A FastAPI integration as an alternative to running standalone
Requirements
Connection details for each database, supplied as environment variables, command-line arguments or in the MCP settings JSON, with a DB_TYPE code naming the engine — pg, mysql, mssql, redshift or cockroach.
Setup effort
One command plus a key — pip install database-mcp, then supply credentials