Skip to main content
Glama
uecs-ccm-mcp

uecs-ccm-mcp

by yasunorioi

uecs-ccm-mcp

MCP server for UECS-CCM greenhouse monitoring and control.

Directly participates in UECS (Ubiquitous Environment Control System) CCM multicast network to read sensor data and send actuator commands — no MQTT broker required.

What is UECS-CCM?

UECS is the Japanese standard protocol for greenhouse environment control, using UDP multicast (224.0.0.1:16520) with XML payloads. CCM (Communication Control Module) packets carry sensor readings (temperature, humidity, CO2, etc.) and actuator commands (irrigation, ventilation, curtain, etc.).

Related MCP server: ESPHome MCP

Features

  • 5 MCP tools for LLM-driven greenhouse control

  • Zero-config networking: joins UDP multicast automatically

  • Safety guardrails: actuator allowlist, rate limiting, max irrigation duration

  • No MQTT dependency: talks CCM directly

  • Standalone test scripts: scp to RPi and run with zero dependencies

Quick Start

Install

pip install uecs-ccm-mcp

Run as MCP Server

uecs-ccm-mcp

Claude Desktop / Claude Code

Add to your MCP config:

{
  "mcpServers": {
    "greenhouse": {
      "command": "uecs-ccm-mcp"
    }
  }
}

MCP Tools

Tool

Description

get_sensor_data

Indoor sensors (temp, humidity, CO2, soil temp, etc.)

get_actuator_status

Actuator states (irrigation, ventilation, curtain)

set_actuator

Control actuators with safety guardrails

get_weather_summary

Outdoor weather station data

list_nodes

Active UECS nodes on the network

Field Test Scripts

Standalone scripts (Python standard library only) for testing on RPi:

# Receive CCM packets
python3 scripts/ccm_receive_test.py
python3 scripts/ccm_receive_test.py --filter InAirTemp

# Send control packets (confirm before sending)
python3 scripts/ccm_send_test.py Irri 1      # Irrigation ON
python3 scripts/ccm_send_test.py Irri 0      # Irrigation OFF
python3 scripts/ccm_send_test.py VenRfWin 50 # Roof window 50%

Supported Hardware

Tested with:

  • ArSprout greenhouse controller (sensor/actuator nodes)

  • Raspberry Pi as CCM participant

  • Any UECS-compliant node

Safety

  • Only allowlisted actuator types can be controlled

  • Minimum 1 second between commands (rate limiting)

  • Maximum 3600 second irrigation duration

  • Auto-OFF timer support

License

MIT

Available Tools

5 tools
get_actuator_statusC

Get current actuator states (irrigation, ventilation, curtain, etc.).

Args: house_id: House identifier (e.g., "h1").

Inputs: house_id. Returns: result

get_sensor_dataA

Get latest greenhouse sensor data (temperature, humidity, CO2, etc.).

Args: house_id: House identifier (e.g., "h1"). Derived from CCM room number. sensor_types: Filter by sensor types. None or ["all"] returns all sensors.

Inputs: house_id, sensor_types. Returns: result

get_weather_summaryB

Get outdoor weather station data (temperature, humidity, wind, rainfall).

Data comes from ArSprout external weather sensors (e.g., Misol WH65) via UECS-CCM multicast.

Args: house_id: House identifier (e.g., "h1").

Inputs: house_id. Returns: result

list_nodesA

List UECS nodes detected on the network.

Nodes are tracked by their source IP address and the CCM data types they broadcast.

Args: active_only: If True, only show nodes seen in the last 5 minutes.

Inputs: active_only. Returns: result

set_actuatorA

Control a greenhouse actuator via CCM packet.

SAFETY: Only allowed actuator types can be controlled. Irrigation has a maximum duration of 3600 seconds. Minimum 1 second between commands.

Args: actuator: CCM actuator type (e.g., "Irri", "VenFan", "VenRfWin", "ThCrtn"). state: True=ON/OPEN, False=OFF/CLOSE. priority: CCM priority (1=emergency, 10=normal, 30=low). duration_seconds: Auto-OFF timer in seconds. If set, actuator turns OFF automatically after this duration. house_id: House identifier (e.g., "h1").

Inputs: state (required), actuator (required), house_id, priority, +1 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to manage ESPHome devices via the 2026.6+ dashboard WebSocket protocol, including listing, configuring, validating, and flashing firmware.
      37
      MIT
    • 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.
      -
    • A
      license
      A
      quality
      C
      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