Skip to main content
Glama
cocaxcode

@cocaxcode/database-mcp

by cocaxcode

Related Servers

Alternatives to @cocaxcode/database-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      An 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.
      10
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A comprehensive PostgreSQL MCP server providing 27 tools for database management and administration, including connection management, query execution, schema introspection, CRUD operations, and server monitoring.
      27
      38
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      10
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A 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
      -
    • A
      license
      A
      quality
      D
      maintenance
      A 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.
      5
      2
      MIT

    TDQS

    A3.5/5.0

    Scored across 34 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.