list_record_typesLABSCO SUMMARY
The data stays on the phone because the phone is the server.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
Follow the published steps — Install — download the APK from GitHub Releases and sideload it (enable "Install from unknown sources")
USE CASES
01
Asking about your own health trends
Query the record types you have permitted and get a summary over a period rather than a screenshot.
02
Finding a notification you swiped away
Search the history by text, app or time range instead of scrolling.
03
Dealing with a notification without picking up the phone
Invoke its action button, or dismiss it.
04
Sending yourself something to act on later
Post a notification with a tap-to-open link and its own channel.
05
Understanding where your screen time went
Read the summary and top apps, then compare this week against last.
06
Getting the phone to do something now
Launch an app, open a link, or drop text on the clipboard.
07
Being left alone
Read and set Do Not Disturb from wherever you are.
22 tools
Listed in project docs. Your client may show a different list.
query_health_dataget_health_summarylist_active_notificationssearch_notification_historyget_notification_statsperform_notification_actiondismiss_notificationlaunch_appopen_linkcopy_to_clipboardsend_notificationlist_installed_appscreate_notification_channellist_notification_channelsdelete_notification_channelget_dnd_stateset_dnd_stateget_usage_summaryget_app_usageget_usage_eventscompare_usageBEFORE YOU INSTALL
What to know first
Tools you get
22 tools named in the project's documentation.
INSTALLATION
Connect your client
Server setup
Install — download the APK from GitHub Releases and sideload it (enable "Install from unknown sources")
Onboard — open the app, tap Get Started, grant notification permissions; the app registers with the relay and provisions TLS certificates
Enable an integration — tap Add Integration, pick one (e.g. Health Connect), grant permissions, and you get a URL like https://brave-health.abc123.rousecontext.com/mcp
Connect your AI client — paste that URL into Claude (Settings -> Connectors -> Add custom connector) or any MCP client
Approve the first connection's OAuth prompt on the phone
