Skip to main content
Glama

Related Servers

Alternatives to BetterDB MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLMs to safely explore and operate Redis instances, with read-only keyspace inspection, multi-structure data access, memory and big-key analysis, slow query diagnostics, and optional opt-in write operations.
      105 PyPI
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      A universal MCP server enabling AI assistants to query and manage six database engines (Postgres, Redis, Elasticsearch, MySQL, MongoDB, LDAP) through 113+ tools with read-only safety and fault tolerance.
      100
      17 npm
      82
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for AWS infrastructure analysis. Connects to DynamoDB, Lambda, SQS, SNS, Secrets Manager, EventBridge, RDS, PostgreSQL, MongoDB, and CloudWatch — surfaces missing indexes, queue DLQs, Lambda config issues, IaC drift, and security findings for Claude Code and Cursor.
      22
      373 npm
      22
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides real-time monitoring of AI agents, context, usage limits, workflows, files, Git, tests, builds, errors, secrets, and model-economy advice for tools like Claude Code, Codex, and Cursor, with 30 MCP tools for comprehensive observability.
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server ecosystem providing Claude AI with 150+ specialized tools across enhanced memory, data analytics, security, design, and infrastructure domains with PostgreSQL, Redis, Qdrant, and Docker orchestration.
      -
    • F
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for Redis. Connect to any Redis instance and execute queries through AI assistants.
      30
      -

    TDQS

    A3.5/5.0

    Scored across 60 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes with detailed descriptions, but the large number (60) creates potential for confusion between closely related tools like get_latency vs get_latency_history, though descriptions clarify differences.

    Naming Consistency4/5

    Tool names follow a consistent snake_case pattern with domain-specific prefixes (memory_, cache_, get_, etc.), but the mix of verb-first (get_, memory_, cache_) and noun-first (select_instance) is not perfectly uniform across all tools.

    Tool Count2/5

    With 60 tools, the count is far above the typical 3-15 range and exceeds the 50+ threshold deemed 'extreme mismatch' in the calibration guidelines, making the surface overly large for an MCP server.

    Completeness5/5

    The toolset covers an extensive range of Valkey/Redis management, monitoring, caching, memory stores, AI traces, and proposals, leaving no obvious gaps for its intended administrative domain.

    Maintenance

    ActivityNo data
    ResponsivenessSlow