Health Export MCP vs Withings Health Data

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

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 Withings Health Data when:

• You need dedicated capabilities in the Monitoring domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: get_hrv, get_sleep_summary, get_activity.

Feature & Specification Comparison

Specification	Health Export MCP io.github.PhilipAD Monitoring	Withings Health Data Monitoring
Summary
Category & Scope	Monitoring	Monitoring
Quality signal

Tools & Capabilities Breakdown

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).

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

{
  "mcpServers": {
    "withings-health-data": {
      "url": "https://withings-mcp.com/mcp"
    }
  }
}

Related MCP Server Comparisons