
MCP Database Server
io.github.Souhar-dya由 GitHub 帳號 Souhar-dya 發布v1.3.1更新於 Oct 24, 2026
MCP server for SQLite, PostgreSQL, and MySQL with natural language to SQL and direct SQL tooling.
概覽
一個本機 MCP 伺服器,將 SQLite、PostgreSQL 與 MySQL 資料庫開放給助理,把自然語言問題轉成 SQL 並回傳結構化結果。
- 可以做什麼
- 列出所連資料庫中的資料表與欄位數,並詳細描述某張資料表的結構。取得某張資料表的樣本資料,快速查看內容。送出自然語言問題,取得產生的 SQL 查詢結果(結構化 JSON)。檢查服務健康狀態。
- 適用情境
- 適合讓助理以自然語言瀏覽與查詢關聯式資料庫而不必手寫 SQL,尤其是唯讀查詢、了解資料表結構與快速取樣資料。
- 執行需求
- 以本機 Docker 容器執行(或從原始碼以 Python 3.11+ 執行)。需要透過 DATABASE_URL 連線可存取的 SQLite、PostgreSQL 或 MySQL 資料庫,並設定 MCP_API_KEY 保護資料庫 HTTP 路由。需要能連線資料庫主機的網路。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 MCP Database Server,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
mcp-db-server
[License] [Python] [mcpindex verdict]
An MCP (Model Context Protocol) server that exposes relational databases (PostgreSQL/MySQL) to AI agents with natural language query support. Transform natural language questions into SQL queries and get structured results.
Features
- Multi-Database Support: Works with PostgreSQL and MySQL
- Natural Language to SQL: Convert plain English queries to SQL using HuggingFace transformers
- RESTful API: Clean FastAPI-based endpoints for database operations
- Safety First: Read-only operations with query validation and result limits
- Docker Ready: Complete containerization with Docker Compose
- Production Ready: Health checks, logging, and error handling
- AI Agent Friendly: Designed specifically for AI agent integration
Version 1.4.0 Changes
- Added mandatory
X-API-Keyauthentication for all database HTTP endpoints;/healthremains public for health checks. - Removed unrestricted credentialed CORS and made allowed origins explicitly configurable.
- Changed the default HTTP bind address to
127.0.0.1. - Added table-name validation against existing database tables to block SQL injection through table routes.
- Added PostgreSQL
sslmode=requirecompatibility forasyncpgconnections. - Updated Docker Compose, environment examples, and documentation for secure API-key configuration.
- Published Docker images:
souhardyak/mcp-db-server:1.4.0souhardyak/mcp-db-server:latest
- Added GitHub Container Registry publishing for:
ghcr.io/souhar-dya/mcp-db-server:1.4.0ghcr.io/souhar-dya/mcp-db-server:latest
API Endpoints
Quick Start
Option 1: Docker Compose (Recommended)
-
Clone and start the services:
-
Test the endpoints:
Option 2: Local Development
-
Prerequisites:
- Python 3.11+
- PostgreSQL or MySQL database
-
Install dependencies:
-
Set environment variables:
-
Run the server:
Sample Database
The project includes a sample database with realistic e-commerce data:
- customers: Customer information (10 sample customers)
- orders: Order records (17 sample orders)
- order_items: Individual items within orders
- order_summary: View combining order and customer data
Natural Language Query Examples
The server can understand various types of natural language queries:
Configuration
Environment Variables
Database Connection Examples
Note:
- For MySQL cloud providers, the
ssl-modeparameter in the URL is ignored by the driver, but SSL is always enabled in the MCP server for cloud connections.- For PostgreSQL, use
sslmode=requirefor cloud DBs. For MySQL, just use the standard URL; SSL is handled automatically.- If you see errors about
ssl-modeorsslmode, check your URL and ensure you are using the correct driver prefix (mysql+aiomysqlorpostgresql+asyncpg).
Cloud Database Examples
Docker Usage with Cloud DB
GitHub Container Registry is also available:
Images are published automatically when a v*.*.* tag is pushed. The workflow also creates the matching GitHub Release. To publish an existing tag such as v1.4.0, open the workflow's Run workflow action and enter 1.4.0. Set the GHCR package visibility to Public in the repository's Packages settings if unauthenticated pulls should be allowed.
Troubleshooting
- If you get
connect() got an unexpected keyword argument 'ssl-mode', ignore it: SSL is still enabled. - For network errors, check firewall and DB credentials.
- For MySQL, always use
mysql+aiomysqlin the URL for async support.
The server normalizes sslmode=require to the ssl option expected by asyncpg. A temporary PostgreSQL verification was completed successfully against a compatible cloud database using CREATE, INSERT, SELECT, UPDATE, DELETE, and DROP; no test data was retained. Never commit or share a connection URL containing a real password.
API key authentication
MCP_API_KEY is a secret that you generate and provide to the server. It protects all database HTTP endpoints through the X-API-Key request header. The /health endpoint remains public for container health checks.
Generate a strong key on Linux or macOS:
Generate one in Windows PowerShell:
Start the Docker image with the key:
Call a protected endpoint with the same key:
Keep the key in a password manager or deployment secret store. Do not commit it to Git, put it in a public image, or include it in logs.
Security Features
- Mandatory HTTP Authentication: Database API routes require
X-API-Key;/healthremains public for health checks - Secure Network Default: HTTP mode binds to
127.0.0.1unless explicitly configured otherwise - Restricted CORS: Cross-origin access is disabled unless origins are explicitly configured
- Read-Only Operations: Only SELECT queries are allowed
- Query Validation: Automatic detection and blocking of dangerous SQL operations
- Result Limiting: Maximum 50 rows per query (configurable)
- Input Sanitization: Protection against SQL injection
- Safe Defaults: Secure configuration out of the box
Architecture
Model Context Protocol (MCP) Integration
This server is designed to work seamlessly with MCP-compatible AI agents:
- Standardized Endpoints: RESTful API following MCP conventions
- Structured Responses: JSON responses optimized for AI consumption
- Error Handling: Consistent error messages and status codes
- Documentation: OpenAPI/Swagger documentation available at
/docs
Publish To VS Code MCP Store (Registry)
VS Code MCP gallery uses MCP Registry metadata. This repository now includes
server.json for registry publication.
1) Build and publish Docker image
2) Validate server metadata
server.json is configured for an OCI package and stdio transport:
name:io.github.Souhar-dya/mcp-db-serverregistryType:ociidentifier:docker.io/souhardyak/mcp-db-server:1.3.1
The Dockerfile includes registry ownership annotation:
io.modelcontextprotocol.server.name=io.github.Souhar-dya/mcp-db-server
3) Publish to MCP Registry
Install publisher and publish metadata:
After publishing, users can discover/install it from MCP-compatible clients, including VS Code MCP experiences that read from the registry.
4) Local VS Code config example
Docker Smoke Test
Use the dedicated Docker smoke test in tests/docker:
This verifies Docker daemon access, image build, container startup, and health status.
Deployment
Docker Hub
Kubernetes
Testing
Run Tests Locally
Manual Testing
Contributing
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add some amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
License
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.
📝 Changelog
v1.3.0 (2025-12-24) - Docker Path Fix
- Fixed: Resolved import path issues in Docker container causing
from db import DatabaseManagerto fail - Fixed: Changed relative paths to absolute paths in Dockerfile and docker-compose.yml healthchecks
- Improved:
mcp_server.pynow uses robust path resolution that works both locally and in Docker containers - Updated: Docker image rebuilt and pushed with all path fixes
v1.2.0 (2025-11-03) - MySQL Column Access Fix
- Fixed: Resolved
Could not locate column in row for column 'column_name'error with MySQL databases - Fixed: Changed
describe_tablemethod to use index-based row access for better SQLAlchemy compatibility - Improved: Enhanced cross-database compatibility for schema introspection
- Resolved: GitHub Issue #1
v1.1.0 (2025-09-28) - Async Bug Fix
- Fixed: Resolved
str can't be used in 'await' expressionerror in MCP server - Improved: NLP query processing now works correctly with Claude Desktop integration
- Enhanced: Added comprehensive test database setup scripts
- Updated: Docker image rebuilt with bug fixes and updated dependencies
v1.0.0 (2025-09-25) - Initial Release
- Initial: Full MCP Database Server implementation
- Added: RESTful API with FastAPI
- Added: Natural language to SQL conversion
- Added: Docker containerization and deployment
- Added: Multi-database support (PostgreSQL, MySQL, SQLite)
Acknowledgments
- FastAPI for the excellent web framework
- HuggingFace Transformers for NL to SQL capabilities
- SQLAlchemy for database abstraction
- The Model Context Protocol (MCP) community
Support
⭐ If this project helped you, please consider giving it a star!
來源:README.md,提交 069028d
工具
0版本歷史
1- v1.3.1最新Sep 16, 2026
評分
已滿足適用檢查項的 40%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。