Skip to main content
Glama
Huawei DCS MCP
by key-well

Related Servers

Alternatives to Huawei DCS MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      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.
      4
      83 PyPI
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI to safely view and operate Redis databases with read-only mode by default and support for key operations.
      11
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables clients to inspect and operate many Redis deployments at once — standalone, Redis Cluster, or Sentinel-managed — through a single endpoint, with 54 tools grouped into core, data, JSON, search, pub/sub, and docs toolsets. It supports read-only and destructive-tool switches, per-cluster isolation, secret-backed passwords, bounded 15-second calls, and Streamable HTTP or stdio transport.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables exploring and diagnosing a Redis instance from MCP clients with read-only safety, using SCAN instead of KEYS for safe key enumeration.
      7
      877 npm
      2
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Read-only Redis MCP server with a configurable command allowlist for safe production diagnostics, enabling exact read-only subcommands like CLIENT LIST and SLOWLOG GET.
      5
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables safe, read-only interaction with Redis databases via cursor-based tools for retrieving keys, hashes, lists, sets, and sorted sets, backed by ACL DRYRUN-verified privilege checks.
      13
      MIT

    TDQS

    C2.9/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools target clearly distinct resources or actions: instance listing vs. detail, config parameters vs. config history, and diagnosis vs. hotkey/bigkey analysis are separated. A few pairs are close enough to require care, such as ShowNodesInformation vs. BatchShowNodesInformation, ListMonitoredObjects vs. ListMonitoredObjectsOfInstance, and ListConfigurations vs. ListConfigHistories, but the descriptions distinguish them.

    Naming Consistency5/5

    The names follow a consistent PascalCase verb-noun convention throughout, using List/Show/BatchShow prefixes with descriptive resource nouns. The List vs. Show distinction is applied consistently across collections and individual resources.

    Tool Count2/5

    At 28 tools, the surface is heavy for a server whose tools are all read-only query operations. Many tools form narrow pairs around diagnostics, hotkeys, bigkeys, nodes, and config history, which could likely be consolidated.

    Completeness2/5

    The server covers a broad read-only observability surface, but it has no create, update, delete, restart, backup, scaling, or whitelist modification operations. For a DCS instance management domain, this is a significant lifecycle gap that would block common agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues