Bosch Flow MCP vs MCP Sports Hub

bosch_get_activities

List e-bike rides with per-ride summary metrics. Live read from the Bosch rider-activity API (no cache). Each ride includes distance, elevation gain/loss, avg/max speed, cadence, measured rider power, calories, rider-vs-motor energy share, assist-mode distance split (metres per mode), CO2 (emissions / car-equivalent / saved), and ABS/brake events. Heart rate is not recorded by the bike (it has no HR sensor) - pair with a wrist device for HR. Args: start_date: Window start (YYYY-MM-DD, YYYY-MM, or "30d"). Default 30 days ago. end_date: Window end. Default today. bike_id: Optional bike UUID filter. limit: Optional cap on rides returned (most recent first).

bosch_get_activity_detail

Get the per-point track for one ride (GPS + speed/elevation/cadence/power). Live read. Returns a downsampled track (~500 points per ride): per-point cumulative distance (m), speed (km/h), elevation (m), cadence, rider power (W), and GPS lat/lon. Get the activity_id from bosch_get_activities. Args: activity_id: The ride UUID from bosch_get_activities.

bosch_sync

Sync Bosch eBike data to the local cache. Fetches data from Bosch and stores it in SQLite. The source depends on your sign-in: a standard Bosch eBike Flow account uses the mobile app API; an EU Data Act (euda) client uses the Data Act API. Run this to populate the cache before using other bosch_get_* tools, or to refresh after a ride or charge cycle. Bikes are identified automatically from your Bosch Flow account. Battery snapshots build a time series for health trend analysis. Service records, software-update history and capacity-tester data are only available with a euda (EU Data Act) client; with a standard sign-in they report status "unavailable" rather than an empty result. Args: data_types: What to sync. Options: "all", "bikes", "batteries", "components", "service", "software_updates", "capacity". Comma-separated for multiple, e.g. "bikes,batteries". Default: "all". Returns a per-type summary: status (ok/empty/unavailable/error), record count, and a message explaining any non-ok result.