BetterDB MCP
Related Servers
Alternatives to BetterDB MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceA 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.10011 npm82MIT
- AlicenseAqualityAmaintenanceMCP 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.22319 npm22MIT
- FlicenseNot gradedqualityCmaintenanceProvides 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-
- FlicenseNot gradedqualityDmaintenanceA 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.-
- FlicenseCqualityDmaintenanceA Model Context Protocol (MCP) server for Redis. Connect to any Redis instance and execute queries through AI assistants.30-
- AlicenseNot gradedqualityCmaintenanceA toolkit of 256 MCP servers for SRE incident diagnosis with Claude. One agent per tech (Postgres, Kafka, Istio, Kubernetes, Prometheus, MongoDB, Redis, Cassandra, ...) with failure modes, key metrics, and runbooks baked in. Plus telemetry MCPs (PromQL/LogQL/Elasticsearch), SSH-via-bastion executor, and 33 discovery adapters across 9 clouds. Apache 2.0, runs locally. Reproducible 5/5 scenariApache 2.0
TDQS
Scored across 60 tools
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.
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.
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.
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.