Multi Database MCP Server

Overview

The DB MCP Server provides a standardized way for AI models to interact with databases, enabling them to execute SQL queries, manage transactions, explore schemas, and analyze performance across different database systems at the same time. Built on mark3labs/mcp-go framework, it follows Clean Architecture principles for maintainability and testability.

Features

Simultaneous Multi-Database Support: Connect to and interact with multiple MySQL and PostgreSQL databases concurrently
Database-Specific Tool Generation: Auto-creates specialized tools for each connected database
Clean Architecture: Modular design with clear separation of concerns
Dynamic Database Tools:
- Execute SQL queries with parameters
- Run data modification statements with proper error handling
- Manage database transactions across sessions
- Explore database schemas and relationships
- Analyze query performance and receive optimization suggestions
Unified Interface: Consistent interaction patterns across different database types
Connection Management: Simple configuration for multiple database connections

Currently Supported Databases

The DB MCP Server currently provides first-class support for:

| Database | Status | Features | |----------|--------|----------| | MySQL | ✅ Full Support | Queries, Transactions, Schema Analysis, Performance Insights | | PostgreSQL | ✅ Full Support | Queries, Transactions, Schema Analysis, Performance Insights |

Roadmap

We're committed to expanding DB MCP Server to support a wide range of database systems. Here's our planned development roadmap:

Q3 2025

MongoDB - Support for document-oriented database operations, schema exploration, and query optimization
SQLite - Lightweight embedded database integration with full transaction support
MariaDB - Complete feature parity with MySQL implementation

Q4 2025

Microsoft SQL Server - Enterprise database support with specialized T-SQL capabilities
Oracle Database - Enterprise-grade integration with Oracle-specific optimizations
Redis - Key-value store operations and performance analysis

2026

Cassandra - Distributed NoSQL database support for high-scale operations
Elasticsearch - Specialized search and analytics capabilities
CockroachDB - Distributed SQL database for global-scale applications
DynamoDB - AWS-native NoSQL database integration
Neo4j - Graph database support with specialized query capabilities
ClickHouse - Analytics database support with column-oriented optimizations

Our goal is to provide a unified interface for AI assistants to work with any database while maintaining the specific features and optimizations of each database system.

Installation

Prerequisites

Go 1.18 or later
Supported databases:
- MySQL
- PostgreSQL

Quick Start

# Clone the repository
git clone https://github.com/FreePeak/db-mcp-server.git
cd db-mcp-server

# Build the server
make build

Configuration

The key advantage of DB MCP Server is the ability to connect to multiple databases simultaneously. Configure your database connections in a config.json file:

{
  "connections": [
    {
      "id": "mysql1",
      "type": "mysql",
      "host": "localhost",
      "port": 13306,
      "name": "db1",
      "user": "user1",
      "password": "password1"
    },
    {
      "id": "mysql2",
      "type": "mysql",
      "host": "localhost",
      "port": 13307,
      "name": "db3",
      "user": "user3",
      "password": "password3"
    },
    {
      "id": "postgres1",
      "type": "postgres",
      "host": "localhost",
      "port": 15432,
      "name": "db2",
      "user": "user2",
      "password": "password2"
    }
  ]
}

Each database connection has a unique ID that is used to reference it when using database tools.

Usage

The server supports two transport modes:

SSE Mode (Server-Sent Events)

# Run with default host (localhost) and port (9092)
./server -t sse -config config.json

# Specify host and port for external access
./server -t sse -host example.com -port 8080 -config config.json

STDIO Mode (for IDE integration)

# Run in STDIO mode (e.g., for Cursor integration)
<path-to-db-mcp-server>/server -t stdio -c <path-to-your-db-config>config.json

Example config for Cursor

{
    "mcpServers": {
        "stdio-db-mcp-server": {
            "command": "<path-to-dir>/db-mcp-server/server",
            "args": [
                "-t",
                "stdio",
                "-c",
                "<your-dir>/database_config.json"
            ]
        }
    }
}

For Cursor integration, you can use the provided scripts:

# Start the server in Cursor
./cursor-mcp.sh config.json

Available Tools

For each connected database, the server dynamically creates a set of database-specific tools. For example, if you have databases with IDs "mysql1", "mysql2", and "postgres1", the following tools will be available:

Query Tools

query_mysql1 - Execute SQL queries on mysql1 database
query_mysql2 - Execute SQL queries on mysql2 database
query_postgres1 - Execute SQL queries on postgres1 database

Execute Tools

execute_mysql1 - Run data modification statements on mysql1
execute_mysql2 - Run data modification statements on mysql2
execute_postgres1 - Run data modification statements on postgres1

Transaction Tools

transaction_mysql1 - Manage transactions on mysql1
transaction_mysql2 - Manage transactions on mysql2
transaction_postgres1 - Manage transactions on postgres1

Performance Tools

performance_mysql1 - Analyze query performance on mysql1
performance_mysql2 - Analyze query performance on mysql2
performance_postgres1 - Analyze query performance on postgres1

Schema Tools

schema_mysql1 - Explore database schema on mysql1
schema_mysql2 - Explore database schema on mysql2
schema_postgres1 - Explore database schema on postgres1

Global Tools

list_databases - Show all available database connections

This architecture enables AI assistants to work with multiple databases simultaneously while maintaining separation between them.

Architecture

The server follows Clean Architecture principles with these layers:

Domain Layer: Core business entities and interfaces
Repository Layer: Data access implementations
Use Case Layer: Application business logic
Delivery Layer: External interfaces (MCP tools)

License

This project is licensed under the MIT License - see the LICENSE file for details.

🤝 Contributing

Contributions are welcome! Here's how you can help:

Fork the repository
Create a feature branch: git checkout -b new-feature
Commit your changes: git commit -am 'Add new feature'
Push to the branch: git push origin new-feature
Submit a pull request

Please make sure your code follows our coding standards and includes appropriate tests.

📝 License