MCP Topology
The reverse tunnel is for tools that are only reachable from the Pi. Everything co-located with the daemon registers as a hosted HTTP MCP. Session overlays register per session; Pi-local tunnel MCP bootstrap may still be incomplete — check Progress Tracker.
home_assistant · media_audio_transcribe · media_understand · media_video_analyze · fetch_url · filesystem_local
COMSTAR attention vision runs bridge → CPAI directly, not via an AO vision MCP.
media_audio_transcribe exists but is not the COMSTAR voice STT path — that is Reach SpeechClient or env STT URL.
| MCP | Exposes |
|---|---|
client.terminal |
display, tones, mic status, sleep, volume |
client.google_workspace |
mail / calendar / Drive via off-the-shelf npm MCP |
filesystem_local |
Scoped local paths, if needed |
Tool tables: Contracts — MCP.
Too slow for the 15 s budget: web search, arxiv, long-running media analysis. Belong in batch flows (morning briefing), not conversation.
| Session | Allowed |
|---|---|
| Known userid | Voice responder MCP allowlist (may include HA, Google, terminal) |
| Guest | Restricted — no home_assistant, no Google, no client.terminal
|