Loving the Index so far! (especially the webhook + MCP support!)
One thing that came up in the original AMA was interest in on-device or local MCP support. Right now, any MCP/agent integration has to round-trip through Pebble’s cloud infrastructure even when the ring, phone, and target server are all on the same LAN/tailnet — which adds latency and an unnecessary cloud dependency for people running fully local smart-home/agent setups.
Is local/LAN-scoped MCP (ring or phone talking directly to a local server, no cloud hop) potentially on the roadmap? A phone-side option to point MCP traffic at a local network address instead of the cloud relay would be huge for anyone running self-hosted agents (Home Assistant, local LLMs, etc.) who wants lower latency and to keep voice-command traffic entirely on their own network.
Happy to help test if this is being considered — currently piecing together a similar result myself via a self-hosted webhook relay, but native local MCP would remove a layer entirely. Thanks again for all you do!!!