Side-by-Side Model Context Protocol Comparison
Health Export MCP vs World Monitor
In-depth architectural comparison of the Health Export MCP and World Monitor MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Health Export MCP
Monitoring · Local stdio
Quality: 65/100 (Great) | Auth: No auth required
World Monitor
Monitoring · Local stdio
Quality: 55/100 (Good) | Auth: other
Verdict Summary: Choose Health Export MCP if you need specialized Monitoring tools running via a local process. Choose World Monitor if your workspace requires Monitoring integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Health Export MCP when:
- You need dedicated capabilities in the Monitoring domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- You have access to required keys:
HEALTH_DATA_DIR. - Primary tools included: get_mcp_status, list_metrics, get_health_metrics.
Choose World Monitor when:
- You need dedicated capabilities in the Monitoring domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: other (Free / Open Source).
- Primary tools included: 39 global intelligence tools, Curated global and regional news, Country Instability Index data.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Health Export MCP Tools (14)
get_mcp_status
Health 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_metrics
List every available Apple Health metric with its unit, day count, and date range. Use this to discover metric names before querying.
get_health_metrics
Get 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_trends
Compare 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.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Health Export MCP Configuration
World Monitor Configuration