Health Connect data for your agent

HC Sync exposes read-only Health Connect data through MCP at https://hcsync.dev/mcp. Connect with your project read key after an Android app uploads permitted records, or load sample data first. Records return at most 200 rows, daily summaries cover 1–90 days, and authenticated MCP requests are limited to 120 per hour.

Last updated: 2026-11-04. Source for the 2026 service details: HC Sync page details.

Free for 5 synced users. Starter: $29/month for 100. Every plan includes MCP, REST and signed webhooks. Android app permissions are required to sync real device data.

How do agent builders connect through MCP?

Connect a Streamable HTTP client to https://hcsync.dev/mcp with Authorization: Bearer $READ_KEY. Create a free project, save the read key, and load sample data in the dashboard. No email required.

Read-only tools: list_users, get_daily_summary(user_id, days), get_records(user_id, type, from, to). These share REST validation, project isolation and data limits. Records return at most 200 rows; daily summaries cover 1–90 days. Use REST pagination for larger exports. Legacy health_* names remain accepted aliases.

curl https://hcsync.dev/mcp -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer $READ_KEY' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_daily_summary","arguments":{"user_id":"sample_user","days":7}}}'

Supports initialize, ping, tools/list and tools/call. JSON responses, no persistent sessions; notifications return 202. The existing IP limiter allows 120 authenticated MCP requests per hour and returns 429 with Retry-After. User device tokens cannot read. Keep health data and read keys private; configure your client’s authorization header instead of putting keys in prompts. MCP setup guide.

How do you configure an MCP client?

{
  "mcpServers": {
    "hcsync": {
      "type": "http",
      "url": "https://hcsync.dev/mcp",
      "headers": { "Authorization": "Bearer $READ_KEY" }
    }
  }
}

Configuration syntax varies by client. Use its remote Streamable HTTP transport and custom headers. No SDK installation is required for the agent. Registry metadata lives in server.json in the repository; listing does not imply registry approval.

What else should you know?

Which tools are available?

Read-only tools: list_users, get_daily_summary(user_id, days), get_records(user_id, type, from, to).

How many records can a tool return?

Records return at most 200 rows; daily summaries cover 1–90 days.

Can device tokens read through MCP?

User device tokens cannot read.