Labsco
MCP SERVER

DBeaver MCP Server

by srthkdev

Query and edit your databases through the connections already saved in DBeaver — no re-entering credentials — with transactions, schema tools and export.

Relational SQL DatabasesVerified
Summary
Your DBeaver connections, without re-entering a single password.

Reusing the workspace's saved connections is the whole convenience: the databases you already set up in DBeaver are immediately reachable, so there is no second credential store to manage. The read/write split and the connection whitelist give you a real safety boundary — execute_query is read-only, write_query is where mutations live, and OMNISQL_ALLOWED_CONNECTIONS lets you decide which databases an assistant can touch at all.

What it is

A universal database server (OmniSQL) that reuses the connections already configured in your local DBeaver-compatible workspace: 21 tools for querying, writing, schema management, transactions and export across PostgreSQL, MySQL/MariaDB, SQL Server and SQLite natively, with Postgres-compatible engines routed automatically.

What you get
  • Connections come from DBeaver: list_connections shows what is configured, get_connection_info details one, and test_connection checks it — no duplicate credential setup
  • Reads and writes kept separate: execute_query runs read-only SQL, and write_query handles INSERT, UPDATE and DELETE
  • Schema management: create_table, alter_table (add columns, rename), drop_table with a safety confirmation, get_table_schema and list_tables
  • Transactions handled explicitly — begin_transaction, execute_in_transaction, commit_transaction and rollback_transaction
  • explain_query returns the execution plan, compare_schemas diffs two connections, get_database_stats and get_pool_stats report on the database and the connection pool
  • export_data writes query results to CSV, JSON and other formats
  • append_insight and list_insights keep a memo of business insights and analysis notes alongside the data
Requirements

A local DBeaver-compatible DB client with at least one configured connection — the server reads those. Node.js 18 or later, installed with npm install -g omnisql-mcp. OMNISQL_PROJECT names the workspace folder if it is not the default General, OMNISQL_ALLOWED_CONNECTIONS whitelists which connections are reachable, and OMNISQL_CLI_PATH points at an external CLI for databases without a native driver.

Setup effort

One command — npm install -g omnisql-mcp