Purpose
matter-controller-mcp is an MCP (Model Context Protocol) server for Matter Controller, used to let AI assistants and AI applications discover, commission, and control Matter-compatible smart home devices. As a bridge between MCP clients and Matter devices, it provides a standardized interface for device control and monitoring.
Main Capabilities
- Device management: commission and decommission Matter devices, with support for automatic connection; can get controller status, list commissioned devices, and get detailed device information.
- Device control: control devices such as lights and switches; supports on/off/toggle, brightness/dimming (0-254), color temperature, and hue/saturation control.
- Device information: get detailed device information and capability structure.
- Attribute access: directly read and write device cluster attributes, support reading specific attributes or all attributes, and writes support batch operations.
- Transport methods: supports three transport methods: stdio, SSE, and streamable HTTP.
- Configuration: supports environment variable-based configuration options.
Supported Device Types
- Lighting: on/off lights, dimmable lights, color lights
- Switches: smart switches and outlets
- Sensors: various sensors (temperature, humidity, etc.)
- And more: any Matter-compatible device
Usage
This server can be used as an MCP server (default stdio transport), also supports streamable HTTP transport, and provides an integration method for Cursor MCP servers. The repository states that configuration via environment variables is supported; the documentation provides examples of operations such as commissioning devices and reading device information, as well as a list of available tools (such as get_controller_status, commission_device, get_commissioned_devices, decommission_device, get_device_info, control_onoff_device, control_level_device, control_color_device, read_attributes, write_attributes).
Environment and Dependencies
- TypeScript 5.6+
- Systems compatible with Matter.js
- BLE support (optional, for BLE commissioning) Development conventions include: using ES modules with the .js extension in import paths, using TypeScript strict typing, following the zod schema pattern for tool input validation, preferring async/await, using descriptive variable names, and appropriate error handling.
Applicable Scenarios
Suitable for scenarios that require AI agents to control Matter smart home devices through a unified MCP protocol, such as home automation, centralized device management and debugging, and controlling lights and switches through AI assistants.
Limitations and Notes
The materials do not provide specific pricing, cost, or platform restriction information. Troubleshooting tips include: device not found (confirm the device is in pairing mode and on the same network), connection timeout, permission errors (BLE access permissions), port conflicts (when using HTTP/SSE transport, the PORT environment variable can be changed), controller initialization failure, device commissioning failure, etc. The project uses the MIT license.
