A LITTLE HELP

Keep things in sync.

Start with the last completed sync and the latest entry in Sync history. They show what finished and what needs another attempt.

The first sync is taking a while

A first backfill scans your readable Health history and uploads encrypted files. Years of heart, movement, or workout data can take considerably longer than a later sync. Keep the app open with a network connection. You can pause; reopening and resuming picks up saved work.

Some data is missing

Open Apple Health → Sharing → Apps and Services → Health MCP and review read access. Then return to Health MCP and sync. Apple intentionally does not tell apps which read permissions you denied; an empty result can also mean no data exists.

Optional groups are in Health MCP Settings. GPS routes need separate route permission. Some data types depend on your device, region, or the apps that record your health data.

Pairing does not finish

Use a fresh code from your client’s authorization page. Codes expire after ten minutes. Enter all six digits in Agents, review the client, and approve. Keep the original authorization browser open so it can finish the connection. Begin again if that browser’s session was closed or cookies were cleared.

The assistant cannot decrypt

Configure the full private key, including the final check character, in the client’s secret store as HEALTHMCP_KEY. Use the exact object path from the manifest for authentication. After rotating a key, update your client and pair it again. Never ignore an authentication or checksum error.

Background sync did not arrive

Open Health MCP. iOS may delay background work, and force-quitting the app prevents background delivery until it is opened again. Enable sync notifications in Settings for a visible prompt when a request remains stale. Push requests are limited to one per 15 minutes.

Lost key or new iPhone

Keys are specific to your iPhone and do not migrate through device backups. The V1 beta does not provide cloud account recovery. Set up a new account and rebuild from Apple Health on the new device. If you still have the old phone, delete its Health MCP account in Settings to remove its encrypted cache.

A privacy change needs another attempt

If cleanup is interrupted, sync stays paused. Reconnect to the network, unlock your iPhone, and tap Retry cleanup. The saved operation resumes even after restarting the app.

Storage limits

The beta allows up to 2 GiB and 500,000 encrypted objects per account, including uploads being processed. If you reach a limit, completed data stays available. Reduce optional data or contact support for help.

Remove data or access

Revoke individual clients in Agents. Disable optional groups in Settings to remove their encrypted copies. To remove everything, use Settings → Delete account & encrypted cache. Deleting the app alone does not delete the cloud cache.

Contact support

For support, privacy questions, or a deletion request, email support@healthmcp.cc. Include the app version and sync status, but never your private key or health measurements.

Beta feedback

If you installed through TestFlight, use TestFlight → Health MCP → Send Beta Feedback. Include the sync status, app version, and a description of the issue. Keep health values and your private key out of feedback.