Skip to content

Commit 8411150

Browse files
committed
Update dependencies and enhance MySQL support
- Add `mysql2` as a dependency for improved MySQL support. - Update README and documentation to reflect new MySQL execution capabilities. - Refactor DBeaver client to handle MySQL queries natively, including SSL configuration. - Introduce workspace path configuration for better user experience. - Clean up unused dependencies and improve error handling in query execution.
1 parent 5284958 commit 8411150

8 files changed

Lines changed: 320 additions & 358 deletions

File tree

README.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,7 @@ A production-ready Model Context Protocol (MCP) server that seamlessly integrate
3333
- **Schema Management**: Complete DDL operations (CREATE, ALTER, DROP)
3434
- **Data Export**: CSV, JSON, XML, Excel export formats
3535
- **Performance Monitoring**: Query execution time tracking
36+
- **Native Execution**: Direct query support for SQLite, PostgreSQL, and MySQL/MySQL8
3637

3738
### 🧠 AI-Powered Intelligence
3839
- **Business Insights**: Track and store analysis insights with tagging
@@ -92,6 +93,7 @@ The server will automatically detect your DBeaver version and use the appropriat
9293
- Node.js 18+
9394
- DBeaver installed and configured with at least one connection
9495
- Claude Desktop, Cursor, or another MCP-compatible client
96+
- For MySQL (including MySQL 8) and most other databases, query execution uses the DBeaver executable in headless mode (set `DBEAVER_PATH` if auto-detection fails)
9597

9698
## 🛠️ Installation
9799

@@ -133,6 +135,7 @@ npm link # Makes the command available globally
133135

134136
### Environment Variables
135137
- `DBEAVER_PATH`: Path to DBeaver executable (auto-detected if not set)
138+
- `DBEAVER_WORKSPACE`: Path to DBeaver workspace directory (defaults to the standard OS location, e.g. `~/Library/DBeaverData/workspace6` on macOS)
136139
- `DBEAVER_TIMEOUT`: Query timeout in milliseconds (default: 30000)
137140
- `DBEAVER_DEBUG`: Enable debug logging (true/false)
138141

@@ -305,4 +308,4 @@ MIT License - see LICENSE file for details
305308
- DBeaver for the amazing database tool
306309
- The open source community for inspiration and feedback
307310

308-
> **Note**: This project is not officially affiliated with DBeaver or Anthropic. It's designed for real-world production use with AI assistants.
311+
> **Note**: This project is not officially affiliated with DBeaver or Anthropic. It's designed for real-world production use with AI assistants.

docs-site/docs/getting-started/configuration.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,7 @@ To use DBeaver MCP Server with Claude Desktop, add the following to your configu
4343

4444
### Core Variables
4545
- `DBEAVER_PATH`: Set a custom path to the DBeaver executable if not auto-detected
46+
- `DBEAVER_WORKSPACE`: Set a custom path to your DBeaver workspace (useful for non-default workspaces and DBeaver CLI execution)
4647
- `DBEAVER_TIMEOUT`: Set the query timeout in milliseconds (default: 30000)
4748
- `DBEAVER_DEBUG`: Set to `true` to enable debug logging
4849

docs-site/docs/guides/available-tools.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,7 @@ The DBeaver MCP Server provides 14 powerful tools organized into four categories
3838
### `execute_query`
3939
**Description**: Execute SELECT queries (read-only)
4040
**Safety Level**: ✅ Safe
41+
**Notes**: Queries are executed natively for SQLite, PostgreSQL, and MySQL/MySQL8. Other drivers may fall back to DBeaver headless mode (set `DBEAVER_PATH` if needed).
4142
**Parameters**:
4243
- `connectionId` (required): The ID or name of the DBeaver connection
4344
- `query` (required): The SQL query to execute (SELECT statements only)
@@ -130,4 +131,4 @@ The DBeaver MCP Server provides 14 powerful tools organized into four categories
130131
- **⚠️ Schema changes**: Operations that modify database structure
131132
- **❌ Destructive**: Operations that permanently remove data or objects
132133

133-
All destructive operations require explicit confirmation to prevent accidental data loss.
134+
All destructive operations require explicit confirmation to prevent accidental data loss.

0 commit comments

Comments
 (0)