mahAnuj/mcp-multi-db
by Various
Read-only MCP server for querying PostgreSQL, MySQL, and SQLite from AI agents — multi-database, safe by default.
MCP
mahAnuj/mcp-multi-db
Added 26 June 2026
Overview
A read-only MCP server that lets AI agents query PostgreSQL, MySQL, and SQLite databases. It enforces safety by default, preventing write operations while providing structured access to multiple database types through a single interface.
Best for
Best for
Developers who need a safe, multi-database read-only bridge for AI agents
Use cases
- Let an AI agent inspect production database schemas without risk of data modification
- Query multiple database types (PostgreSQL, MySQL, SQLite) from a single MCP endpoint
- Enable read-only data retrieval for AI-powered analytics or reporting tools
Notes
A read-only MCP server that lets AI agents query PostgreSQL, MySQL, and SQLite databases. It enforces safety by default, preventing write operations while providing structured access to multiple database types through a single interface.
0 stars on GitHub. Last updated 2026-06-21. Licensed ISC.
Use cases
- Let an AI agent inspect production database schemas without risk of data modification
- Query multiple database types (PostgreSQL, MySQL, SQLite) from a single MCP endpoint
- Enable read-only data retrieval for AI-powered analytics or reporting tools
Pros
- Read-only by design, reducing risk of accidental data corruption
- Supports three major database types in one server
- Lightweight TypeScript implementation with no external dependencies beyond database drivers
Cons
- No write support limits use cases to data retrieval only
- Zero stars and no community adoption suggests early or untested code
- Requires separate database credentials and network access for each database type
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Read-only by design, reducing risk of accidental data corruption
- Supports three major database types in one server
- Lightweight TypeScript implementation with no external dependencies beyond database drivers
Cons
- No write support limits use cases to data retrieval only
- Zero stars and no community adoption suggests early or untested code
- Requires separate database credentials and network access for each database type