Skip to content

Multi-Database Configuration Support#31

Open
noxymon-mekari wants to merge 2 commits intoexecuteautomation:mainfrom
noxymon-mekari:feature/multi-database-config
Open

Multi-Database Configuration Support#31
noxymon-mekari wants to merge 2 commits intoexecuteautomation:mainfrom
noxymon-mekari:feature/multi-database-config

Conversation

@noxymon-mekari
Copy link

@noxymon-mekari noxymon-mekari commented Mar 17, 2026

This fix #32

noxymon and others added 2 commits March 17, 2026 03:38
Allow a single MCP server instance to connect to multiple databases
simultaneously via a JSON config file (--config flag), enabling
companies with multiple microservices to use one server for all DBs.

Key changes:
- New config loader with validation (src/config.ts)
- Database registry replacing singleton adapter (src/db/index.ts)
- New list_databases tool and database parameter on all DB tools
- Multi-DB resource listing with db://{name}/{table}/schema URIs
- Insights converted to in-memory storage for DB-agnostic operation
- Full backward compatibility with single-database CLI mode

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
--config now auto-detects JSON strings vs file paths (starts with '{').
Added --config-env <VAR_NAME> to read config from an environment
variable, ideal for Kubernetes Secrets where the JSON is injected
as an env var rather than mounted as a file.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@noxymon-mekari noxymon-mekari marked this pull request as ready for review March 17, 2026 01:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Multi-Database Configuration Support

2 participants