A multi-database MCP server supporting multiple remote databases
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"multidb-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# MultiDB MCP Server MCP (Model Context Protocol) server supporting multiple remote databases. Stateless design - specify the database with each call. ## Features - 🔄 Connect to multiple databases (MySQL/PostgreSQL) simultaneously - 🎯 Stateless design - no connection state management needed - 🔍 Query, schema inspection, database management - 🛡️ Connection info managed via configuration file - ✅ User confirmation for data modification operations ## Installation ### Recommended: Using uvx ```bash uvx multidb-mcp ``` MCP configuration example: ```json { "multidb-mcp": { "type": "stdio", "command": "uvx", "args": [ "multidb_mcp" ], "env": { "DATABASE_CONFIG_PATH": "xxx/database.json", "DEFAULT_MAX_ROWS_AFFECTED": "1" } } } ``` ### Other methods **Using uv:** ```bash uv venv && source .venv/bin/activate uv pip install -e . multidb-mcp ``` **Using pip:** ```bash pip install -e . multidb-mcp ``` ## Configuration Create a `config.json` file: ```json { "databases": { "dev1": { "type": "mysql", "host": "localhost", "port": 3306, "user": "root", "password": "password", "database": "dev_db" }, "test": { "type": "postgresql", "host": "localhost", "port": 5432, "user": "postgres", "password": "password", "database": "test_db" } } } ``` Copy from `config.example.json`: ```bash cp config.example.json config.json # Edit with actual connection details ``` ### Configuration file priority 1. Command-line argument: `--config /path/to/config.json` 2. Environment variable: `DATABASE_CONFIG_PATH=/path/to/config.json` 3. Default path: `./config.json` ## Usage ### Start the server ```bash # Using default config multidb-mcp # Using custom config multidb-mcp --config /path/to/config.json # Using environment variable export DATABASE_CONFIG_PATH=/path/to/config.json && multidb-mcp # Development mode fastmcp dev multidb_mcp/server.…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.