amaran-mcp
Related Servers
Alternatives to amaran-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables control of Apple Music on macOS, including playback, track info, volume, and more.12 npmMIT
- AlicenseAqualityDmaintenanceEnables discovery and control of Philips Hue lighting devices via a local bridge using the CLIP v2 API, without any cloud dependency.10MIT
- AlicenseAqualityDmaintenanceEnables control of Philips Hue lights via Bluetooth LE directly from Claude, without requiring a Hue Bridge or internet connection.81MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI-driven control of Art-Net/sACN DMX lighting, including scenes, effects, groups, safety rules, MIDI/OSC, and Ableton Live integration through a unified command layer.MIT
- AlicenseNot gradedqualityDmaintenanceEnables users to control Govee LED devices using the Govee API, with features for turning devices on/off, setting colors, and adjusting brightness through a CLI or MCP clients.6MIT
- FlicenseNot gradedqualityCmaintenanceEnables local Mac agents to monitor and control Bambu Lab 3D printers via MCP tools, including status checks, camera snapshots, and print job management.-
TDQS
Scored across 12 tools
Each tool has a distinct verb targeting a different aspect of the lamp's state (power, brightness, white, colour, effect, scene, music mode), and descriptions explicitly clarify boundaries, e.g. set_brightness noting it only adjusts brightness while preserving the current mode. The only mild conceptual overlap, start_music_mode vs set_effect, is resolved by describing music mode as a separate behaviour. An agent can pick the right tool from names alone.
All twelve tools follow a strict snake_case verb_noun pattern (get_light, set_power, stop_effect, save_scene, start_music_mode), with natural mirrored pairs like start_music_mode/stop_music_mode and save_scene/recall_scene. No mixed casing or inconsistent verb styles.
Twelve tools is well within the ideal 3-15 range for a single-device lighting controller. Every tool maps to a real capability (state read, each light attribute, effects, scenes, music mode) without redundant entries.
The surface covers the full lifecycle for light control: read state, set power/brightness/colour/white, start and stop effects, save and recall scenes, and music mode. The main gap is scene management beyond save/recall — there is no delete_scene or rename, so saved scenes can only be overwritten, not removed.