Universal database MCP server — native drivers for PostgreSQL, MySQL, SQLite, SQL Server with CLI fallback, reading connections from your local DB
Universal database MCP server — native drivers for PostgreSQL, MySQL, SQLite, SQL Server with CLI fallback, reading connections from your local DB client workspace. Exposed over MCP by the dbeaver mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Universal database MCP server — give AI assistants read/write access to your databases using connections already saved in your local DB client workspace (DBeaver-compatible).
Everything the assistant can do here goes through one of these:
Cursor — The Cursor tool exposed by this serverTransactions — The Transactions tool exposed by this serverOther — The Other tool exposed by this serverYou will need 4 environment variables: OMNISQL_READ_ONLY, OMNISQL_ALLOWED_CONNECTIONS, OMNISQL_DISABLED_TOOLS, OMNISQL_CLI_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
The server ships on npm as omnisql-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Dbeaver's toolset — Cursor, Transactions, Other — is a fair guide to whether it matches your workflow. It is maintained by srthkdev; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Cursor | The Cursor tool exposed by this server. |
| Transactions | The Transactions tool exposed by this server. |
| Other | The Other tool exposed by this server. |
### Disable Specific Tools
```json
{
"mcpServers": {
"omnisql": {
"command": "omnisql-mcp",
"env": {
"OMNISQL_DISABLED_TOOLS": "drop_table,alter_table,write_query"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OMNISQL_READ_ONLY | Configuration value read at startup. | Optional |
| OMNISQL_ALLOWED_CONNECTIONS | Configuration value read at startup. | Optional |
| OMNISQL_DISABLED_TOOLS | Configuration value read at startup. | Optional |
| OMNISQL_CLI_PATH | Filesystem location the server is allowed to use. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.