MCEC

The Model Context Environment Controller is eyes, hands, and a safe front door for agents on Windows; and the same battle-tested remote control for smart-home systems.

By Tigger Kindel
@ckindel on Twitter

MCEC

MCEC

MCEC (Model Context Environment Controller) is eyes, hands, and a safe front door for agents on Windows — and the same battle-tested remote control for smart-home systems.

In its long-standing role, MCEC provides robust control of Windows PCs for smart home systems. It runs in the background listening on the network (or serial port) for commands. It then translates those commands into actions such as keystrokes, text input, and the starting of programs. Any remote control, home control system, or application that can send text strings via TCP/IP or a serial port can use MCEC to control a Windows PC.

Almost any action a user can perform on Windows can be invoked remotely from another device on the network. This includes key presses (e.g. Alt-Tab or Win-S), mouse movements, and Window management actions (e.g. maximize window or set a window to the foreground)

MCEC works great with any remote control system that supports TCP/IP or RS-232 connections. Examples include Control4, iRule, Crestron, and Premise Home Control

New in 3.0, MCEC is also an agent-automation server: it can see the screen (capture a screenshot), query the UI Automation tree, find and wait for elements, and drive native Windows apps — exposed to AI agents and scripts over the Model Context Protocol (MCP) (stdio: mcec.exe --mcp) or a localhost HTTP floor. All of these agent capabilities are opt-in and disabled by default; everything below remains unchanged. See the Agent Server user guide and AGENTS.md (agent guidance + dogfood recipe).

Full MCEC Documentation

Download & Install

Download and Install the Latest Version

Version History