Skip to main content
Glama
yasunorioi

uecs-ccm-mcp

by yasunorioi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to uecs-ccm-mcp

No user-submitted related servers found.

    Related Servers

    • GrowBridge

      kirinhcl
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to control Spider Farmer GGS controllers over local Bluetooth, including environmental monitoring, telemetry history, outlet switching, light and fan adjustment, and timed pump operation with readback verification.
      MIT

    • acinfinity-mcp

      misterboe
      A
      license
      A
      quality
      B
      maintenance
      Enables natural language control of AC Infinity UIS grow controllers to read tent climate, sensor data, port settings, and automations, and to modify port modes, power levels, timers, schedules, and automation rules via MCP clients like Claude or Codex.
      18
      2
      MIT

    • Smartlife Tuya MCP Server

      bennythecoder
      F
      license
      Not graded
      quality
      D
      maintenance
      Local MCP server for reading temperature/humidity sensors from Tuya/SmartLife devices, exposing tools to list devices, get capabilities, and read sensor data.
      -

    • ESPHome MCP

      loryanstrant
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to manage ESPHome devices via the 2026.6+ dashboard WebSocket protocol, including listing, configuring, validating, and flashing firmware.
      36
      MIT

    • py-unifi-mcp

      duganth
      A
      license
      A
      quality
      B
      maintenance
      Enables local UniFi Network inspection and management through MCP, providing typed read-only inventory of sites, devices, clients, and networks, with preview-first, explicitly confirmed device rename and LED locate operations.
      8
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: reading sensor data, weather, actuator status, listing network nodes, and controlling actuators. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (get_, list_, set_), making them predictable and easy to understand.

    Tool Count5/5

    Five tools is well-scoped for greenhouse monitoring and control, covering essential operations without unnecessary duplication or gaps.

    Completeness4/5

    The set covers core CRUD-like operations (read sensor data, control actuator) but lacks historical data retrieval or detailed node diagnostics, which are minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources