In-depth architectural comparison of the Garmin Local MCP and Withings MCP 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
Garmin Local MCP
Sports · Local stdio
Quality: 52/100 (Good) | Auth: other
Withings MCP
Sports · Local stdio
Quality: 59/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Garmin Local MCP if you need specialized Sports tools running via a local process. Choose Withings MCP if your workspace requires Sports integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Garmin Local MCP when:
You need dedicated capabilities in the Sports domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
Primary tools included: Incremental sync into raw JSON and SQLite, Offline analysis over previously synced history, Server-side trends, correlations, and personal baselines.
Local-first Garmin data warehouse: incremental sync into SQLite you own, with server-side trends, lag-aware correlations, personal baselines, and anomaly detection returned as compact tables. Analysis keeps working offline when Garmin's API breaks, and a zero-auth FIT-bundle import fills gaps with no login at all.
MCP server for the Withings Health API: OAuth, local SQLite cache, and trend analysis for body composition, sleep, activity, workouts, and ECG.
Category & Scope
Tools & Capabilities Breakdown
Garmin Local MCP Tools (6)
Incremental sync into raw JSON and SQLite
Offline analysis over previously synced history
Server-side trends, correlations, and personal baselines
Multi-metric anomaly detection
Zero-auth wellness FIT-bundle import
Compact columnar tool responses
Withings MCP Tools (8)
withings_sync
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).
Garmin Local MCP is categorized under Sports and uses a local stdio subprocess. In contrast, Withings MCP belongs to Sports using local stdio subprocess. Select Garmin Local MCP when you need capabilities focused on sports and Withings MCP when you require tools for sports.
Sync Withings health data to the local cache.
Fetches data from the Withings API and stores it in SQLite for fast
offline queries. Run this before using other withings_get_* tools.
Syncs incrementally: only fetches data newer than the last sync.
First sync fetches the specified number of days of history.
Args:
data_types: What to sync. Options: "all", "body", "sleep",
"activity", "workouts". Comma-separated for multiple,
e.g. "body,sleep". Default: "all".
days: Days of history for first sync (default: 30). Ignored
on subsequent syncs (uses last sync timestamp).
Returns summary of records synced per data type.
Not for querying data - use withings_get_body, withings_get_sleep,
withings_get_activity, or withings_get_workouts instead.
withings_get_activity
Get daily activity summaries (steps, distance, calories, active time).
Returns one entry per day from the local cache by default.
Run withings_sync first to populate the cache.
Args:
start_date: Start date as "YYYY-MM-DD", "YYYY-MM", or "30d".
Default: last 30 days.
end_date: End date as "YYYY-MM-DD". Default: today.
live: If true, fetch from Withings API instead of cache.
Returns daily activity data sorted by date, with steps, distance
in km, calories, and active minutes by intensity level.
Not for workout sessions -- use withings_get_workouts instead.
withings_get_workouts
Get workout sessions (type, duration, HR, calories).
Returns individual workout sessions from the local cache by default.
Run withings_sync first to populate the cache.
Args:
start_date: Start date as "YYYY-MM-DD", "YYYY-MM", or "90d".
Default: last 90 days.
end_date: End date as "YYYY-MM-DD". Default: today.
category: Filter by workout type, e.g. "cycling", "walk", "run".
Case-insensitive partial match.
live: If true, fetch from Withings API instead of cache.
Returns workout sessions sorted by date with type, duration,
calories, distance, and heart rate data.
Not for daily step/activity totals -- use withings_get_activity.
withings_trends
Analyse trends in cached health data.
Computes averages, min/max, and changes over time from the local
cache. Auto-syncs if the cache is stale (no sync today).
Args:
data_type: What to analyse. Options: "body", "sleep", "activity".
period: Aggregation period. Options: "weekly", "monthly",
"quarterly". Default: "monthly".
start_date: Start date as "YYYY-MM-DD" or "12m" for relative.
Default: last 12 months.
end_date: End date as "YYYY-MM-DD". Default: today.
compare: Compare two periods. Format: "last_30d vs previous_30d",
"2026-03 vs 2026-02", "2026-Q1 vs 2025-Q4".
When set, period/start_date/end_date are ignored.
Returns aggregated averages with change indicators. For body data:
weight, fat%, muscle trends. For sleep: duration, score, HR trends.
For activity: steps, distance, calorie trends.
Not for raw data -- use withings_get_body/sleep/activity instead.
withings_get_body
Get body composition measurements (weight, fat, muscle, etc.).
Returns measurements from the local cache by default. Use live=True
to fetch directly from Withings API. Run withings_sync first to
populate the cache.
Args:
start_date: Start date as "YYYY-MM-DD", "YYYY-MM", or "30d" for
relative days. Default: last 30 days.
end_date: End date as "YYYY-MM-DD". Default: today.
metrics: Comma-separated metric filter, e.g. "weight_kg,fat_pct".
Default: all available metrics. Options: weight_kg, fat_pct,
fat_mass_kg, muscle_mass_kg, hydration_kg, bone_mass_kg,
heart_rate, systolic_bp, diastolic_bp, spo2_pct.
live: If true, fetch from Withings API instead of cache.
Returns measurements sorted by date, one entry per measurement group.
Not for sleep or activity data -- use withings_get_sleep or
withings_get_activity instead.
withings_get_devices
Get connected Withings devices with battery and firmware info.
Always fetched live from the Withings API.
Returns device type, model name, battery level (high/medium/low),
and last session date for each connected device.
withings_get_heart
Get ECG recordings and atrial fibrillation detection results.
Always fetched live from the Withings API (not cached due to large
signal data). Requires a Withings device with ECG capability
(ScanWatch, BPM Core).
Args:
start_date: Start date as "YYYY-MM-DD" or "30d". Default: last 30 days.
end_date: End date as "YYYY-MM-DD". Default: today.
Returns ECG recording list with timestamps, AFib classification
(negative/positive/inconclusive), and heart rate. Does not include
raw signal waveforms.
For resting heart rate trends, use withings_get_body or
withings_get_sleep instead.
withings_get_sleep
Get sleep data (summaries or detailed phases).
Summary mode (default): nightly totals with duration, sleep score,
HR, respiratory rate, and snoring. From local cache unless live=True.
Detail mode (detail=True): minute-by-minute sleep phases (awake,
light, deep, REM) with HR and respiratory rate. Always fetched live.
Maximum 7 days per request (Withings API limit).
Args:
start_date: Start date as "YYYY-MM-DD", "YYYY-MM", or "7d".
Default: last 7 days (detail) or last 30 days (summary).
end_date: End date as "YYYY-MM-DD". Default: today.
detail: If true, return minute-by-minute sleep phases instead
of nightly summaries. Always live, max 7 days.
live: If true, fetch summaries from API instead of cache.
Ignored when detail=True (always live).
Returns nightly sleep data sorted by date.
Not for body composition -- use withings_get_body instead.