F
licenseNot graded
qualityD
maintenanceEnables natural language command and control of remote systems across multiple platforms through Claude AI using the Model Context Protocol.
8
-
CrestronMCP client
Related Servers
Alternatives to CrestronMCP client
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables natural language control of ESP8266 and Raspberry Pi IoT devices via Claude Desktop using the MCP protocol.MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude AI to execute commands across multiple remote servers via SSH, with TOTP 2FA authentication and 29 built-in MCP tools for server management.-
- FlicenseNot gradedqualityBmaintenanceEnables managing meeting room reservations through a conversational interface using Claude's language model and the MCP protocol.-
- AlicenseAqualityDmaintenanceAn MCP server that enables Claude to control SmartRent smart home devices such as locks, thermostats, light switches, and sensors through natural conversation.5MIT
- FlicenseNot gradedqualityCmaintenanceMiddleware that uses Model Context Protocol and generative AI to automatically generate native Crestron Construct interfaces (.cuig/.cuib), enabling natural language creation of AV control UI components.-
TDQS
A3.9/5.0
Scored across 14 tools
Disambiguation5/5
Each tool targets a distinct operation: licensing (activate/check/start trial), device control (control/pulse/ramp/cancel), batch control (set), querying (query, get_room_status, list, discover), and system info (get time). No two tools have overlapping purposes; agents can easily distinguish when to use which.
Naming Consistency4/5
Most tools follow a verb_crestron_device or verb_crestron_system pattern, with consistent snake_case. The only minor deviation is 'get_room_status' instead of 'get_crestron_room_status', but it's a single outlier and still clear.
Tool Count5/5
14 tools are well-scoped for a Crestron control system: licensing (3 tools), device control (5: control, pulse, ramp, cancel, set), information (5: discover, list rooms, list devices, get room status, query device), and utility (1: get time). This covers all core operations without bloat.
Completeness4/5
The set covers the full lifecycle: discover, list, query, control (single & batch), ramp, pulse, cancel, and licensing management. Minor gaps like a 'stop all devices' or 'reset device' are absent but not essential for typical agent workflows. Overall highly complete.
Maintenance
ActivitySlowing
ResponsivenessNo issues