What is the key difference between Health Export MCP and MCP Telemetry?

Health Export MCP belongs to the Monitoring category with local stdio execution, while MCP Telemetry belongs to the Monitoring category with local stdio execution.

How do I install Health Export MCP or MCP Telemetry in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Health Export MCP and MCP Telemetry free or paid?

Health Export MCP operates under a Free / Open Source model (No auth required). MCP Telemetry operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Health Export MCP lists 14 tools with 4 views and 4 GitHub stars. MCP Telemetry lists 5 tools with 2 views and 2 GitHub stars.

Can I use both Health Export MCP and MCP Telemetry together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Health Export MCP vs MCP Telemetry

In-depth architectural comparison of the Health Export MCP and MCP Telemetry 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

MCP Telemetry

Monitoring · Local stdio

Quality: 63/100 (Good) | Auth: No auth required

Verdict Summary: Choose Health Export MCP if you need specialized Monitoring tools running via a local process. Choose MCP Telemetry 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.

Explore Health Export MCP Details

Choose MCP Telemetry 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).
Primary tools included: check_deployment_status, watch_deployment, compare_deployments.

Feature & Specification Comparison

Specification	Health Export MCP io.github.PhilipAD Monitoring	MCP Telemetry arnavranjan005 Monitoring
Summary	Query 190 Apple Health metrics from any MCP agent — zero-dependency, read-only, local-first.	Socket.IO-style telemetry for MCP servers. Instrument a tool call with a few lines of mcp-telemetry-sdk, and telemetrysubscribe streams its live progress (steps, logs, cost, done) to any connected MCP client via notifications/progress — no polling, and a job started in one session can be watched from a completely different one.
Category & Scope

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

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "io-github-philipad-health-export-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "health-export-mcp"
      ],
      "env": {
        "HEALTH_DATA_DIR": "YOUR_HEALTH_DATA_DIR_HERE"
      }
    }
  }
}

MCP Telemetry Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "arnavranjan005-mcp-telemetry": {
      "command": "npx",
      "args": [
        "-y",
        "deploy-mcp"
      ]
    }
  }
}

Frequently Asked Questions

Health Export MCP is categorized under Monitoring and uses a local stdio subprocess. In contrast, MCP Telemetry belongs to Monitoring using local stdio subprocess. Select Health Export MCP when you need capabilities focused on monitoring and MCP Telemetry when you require tools for monitoring.

More alternatives to Health Export MCP More alternatives to MCP Telemetry Monitoring category hub Canonical compare URL