A
licenseA
qualityA
maintenanceMCP server for the Fitbit Web API with OAuth PKCE, local cache, and trend analysis.
18
2
GPL 3.0
bosch-flow-mcp
by partymola
Related Servers
Alternatives to bosch-flow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenancePrivacy-first MCP server for Strava activities, streams, routes and training data.29189 npm3MIT
- AlicenseBqualityAmaintenanceMCP server for local fitness-data extraction and analysis from Garmin Connect, Intervals.icu, and Strava. Provides read-only analytical tools over DuckDB and targeted Strava enrichment.3527 npmAGPL 3.0
- FlicenseAqualityCmaintenanceProvides read-only access to your Garmin Connect health data, including sleep, HRV, body battery, stress, training readiness, and activities, through an MCP server.14-
- AlicenseCqualityCmaintenanceMCP server for Mi Fitness cloud data. Provides a local SQLite-backed server to sync and query daily activity, heart rate, and body measurements.125MIT
- AlicenseAqualityBmaintenanceMCP server for reading and querying Garmin Connect data, including activities, strength history, recovery, trends, and optionally creating workouts.12MIT
TDQS
A4.2/5.0
Scored across 12 tools
Disambiguation3/5
Several battery-focused tools (bosch_get_soc, bosch_get_batteries, bosch_battery_trends, bosch_get_capacity) overlap in terms of charge/health data, and singular/plural pairs like get_bikes/get_bike and get_activities/get_activity_detail could be mixed up. The descriptions do clarify live vs historical vs analysed vs capacity-tester data, so most confusion can be resolved by reading carefully.
Naming Consistency4/5
Most tools follow the bosch_get_<resource> pattern, making the set highly predictable. The exceptions are bosch_sync and bosch_battery_trends, which break the get_ prefix but remain understandable; minor singular/plural inconsistencies also slightly reduce consistency.
Tool Count5/5
Twelve tools is well-scoped for a Bosch eBike data server: one sync/maintenence primitive plus read endpoints for bikes, battery health, activities, components, service records, and software updates. Each tool has a distinct role and none feel redundant or filler.
Completeness5/5
The tool surface covers the relevant read-only domain thoroughly: bike inventory, live and historical battery state, capacity diagnostics, ride summaries and details, components, service records, and software update history. No critical gap is apparent for a Flow eBike data-access server, and the sync tool ties the cached data sources together.
Maintenance
ActivityActive
ResponsivenessNo issues