RAPT.io MCP Server
Related Servers
Alternatives to RAPT.io MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAccess Home Assistant data and control devices (lights, switches, thermostats, etc).6 npm576Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables control and monitoring of Tesla vehicles through the Tessie API, providing access to vehicle state (battery, location, climate) and commands (lock/unlock, climate control, navigation) with support for both local and Cloudflare Worker deployment.11-
- FlicenseNot gradedqualityDmaintenanceEnables control and monitoring of Tesla vehicles via the Tessie API, providing state and command tools for climate, locks, charging, and navigation.-
- AlicenseAqualityDmaintenanceEnables control and monitoring of Plugwise smart home devices including thermostats, switches, and energy meters with automatic network discovery. Supports temperature control, energy monitoring, and multi-hub management through natural language commands.1617 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables control and monitoring of Home Assistant smart home devices through MCP protocol. Automatically manages authentication tokens and provides simplified tools for device discovery, switch control, and light brightness adjustment.MIT
- FlicenseNot gradedqualityDmaintenanceEnables control of Yeelight smart lights over local LAN, supporting on/off, brightness, color, temperature, and auto discovery.-
TDQS
Scored across 23 tools
Most tools target distinct resources, but get_bonded_device_telemetry overlaps with resource-specific telemetry endpoints, and get_bonded_device vs get_fermentation_chamber could confuse agents unfamiliar with the domain. Descriptions mostly clarify these boundaries.
All tools follow a consistent snake_case verb_noun pattern: get_* for reads, set_* for writes, and plural forms for list operations. This makes the API highly predictable and easy to navigate.
With 23 tools, the server is slightly heavy, but the count is justified by the breadth of resources (devices, chambers, hydrometers, profiles) and the granular control offered for fermentation chambers. No redundant tools exist.
The server covers monitoring and direct control well, but lacks profile management (create/update/delete) and the ability to assign or start a profile on a chamber. These are notable gaps for a fermentation control system, though core read/control workflows are present.