Multi Database MCP Server

@FreePeak

リポジトリ

基本情報

カテゴリ

データベース

ライセンス

MIT

トランスポート

stdio

作者

FreePeak

Multi Database MCP Server について

A powerful multi-database server implementing the Model Context Protocol (MCP) to provide AI assistants with structured access to databases.

#mcp-server#database-mcp-server

Multi Database MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "db-mcp-server": {
      "command": "docker",
      "args": [
        "pull",
        "freepeak/db-mcp-server:latest"
      ]
    }
  }
}

Multi Database MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Multi Database MCP Server?

The Multi Database MCP Server is a server that implements the Model Context Protocol (MCP) to give AI assistants structured access to multiple databases simultaneously. Built on the FreePeak/cortex framework, it lets AI models execute SQL queries, manage transactions, explore schemas, and analyze performance across MySQL, PostgreSQL, SQLite, Oracle, and TimescaleDB through a single, unified interface.

How to use Multi Database MCP Server?

Configure database connections in a config.json file, then run the server with ./bin/server -t <transport> -c <config.json>. Use STDIO mode (-t stdio) for IDE integration (e.g., Cursor) or SSE mode (-t sse) for remote access on a specified host and port (default localhost:9092). Docker deployment and source compilation from GitHub are also supported.

Key features of Multi Database MCP Server

Simultaneous multi-database support with MySQL, PostgreSQL, SQLite, Oracle, and TimescaleDB
Dynamic, database-specific tool generation for each configured connection
Lazy loading mode to defer connections until first use
Clean Architecture with clear separation of concerns
Full compatibility with OpenAI Agents SDK
Health check with automatic connectivity validation on startup
Unified interface for queries, transactions, schema exploration, and performance analysis

Use cases of Multi Database MCP Server

AI assistants running cross-database analytics and reporting across different SQL systems
IDE integration enabling natural-language database queries via tools like Cursor
Automated schema exploration and performance tuning across development and production databases
Managing encrypted SQLite databases (SQLCipher) alongside cloud Oracle databases in one session
Time-series analysis on TimescaleDB hypertables through AI-driven workflows

よくある質問

How does this server differ from a standard database connector?

Unlike a single-database connector, the Multi Database MCP Server connects to multiple databases concurrently and automatically generates specialized MCP tools for each connection, providing a unified interface for queries, transactions, schema exploration, and performance analysis.

What are the runtime requirements?

The server is built in Go and runs as a standalone binary. It requires a valid configuration file (JSON) with database connection details. For Docker deployment, use the `freepeak/db-mcp-server:latest` image.

How is data transmitted between the AI and the database?

Data flows through the MCP protocol via either STDIO (for local IDE integration) or SSE (Server-Sent Events) mode. The server handles authentication and connection management locally based on the provided configuration file.

What transport modes are supported?

Two transport modes are supported: STDIO (`-t stdio`) for local IDE integration, and SSE (`-t sse`) for remote access with a configurable host and port (default `localhost:9092`). The client connects to the SSE endpoint at `http://<host>:<port>/sse`.

Are there any known limits?

The README recommends enabling lazy loading (`--lazy-loading` flag) for setups with 10 or more databases to defer connection establishment until first use. All other limits depend on the underlying database systems and server resources.