Health Export MCP vs MCP Server
A side-by-side look at the Health Export MCP and MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Health Export MCP for monitoring work as a local process; choose MCP Server for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Health Export MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
HEALTH_DATA_DIR. - You want tools like
get_mcp_status, list_metrics, get_health_metrics.
Choose MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DEVHELM_API_TOKEN. - You want tools like
list_monitors, get_monitor, create_monitor.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 67/100 · Great | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | HEALTH_DATA_DIR | DEVHELM_API_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 8 | 1 |
| Directory activity | 9 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 14 | 129 |
| Full listing | View Health Export MCP | View MCP Server |
Tools & capabilities
Health Export MCP tools 14
get_mcp_statusHealth check: data source, how many metrics/workouts are available, which optional context files exist, and the most recent data date. Call this first to confirm the bridge is connected.list_metricsList every available Apple Health metric with its unit, day count, and date range. Use this to discover metric names before querying.get_health_metricsGet values for a metric (or all metrics) over an optional date range, with an aggregate (avg/sum/min/max/latest). The core data-retrieval tool. Every result carries a `coverage` block giving the metric's real firstDate/lastDate/days: check it before trusting a long window, and note that `aggregate` is always computed over the full range even when `points` are rolled up. Single-metric answers also list any logged point events inside the window as segmentBoundaries.get_trendsCompare the most recent N-day window against the prior N days for a metric: change, percent change and direction (up/down/flat). Also returns `daysAvailable` and `windowSatisfied`: if windowSatisfied is false the file does not hold enough history for the window you asked for, and the comparison is over less data than requested. Logged point events inside the compared span are listed as segmentBoundaries.compare_periodsCompare a metric between two arbitrary date periods (A vs B): each aggregate plus the change and percent change. Pass periodA/periodB explicitly, or pass anchor {eventId, days} to build both periods around a logged event (the before/after question, with the event day excluded from both sides).get_structured_exportReturn clean structured JSON for the chosen metrics/date range. Paginated: the result carries `nextCursor` when more metrics remain; pass it back as `cursor` for the next page. Prefer naming the metrics you need and a date range; calling it bare over a full history is a lot of data.get_intradayThe current hour-by-hour window from the iOS app's HOURLY automations (health-intraday.json, app 1.4+): each metric's hourly points plus its latest value. The file is REPLACED on every hourly run, so this is a live within-day view, not history; use get_health_metrics for day-level questions. Returns available:false with setup guidance when no hourly automation has delivered yet.query_health_dataNatural-language convenience: pass a question and get routed structured results. Prefer the specific tools above when you can, and call list_metrics first to see how much history exists, since this tool answers over whatever the file holds.list_eventsLogged context events from health-events.json: medication starts, habit changes, doctor visits, life events, shift blocks, episodes, travel, and any type a newer app adds. Optional {type, tag, start, end} filters; a range event matches a window it overlaps. Sorted ascending by date. Returns available:false when the file was never exported; absence means nothing was exported, not that nothing happened.get_profileThe context fields the user explicitly opted in to sharing (health-profile.json): conditions, medications, goals, allergies, notes. Returns the fields plus a presentFields list. An absent field was withheld by the user or never enabled; absence must never be read as "none".get_workoutsQuery the workouts cache with {activityType (a name like Running, or a raw HealthKit id like 37), start, end} filters and pagination ({limit} default 50 max 200, {cursor} from a previous nextCursor). Records are returned exactly as stored, including the newer optional keys (avgHeartRate, maxHeartRate, running dynamics, cycling power, intervals, hasRoute) when the app exported them; older caches simply lack those keys and nothing is fabricated. Also returns summary {count, byActivityType} over everything that matched.get_sleep_sessionsClustered sleep sessions from health-sessions.json with {start, end, day} filters. Sessions are attributed to the WAKING day, matching the daily cache's sleep_analysis, so the two surfaces never disagree; a split night appears as multiple sessions with the same day, returned as-is. Timestamps carry the local UTC offset at the time of the sample.- +2 more on the listing page
MCP Server tools 129
list_monitorsList all uptime monitors in the workspace.get_monitorGet a single monitor by ID, including its full configuration.create_monitorCreate a new uptime monitor. Required: name and type (HTTP, DNS, TCP, ICMP, HEARTBEAT, MCP_SERVER, BROWSER, MULTI_STEP_API). ``config`` is required for probe types (HTTP, DNS, TCP, ICMP, HEARTBEAT, MCP_SERVER). Browser and multi-step monitors use a type default when ``config`` is omitted. ``frequencySeconds`` is optional (10–86400). Omit it to use the plan minimum. ``managedBy`` is set automatically to ``MCP`` server-side; callers cannot override it. Use the SDK or CLI directly if you need a different attribution.update_monitorUpdate an existing monitor's configuration.delete_monitorDelete a monitor permanently.pause_monitorPause a monitor (stops checking until resumed).resume_monitorResume a paused monitor.test_monitorTrigger an ad-hoc test run for a monitor and return the result.list_monitor_resultsList recent check results for a monitor (cursor-paginated).list_monitor_versionsList version history for a monitor.list_incidentsList all incidents in the workspace.get_incidentGet a single incident by ID with full details.- +117 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Health Export MCP
{
"mcpServers": {
"io-github-philipad-health-export-mcp": {
"command": "npx",
"args": [
"-y",
"health-export-mcp"
],
"env": {
"HEALTH_DATA_DIR": "YOUR_HEALTH_DATA_DIR_HERE"
}
}
}
}
MCP Server
{
"mcpServers": {
"mcp-server-113": {
"command": "uvx",
"args": [
"devhelm-mcp-server"
],
"env": {
"DEVHELM_API_TOKEN": "YOUR_DEVHELM_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Health Export MCP is categorized under Monitoring and uses a local stdio subprocess. MCP Server belongs to Monitoring and uses a local stdio subprocess. Pick Health Export MCP for monitoring work and MCP Server for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Health Export MCP is listed as free. Auth: no auth required. MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add io-github-philipad-health-export-mcp and mcp-server-113 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Health Export MCP has a quality signal of 67/100 (Great) with 9 views, 0 installs and 8 GitHub stars. MCP Server has 57/100 (Good) with 2 views, 0 installs and 1 GitHub stars.