yoyo-mcp · IoT device
A prospective IoT device client — the same device role as the web and mobile apps, just running on constrained hardware (an ESP32-class board, a smart bulb, a sensor hub).
What it would do
- Dial out over WSS to
/ws?deviceKey=…— the device only ever connects out. - Answer the same two MCP tools —
list_messages/add_message— against its own local state. - Keep that state on the device — nothing syncs server-side, exactly like the other clients.
It plugs into the same loop as everything else: an AI reaches its local state through the
yoyo gateway, and it can poke /agent to talk back. No new wire contract.
The live browser device runs the identical behaviour today: