A
licenseA
qualityF
maintenanceMCP server for the Fitbit Web API with OAuth PKCE, local cache, and trend analysis.
18
29 PyPI
2
GPL 3.0
bosch-flow-mcp
by partymola
Related Servers
Alternatives to bosch-flow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenancePrivacy-first MCP server for Strava activities, streams, routes and training data.29295 npm3MIT
- AlicenseBqualityBmaintenanceMCP 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.35759 npm1AGPL 3.0
- FlicenseAqualityDmaintenanceProvides read-only access to your Garmin Connect health data, including sleep, HRV, body battery, stress, training readiness, and activities, through an MCP server.214-
- AlicenseCqualityCmaintenanceMCP server for Mi Fitness cloud data. Provides a local SQLite-backed server to sync and query daily activity, heart rate, and body measurements.128MIT
- AlicenseAqualityDmaintenanceMCP server for reading and querying Garmin Connect data, including activities, strength history, recovery, trends, and optionally creating workouts.12MIT
TDQS
A3.9/5.0
Scored across 12 tools
Disambiguation4/5
Most tools target clearly distinct resources (live SOC, ride activities, activity track, bikes, components, service records, updates, capacity tests). The mild overlap sits between bosch_get_batteries (cached snapshots/health), bosch_battery_trends (aggregated trends), and bosch_get_soc (live state) — but the descriptions clearly separate live vs. cached vs. derived, so an agent can choose correctly.
Naming Consistency4/5
All names are snake_case with a uniform bosch_ prefix, giving a predictable namespace. The only deviation is bosch_battery_trends and bosch_sync, which drop the get_ verb, but they remain readable and clearly scoped.
Tool Count5/5
Twelve tools is well within a comfortable range and each covers a distinct slice of the eBike data domain (rides, battery, components, service, updates). No redundant or filler tools are present.
Completeness4/5
The surface covers the full read lifecycle: sync, bikes/bike, components, batteries/SOC/trends/capacity, activities/detail, service records, and software updates. Minor gaps exist — no write operations (e.g. tagging or notes on rides) and no explicit charge-session or motor-statistics view — but core workflows are covered.
Maintenance
ActivityActive
ResponsivenessNo recent community issues