Wc26 MCP vs Fitbit MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Wc26 MCP vs Fitbit MCP
In-depth architectural comparison of the Wc26 MCP and Fitbit 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
Wc26 MCP
Sports · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Fitbit MCP
Sports · Local stdio
Quality: 60/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Wc26 MCP if you need specialized Sports tools running via a local process. Choose Fitbit 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 Wc26 MCP when:
You need dedicated capabilities in the Sports domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
FIFA World Cup 2026 data — 18 tools covering matches, teams, venues, city guides, fan zones, visa requirements, injuries, odds, standings, and more. Zero API keys needed.
MCP server for the Fitbit Web API. OAuth 2.0 PKCE, local SQLite cache with auto-sync, and trend analysis. Tools for heart rate, activity, exercises, sleep, weight, SpO2, and HRV.
Query FIFA World Cup 2026 matches. Filter by date, date range, team, group, venue, round, or status. Returns enriched match data with team names, venue details, and local venue time. Optionally pass a timezone to convert match times to any IANA timezone.
get_teams
Query FIFA World Cup 2026 teams. Filter by group, confederation, or host status. Returns team details including FIFA ranking and flag emoji.
get_groups
Get FIFA World Cup 2026 group details. Returns teams, venues, and match schedule for each group. Optionally filter to a specific group.
get_venues
Query FIFA World Cup 2026 venues across the USA, Mexico, and Canada. Filter by country, city, or region. Returns full venue details including capacity, coordinates, and notable events.
get_schedule
Get the full FIFA World Cup 2026 tournament schedule organized by date. Optionally filter to a specific date range. Each day includes all matches with team names, venues, kick-off times (UTC), and local venue time. Optionally pass a timezone to convert all match times.
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).
Wc26 MCP is categorized under Sports and uses a local stdio subprocess. In contrast, Fitbit MCP belongs to Sports using local stdio subprocess. Select Wc26 MCP when you need capabilities focused on sports and Fitbit MCP when you require tools for sports.
Get a detailed profile for any FIFA World Cup 2026 team. Returns coach, playing style, key players with clubs, World Cup history, and qualifying summary. Use team ID or FIFA code (e.g. 'usa', 'BRA', 'arg').
get_nearby_venues
Find venues near a given World Cup venue, sorted by distance. Useful for planning multi-match trips. Returns distance in miles and kilometers between all venue pairs.
get_city_guide
Get a travel guide for any FIFA World Cup 2026 host city. Returns highlights, getting there, food & drink recommendations, things to do, and local tips. Accepts venue ID (e.g. 'metlife'), city name (e.g. 'Miami'), or metro area name (e.g. 'New York'). Case-insensitive.
get_historical_matchups
Head-to-head World Cup history between any two teams. Returns all tournament meetings, aggregate stats, and a narrative summary. Accepts team ID or FIFA code (e.g. 'bra', 'ARG', 'england'). Also checks for a scheduled 2026 match between the pair.
what_to_know_now
Zero-query temporal briefing for the FIFA World Cup 2026. No parameters needed — just brief me. Automatically detects the current tournament phase and returns the most relevant information for today. Optionally pass a date to simulate a different day, or a timezone for local times.
get_visa_info
Entry requirements for FIFA World Cup 2026 travelers. Returns visa/ESTA/eTA requirements for any team's nationals entering the three host countries (USA, Mexico, Canada). Accepts team ID, FIFA code, or country name. Optionally filter to a specific host country.
get_fan_zones
Official FIFA Fan Festival and fan zone locations for World Cup 2026 host cities. Returns venue details, capacity, hours, activities, transportation tips, and amenities. Filter by city, country, or match venue.
+6 more tools listed on main page
Fitbit MCP Tools (18)
fitbit_sync
Sync Fitbit health data to the local cache.
Fetches data from the Fitbit API and stores it in SQLite for fast
offline queries. Run this before using other fitbit_get_* tools.
Syncs incrementally: only fetches data newer than the most recent
entry in each table. First sync fetches the specified number of days.
Args:
data_types: What to sync. Options: "all", "heart_rate", "activity",
"exercises", "sleep", "weight", "spo2", "hrv", "azm",
"breathing_rate", "skin_temperature", "core_temperature",
"cardio_fitness", "food_log".
Comma-separated for multiple, e.g. "sleep,hrv". Default: "all".
days: Days of history for first sync (default: 30). Ignored
on subsequent syncs (uses last synced date).
since: Optional "YYYY-MM-DD" backfill date. When set, fetches from this
date regardless of what is already cached - use to pull history
older than the current cache. Overrides incremental resume and days.
until: Optional "YYYY-MM-DD" inclusive end date; requires since.
Together they re-fetch and upsert exactly the since..until window -
use to repair a gap in the middle of the cache without re-pulling
everything from the gap to today.
Returns summary of records synced per data type.
Not for querying data - use fitbit_get_heart_rate, fitbit_get_activity,
fitbit_get_sleep, etc. instead.
fitbit_get_activity
Get daily activity summaries (steps, calories, active minutes, distance).
Returns data from the local cache by default. Use live=True to fetch
from Fitbit API. Run fitbit_sync first to populate the cache.
Note: live=True fetches one API call per day - avoid large ranges to
stay within the 150 requests/hour rate limit.
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 directly from Fitbit API instead of cache.
Returns one entry per day with steps, calories, active minutes, distance.
active_minutes = very_active + fairly_active (excludes lightly active).
fitbit_trends
Analyse trends in cached Fitbit data.
Computes averages and totals over time from the local cache,
auto-syncing if stale.
Args:
data_type: What to analyse. Options: "heart_rate", "activity",
"exercises", "sleep", "weight", "spo2", "hrv", "azm",
"breathing_rate", "skin_temperature", "core_temperature",
"cardio_fitness", "food_log". Default: "activity".
period: Aggregation period. Options: "weekly", "monthly",
"quarterly". Default: "monthly".
start_date: Start date as "YYYY-MM-DD" or "365d". 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 per period. For activity: steps, distance,
active minutes. For exercises: sessions, duration, calories.
For sleep: duration, efficiency, stage breakdown.
For heart_rate: resting HR min/avg/max. For weight: weight, fat%, BMI.
For spo2: avg/min/max oxygen saturation. For hrv: daily and deep RMSSD.
Not for raw data - use fitbit_get_* tools instead.
fitbit_get_azm
Get daily Active Zone Minutes (AZM) - Fitbit's headline cardio metric.
AZM counts minutes spent in heart rate zones at or above Fat Burn intensity.
Cardio and Peak zone minutes count double. Returns from local cache by default,
auto-syncing if stale. Use live=True to bypass 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 directly from Fitbit API instead of cache.
Returns one entry per day with total_minutes plus per-zone breakdown
(fat_burn_minutes, cardio_minutes, peak_minutes).
Distinct from active_minutes in fitbit_get_activity, which counts wall-clock
minutes regardless of intensity.
fitbit_get_breathing_rate
Get nightly breathing rate (avg breaths per minute during sleep).
Sourced during sleep tracking. Useful as an illness/recovery signal:
sustained increases of 2-3 bpm above personal baseline can indicate
incipient infection or strain. Returns from cache by default,
auto-syncing if stale.
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 directly from Fitbit API instead of cache.
Returns one entry per night with breaths_per_min.
Typical adult range: 12-20 bpm at rest.
fitbit_get_cardio_fitness
Get Cardio Fitness Score (VO2 Max estimate).
Fitbit estimates VO2 Max from resting HR, HR during walks/runs, and demographics.
Updates roughly weekly. Returns from cache by default, auto-syncing if stale.
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 directly from Fitbit API instead of cache.
Returns entries with vo2_max_low and vo2_max_high (mL/kg/min).
Fitbit reports as a range (e.g. 39-43); when a single value is given,
low and high are equal. Higher = better cardiorespiratory fitness.
fitbit_get_devices
List paired Fitbit devices with battery level and last sync time.
Live-only (no caching) - reflects current device state. Useful for
monitoring tracker health, knowing which device produced data, and
spotting sync gaps.
Returns one entry per paired device with id, type, device_version,
battery (e.g. "High"), battery_level (0-100), last_sync_time, mac,
and features list.
fitbit_get_exercises
Get exercise log entries (individual tracked activities).
Returns exercise sessions from the local cache by default. Use live=True
to fetch from Fitbit API. Run fitbit_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.
exercise_type: Filter by activity name (case-insensitive substring match),
e.g. "cycling", "walk", "run". Default: all types.
live: If true, fetch directly from Fitbit API instead of cache.
Returns exercise entries with name, duration, calories, avg heart rate,
distance, and source (auto-detect vs manual).
Note: HR data from cycling may be unreliable (optical sensor vs handlebar grip).
fitbit_get_food_log
Get daily food and water log summary.
Returns calories consumed and water intake (in mL) per day. Only populated
if the user logs food/water in the Fitbit app. Returns from cache by default,
auto-syncing if stale.
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 directly from Fitbit API. Uses one API call per day.
Returns one entry per day with calories_in and water_ml.
Days with no logging are omitted.
fitbit_get_heart_rate
Get daily resting heart rate and heart rate zones.
Returns resting HR and zone breakdown (Out of Range, Fat Burn, Cardio, Peak)
from the local cache by default, auto-syncing if stale. Use live=True to
bypass the cache entirely.
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 directly from Fitbit API instead of cache.
Returns one entry per day with resting_hr and zones array.
Zone data: name, minutes, caloriesOut, max/min HR for each zone.
fitbit_get_hrv
Get nightly HRV (heart rate variability) data.
Returns data from the local cache by default. Use live=True to fetch
from Fitbit API. Run fitbit_sync first to populate the cache.
HRV data is sparse: only nights with on-wrist sleep tracking produce readings.
Requires Fitbit Premium for access to this endpoint.
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 directly from Fitbit API instead of cache.
Returns one entry per night with daily_rmssd and deep_rmssd (ms).
RMSSD = root mean square of successive RR interval differences.
Higher values generally indicate better recovery and parasympathetic activity.
fitbit_get_lifetime_stats
Get all-time activity totals and personal best records.
Live-only (no caching). Returns lifetime totals (steps, distance, floors,
calories, active score) and personal bests (best day for steps, distance,
floors), each with the date the record was set.
Useful for long-term context that the daily activity table can't easily
answer (e.g. "what's my best step day ever?").