bosch-flow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bosch_get_activitiesA | 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_detailA | 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_syncA | 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. |
| bosch_battery_trendsA | Analyse battery health trends for your Bosch eBike over time. Computes per-period averages and deltas for:
A declining remaining_energy_wh at a constant charge level indicates the battery capacity is degrading. Compare early and recent snapshots for a long-term health picture. Args: bike_id: Optional bike UUID. If omitted, includes all bikes. period: Aggregation period. Options: "weekly", "monthly" (default), "quarterly". start_date: Start date (YYYY-MM-DD, YYYY-MM, Nd, or None for all data). end_date: End date. Default: today. |
| bosch_get_batteriesA | Get battery state and health for your Bosch eBike. Returns charge level, remaining energy, total capacity, charge cycles (total / on-bike / off-bike), lifetime energy delivered, and software version. Each sync captures a snapshot, building a time series of battery health. Use latest_only=False with a date range to see history. Args: bike_id: Optional bike UUID to filter to one bike. start_date: Start date (YYYY-MM-DD, YYYY-MM, or Nd like "30d"). Default: 30 days ago. end_date: End date. Default: today. latest_only: If True (default), return only the most recent snapshot per bike. Set to False to return all snapshots in the date range. |
| bosch_get_socA | Get live state-of-charge from the Bosch ConnectModule. Returns real-time battery percentage, charging status, remaining energy, and reachable range per assist mode (eco/tour/sport/turbo). Requires a ConnectModule on the bike. Data is only available when the bike is powered on, charging, or recently active. Note: This calls the Bosch mobile API live - no caching. Args: bike_id: The bike UUID from bosch_get_bikes. |
| bosch_get_capacityA | Get battery capacity tester diagnostic results. Shows battery health data from Bosch's official capacity tester tool, typically done at dealer service appointments. Includes remaining capacity percentage vs. original specification. Capacity-tester data comes only from the EU Data Act API; with a standard Bosch eBike Flow sign-in this is empty and the result explains why. Args: part_number: Optional battery part number to filter results. serial_number: Optional battery serial number to filter results. |
| bosch_get_bikesA | List all Bosch eBikes registered to your Flow account. Returns bike names, brand, and frame numbers. Uses local cache (auto-syncs if stale). Run bosch_sync first if the list is empty. Returns a list of bikes with id, name, brand_name, and frame_number. |
| bosch_get_bikeA | Get detailed profile for a single Bosch eBike. Returns full bike details including brand, model, frame number, and the cached raw API response which may include component info. Args: bike_id: The bike UUID from bosch_get_bikes. |
| bosch_get_componentsA | List registered components for your Bosch eBike with software versions. Shows the bike's components - drive unit, battery, ConnectModule, head unit, remote control, ABS - with part numbers, serial numbers, and firmware versions. The source depends on your sign-in: a standard Bosch eBike Flow account reads them from the bike profile (mobile app API); an EU Data Act (euda) client reads them from the Data Act registrations endpoint. Useful for tracking firmware versions and identifying components for warranty or service purposes. Args: bike_id: Optional bike UUID to filter to one bike. component_type: Optional component type filter, e.g. "driveUnit", "battery", "headUnit", "connectedModule", "remoteControl". |
| bosch_get_service_recordsA | Get the digital service book history for your Bosch eBike. Returns all service records logged by Bosch dealers and service centres, including dates and descriptions of work performed. Service records come only from the EU Data Act API; with a standard Bosch eBike Flow sign-in this is empty and the result explains why (register a euda client). Args: bike_id: Optional bike UUID to filter to one bike. start_date: Start date (YYYY-MM-DD, YYYY-MM, or Nd). Default: all records. end_date: End date. Default: today. |
| bosch_get_software_updatesA | Get software update installation history for your Bosch eBike. Returns all firmware/software update reports, showing which components were updated, from which version to which version, and when. This history comes only from the EU Data Act API; with a standard Bosch eBike Flow sign-in it is empty (current firmware is still available via components). Args: bike_id: Optional bike UUID to filter to one bike. start_date: Start date (YYYY-MM-DD, YYYY-MM, or Nd). Default: all records. end_date: End date. Default: today. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/partymola/bosch-flow-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server