# Feature Request: LAN-only / on-device MCP (skip the cloud relay round-trip)

**URL:** <https://forum.repebble.com/t/feature-request-lan-only-on-device-mcp-skip-the-cloud-relay-round-trip/1581>\
**Category:** Pebble Index\
**Created:** [September 7, 2026, 5:27pm UTC](https://forum.repebble.com/t/feature-request-lan-only-on-device-mcp-skip-the-cloud-relay-round-trip/1581 "2026-09-07T17:27:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brad](https://avatars.discourse-cdn.com/v4/letter/b/59ef9b/32.png) [@Brad](https://forum.repebble.com/u/Brad)\
**Post date:** [September 7, 2026, 5:27pm UTC](https://forum.repebble.com/t/feature-request-lan-only-on-device-mcp-skip-the-cloud-relay-round-trip/1581/1 "2026-09-07T17:27:40Z")

</div>

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!!!

---

<div class="post-metadata">

**Author:** ![crc32](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@crc32](https://forum.repebble.com/u/crc32)\
**Post date:** [September 8, 2026, 10:26am UTC](https://forum.repebble.com/t/feature-request-lan-only-on-device-mcp-skip-the-cloud-relay-round-trip/1581/2 "2026-09-08T10:26:38Z")

</div>

Hey! A LAN MCP should already work (obviously only when you’re on said LAN, and only via the cloud agent currently) but yes, true on-device MCP is a feature we’re working on.

The local agent is a model purpose-trained to the built-in tools for reliability and efficiency purposes (it’s under 30MB!) and has extremely limited reasoning, so that’s why you can’t use other MCPs fully locally right now, but a generalised on-device model will likely be offered too at some point.