uecs-ccm-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@uecs-ccm-mcp show me the current greenhouse sensor readings"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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-mcpRun as MCP Server
uecs-ccm-mcpClaude Desktop / Claude Code
Add to your MCP config:
{
"mcpServers": {
"greenhouse": {
"command": "uecs-ccm-mcp"
}
}
}MCP Tools
Tool | Description |
| Indoor sensors (temp, humidity, CO2, soil temp, etc.) |
| Actuator states (irrigation, ventilation, curtain) |
| Control actuators with safety guardrails |
| Outdoor weather station data |
| 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 toolsget_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
Scored across 5 tools
Each tool serves a distinct purpose: reading sensor data, weather, actuator status, listing network nodes, and controlling actuators. No overlap in functionality.
All tool names follow a consistent verb_noun pattern with snake_case (get_, list_, set_), making them predictable and easy to understand.
Five tools is well-scoped for greenhouse monitoring and control, covering essential operations without unnecessary duplication or gaps.
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
Real-time planetary signal engine and Model Context Protocol (MCP) server for autonomous AI agents.
Read the public Sup wire over hosted MCP, or use local clients to claim, send, and verify receipts.
Zero-auth Notary & AST: RM(1,3), RFC 6962, W3C VC 2.0, ROS 2, 3-Level Mind & A2A-MCP Bridge.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables discovery and control of Switcher KIS devices locally via MCP, including turning on/off and retrieving device state without cloud dependency.1-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to manage ESPHome devices via the 2026.6+ dashboard WebSocket protocol, including listing, configuring, validating, and flashing firmware.37MIT
- FlicenseNot gradedqualityDmaintenanceLocal MCP server for reading temperature/humidity sensors from Tuya/SmartLife devices, exposing tools to list devices, get capabilities, and read sensor data.-
- AlicenseAqualityCmaintenanceEnables 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.8MIT