Every other way of giving an assistant your health or notification history involves a copy of it somewhere else. Here the relay is deliberately blind — it wakes the device and joins two encrypted streams — and the session is ephemeral. The trade is that your phone has to be reachable and awake enough to answer, and each integration is an explicit grant rather than one blanket permission.
An Android app that serves MCP from the phone itself. A relay wakes the device when a client connects and splices two TLS streams together without seeing the plaintext, so the assistant talks to your phone directly. Four integrations are enabled separately, each with its own endpoint and its own approval.
- list_record_types, query_health_data and get_health_summary over Health Connect's record types
- list_active_notifications and search_notification_history, plus get_notification_stats for counts, top apps and the busiest hour
- perform_notification_action and dismiss_notification — acting on a notification, not just reading it
- launch_app, open_link, copy_to_clipboard and send_notification for making something happen on the device
- list_installed_apps, create_notification_channel, list_notification_channels and delete_notification_channel
- get_dnd_state and set_dnd_state
- get_usage_summary, get_app_usage, get_usage_events and compare_usage for screen time, including two periods compared with the biggest changes first
- An audit tab logging every tool call, and an approval prompt on the phone the first time a client connects
An Android phone and the app, sideloaded from the releases page — two builds ship, one without Firebase. Each integration is enabled by hand and asks for its own Android permissions, then gives you a URL to paste into your client. The first connection triggers an approval you tap on the phone. Nothing syncs to a server: the relay wakes the device and passes encrypted traffic through, and the session ends when the client disconnects.