Both Apple Health exporters now ship an MCP server. That was the easy half of the problem.
The half that decides your setup is transport. Health Auto Export runs its MCP server on the iPhone, reachable at http://{LAN_IP}:9000/mcp over your local network, with Premium access as a prerequisite and Node 18+ on the client machine. That is a clean design when your agent lives on the same Wi-Fi as your phone.
MetricBridge ships its MCP server as a file you run on your computer. It reads the export you sync to iCloud Drive, a local folder, your LAN or a webhook. The server has zero runtime dependencies, makes no network calls, and exposes 16 read-only tools, two event tools and 22 prompts. Your agent can run on a laptop, a home server, a container or a hosted runner, and the phone can be in another room.
So the question moved. It is no longer "does this app have an MCP server" but "where does it run, and what has to be switched on for my agent to reach it". If your agent and your phone share a network, the on-phone server is the shortest path. If your agent runs anywhere else, the export-file server is the one that survives the phone being put down.
The full comparison, including destinations and formats, is here: https://www.healthexport.dev/blog/health-auto-export-vs-metricbridge?utm_source=devto&utm_medium=social&utm_campaign=agentic_upgrade&utm_content=health-auto-export-vs-metricbridge
Top comments (0)