@cocaxcode/database-mcp
Related Servers
Alternatives to @cocaxcode/database-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for multiple databases (PostgreSQL, MySQL, MariaDB, SQLite, MongoDB, Redis) with tools for schema inspection, querying, performance diagnostics, and safe write operations, featuring access modes, PII masking, and audit logging.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn extensible MCP server for database operations that supports PostgreSQL for managing schemas, tables, data, and user permissions. It features automatic migration recording for DDL changes and integrates with various AI-powered editors like Cursor, Zed, and Claude Code.102MIT
- AlicenseAqualityCmaintenanceA comprehensive PostgreSQL MCP server providing 27 tools for database management and administration, including connection management, query execution, schema introspection, CRUD operations, and server monitoring.2738AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceA modular MCP server that enables interaction with multiple database types including PostgreSQL, MySQL, SQLite, Redis, MongoDB, and LDAP. It provides tools for executing queries, managing SQL commands, and exploring database schemas with configurable read-only security.10MIT
- FlicenseNot gradedqualityDmaintenanceA secure multi-database MCP server supporting MySQL, PostgreSQL, and SQLite with read-only enforcement, SQL injection prevention, and tools for schema analysis, performance optimization, and visualization.4-
- AlicenseAqualityDmaintenanceA multi-database MCP server supporting MySQL, PostgreSQL, MongoDB, and SQLite with read-only and read-write query capabilities, schema inspection, and SSH tunneling, all without Docker.52MIT
TDQS
Scored across 34 tools
Most tools have a single clear responsibility, and the conn_* prefix cleanly separates connection management from querying, rollback, history, config, and dump operations. Some overlap remains around conn_set versus conn_set_group/conn_set_default, but descriptions are explicit enough to guide selection.
The dominant pattern is resource_action in snake_case (conn_create, conn_list, rollback_apply, config_set), which is predictable and readable. A minority of tools invert the order (execute_query, search_schema, inspect_last_query), creating a minor but noticeable inconsistency.
At 34 tools this server is heavy, exceeding the 25+ threshold where selection overhead becomes a real problem. The broad database domain justifies many operations, but several could be consolidated (e.g., conn_set variants, group/project management) to reduce cognitive load.
The tool surface covers the main database workflows: connection CRUD, grouping and scopes, query execution with rollback, history, config, schema search, and dump/restore. Minor gaps exist, such as no explicit group rename or direct project-assignment tool, but agents can work around them.