esp32-pet
Related Servers
Alternatives to esp32-pet
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible agents to control a desktop mascot by switching its appearance and voice, showing speech-bubble dialogue, and managing state such as affinity.12 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control a Live2D desktop pet's expressions and actions via MCP protocol.MIT
- AlicenseNot gradedqualityDmaintenanceEnables agents to control a transparent, always-on-top desktop character window over a loopback-only local HTTP API — applying expressions, motions, parameters and gaze, speaking via TTS or uploaded audio with lip-sync, capturing screenshots, and switching models, window placement and visibility. Everything stays local, so no cloud account or manual token handling is required.MIT
- AlicenseBqualityCmaintenanceEnables natural-language control of DK-META2 devices through local BLE for vibration, linear extension, and rotation. It also supports scanning, connecting, status checks, and safe stop/disconnect operations without cloud access.81MIT
- AlicenseBqualityAmaintenanceControls an OBSBOT Tiny 2 camera gimbal, zoom, and wake/sleep over UVC/USB without any vendor SDK.80106 npm2MIT
- AlicenseAqualityBmaintenanceEnables controlling a Dirtywave M8 over USB by reading its screen as text, pressing buttons, playing notes, and retrieving system information through MCP tools.7MIT
TDQS
Scored across 4 tools
Each tool targets a distinguishable action: setting a single state, playing a keyframe timeline, reading status, and speaking text. There is mild overlap since bip_set_state also controls speaking mouth animation while bip_speak synchronizes mouth/gaze/blink, so an agent might hesitate over which to use for mouth motion, but the descriptions clarify the intended split.
All four tools use a consistent snake_case pattern with the shared 'bip_' prefix and a verb-led name (set_state, play_timeline, get_status, speak). The convention is predictable and readable across the whole surface.
Four tools is on the lean side but each covers a distinct facet (state, sequence playback, status, speech) of driving a physical pet device. It is slightly thin — no separate stop/reset tool — but nothing feels redundant.
The core actions (set expression, play animation, speak, read status) are covered, but there is no way to stop or interrupt a running timeline, reset to a known idle state, or enumerate valid expressions/gazes. These gaps will force agents to improvise when recovering from an animation or discovering valid state values.