Bosch Flow MCP

Name: Bosch Flow MCP
Author: partymola

by partymolaversion 0.10.0i★ –iRuns on your computer

Registry nameio.github.partymola/bosch-flow-mcp

Install

Overview

Description from the maker (original English)

MCP server for Bosch eBike Flow (BES3): battery health, charge cycles, components, and ride data.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiEarly↓ 566/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Clinics & health

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "bosch-flow": {
      "command": "uvx",
      "args": [
        "bosch-flow-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add bosch-flow -- uvx bosch-flow-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "bosch-flow": {
      "command": "uvx",
      "args": [
        "bosch-flow-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "bosch-flow": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "bosch-flow-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account partymola, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Clinics & healthi

More stars than 0% of the other 1034 servers in this category
Published to the registry more recently than 90% of the other 1034 servers in this category
Basic checks equal to or better than 100% of the other 1034 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Bosch Flow MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.10.0) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Mirobody, FHIR MCP Server, Google Health MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Mirobody

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

by thetahealthGrowing↓ 290/wk★ 1.4KUpdated 2 days ago

Runs on your computer✓ thetahealth.ai

Install

FHIR MCP Server

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

by wso2Growing↓ 823/wk★ 137Updated 11 days ago

Runs on your computer

Install

Google Health MCP

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

by davidmosiahGrowing↓ 1K/wk★ 79Updated 4 months ago

Runs on your computer

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

bosch-flow-mcp

MCP server for Bosch eBike Flow (Smart System / BES3). Tracks battery health, charge cycles, component versions, service history, live state-of-charge, and per-ride activity data (distance, elevation, power, assist-mode, CO2).

Disclaimer

This is an unofficial, community-built project. It is not affiliated with, authorised by, or endorsed by Robert Bosch GmbH, Bosch eBike Systems, or SingleKey ID. "Bosch", "eBike Flow", and related marks belong to their owners and are used here only to describe interoperability.

It signs in with your own Bosch eBike Flow account (via the standard SingleKey ID login) and reads only your own data. It is read-only - it never modifies your bike, battery, or account.
It uses the same public OAuth client (one-bike-app, PKCE) that the official Bosch eBike Flow app uses. No credentials, secrets, or protection measures are extracted, bypassed, or circumvented - every identifier here is already publicly documented.
When you supply your own EU Data Act API credentials, the official Data Act API is used. Otherwise the same app API your phone already uses is queried with your own login.
This is an undocumented, unofficial interface that may change or stop working at any time if Bosch alters their systems.
You are responsible for ensuring your use complies with Bosch's and SingleKey ID's terms of service in your jurisdiction.
Provided with no warranty under GPLv3+ (see LICENSE). Use at your own risk.

Features

Battery state snapshots over time (charge cycles, energy delivered, degradation trends)
Components and firmware versions (drive unit, battery, ConnectModule, head unit, remote, ABS)
Service book history and software update log (EU Data Act client only)
Live state-of-charge from ConnectModule via mobile API
Battery capacity tester results (EU Data Act client only)
Per-ride activities: distance, elevation, speed, cadence, measured rider power, calories, rider-vs-motor energy share, assist-mode split, CO2, ABS events, plus a per-point GPS/speed/elevation/power track
Auto-sync on demand - tools fetch fresh data without a cron job

Requirements

Python 3.13+ (tested on 3.13, 3.14 and 3.15, on Linux, macOS and Windows, in CI)
uv (recommended) or pip
A Bosch eBike Flow account (free, register at the Bosch eBike Flow app)
A BES3 Smart System eBike registered in the app

Install

pip install bosch-flow-mcp

Or run it without installing with uvx bosch-flow-mcp. For development from a clone:

git clone https://github.com/partymola/bosch-flow-mcp

cd bosch-flow-mcp uv venv --python 3.13 .venv uv pip install -e .

Auth

.venv/bin/bosch-flow-mcp auth

Opens your browser to Bosch login. The auth flow uses the one-bike-app public client with PKCE - no API keys or registration needed. Just your Bosch Flow account.

Important: Open browser DevTools (F12) and switch to the Network tab before logging in. After login, the browser redirects to an iOS URI (onebikeapp-ios://) that desktop browsers can't open. Copy the full redirect URL from DevTools (right-click > Copy URL on the oauth2redirect entry) and paste it at the prompt.

Tokens are saved to config/bosch_tokens.json and auto-refresh via offline_access.

EU Data Act users: if you have registered your own euda client and placed its ID in config/bosch_config.json, auth uses that instead - it opens the browser and completes automatically through a local http://localhost:4200 callback, with no DevTools step.

Sync

.venv/bin/bosch-flow-mcp sync                     # all data types

.venv/bin/bosch-flow-mcp sync --types bikes,batteries

Data types: bikes, batteries, components, service, software_updates, capacity.

Fetches your data and stores it locally. The source depends on your sign-in:

A standard Bosch eBike Flow account (the default) reads bikes, batteries, components, current firmware, and live state-of-charge from the mobile app API - works for any account, including non-EU.
Service-book history, software-update history, and capacity-tester results come only from the EU Data Act API, which requires registering your own euda client at the Bosch Data Act portal. With a standard sign-in those types report unavailable (with a note) rather than a silent empty result, and the Data Act API returns nothing for accounts registered outside the EU.

You can also use the bosch_sync MCP tool, or rely on automatic sync (each get_* tool triggers a sync if data is stale).

Run bosch-flow-mcp --version to print the installed package version.

Register with Claude Code

claude mcp add -s user bosch-flow -- /full/path/to/bosch-flow-mcp/.venv/bin/bosch-flow-mcp

Then ask Claude questions like:

"What's my bike's battery health this year?"
"Show me charge cycle trends by month"
"What firmware version is my drive unit on?"
"Have there been any service records for my bike?"
"How far and how hard were my rides this week?"

Available tools

Tool	Description
`bosch_sync`	Sync one or more data types (default: all)
`bosch_get_bikes`	List registered bikes
`bosch_get_bike`	Single bike with full details
`bosch_get_batteries`	Battery snapshots - latest or historical range
`bosch_get_soc`	Live state-of-charge from ConnectModule
`bosch_get_capacity`	Battery capacity tester results (EU Data Act client only)
`bosch_get_components`	Components with part numbers and firmware versions
`bosch_get_service_records`	Service book entries (EU Data Act client only)
`bosch_get_software_updates`	Software update history (EU Data Act client only)
`bosch_battery_trends`	Charge cycle and energy trends by period
`bosch_get_activities`	Per-ride summaries (distance, elevation, power, mode, CO2) over a date range
`bosch_get_activity_detail`	Per-point track for one ride (GPS/speed/elevation/cadence/power)

API credits

This server uses the Bosch Mobile API (obc-rider-profile.prod.connected-biking.cloud) as the primary data source, the rider-activity API (obc-rider-activity.prod.connected-biking.cloud) for per-ride data, and optional Data Act API (api.bosch-ebike.com) support for additional endpoints.

Authentication uses the one-bike-app public client (the same OAuth client as the Bosch eBike Flow mobile app). The auth approach was documented by the marq24/ha-bosch-ebike-flow Home Assistant integration and the open-ebike/open-ebike-backend project.

Configuration

Variable	Default	Description
`BOSCH_FLOW_MCP_DB_PATH`	`bosch_flow.db` in the package root	SQLite database path
`BOSCH_FLOW_MCP_CONFIG_DIR`	`config/` in the package root	Directory for tokens and client config

Data safety

OAuth tokens are created at 0600 on POSIX - Windows ignores the mode and governs access by inherited ACLs; the token files and bosch_flow.db are gitignored.
A pre-commit hook (scripts/check-no-data.sh) blocks committing database files, files under config/, and large files. It does not read file contents. Install it after cloning:

  ln -sf ../../scripts/check-no-data.sh .git/hooks/pre-commit

Tests use temporary SQLite databases and fictional identifiers - no real bike or account data ever enters the repo.

Contributing

See CONTRIBUTING.md for development setup, the test workflow, and the pre-commit hook. Changes are tracked in CHANGELOG.md.

License

GPLv3+. See LICENSE.

Bosch Flow MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Clinics & healthi

Common questions

Alternatives

Mirobody

FHIR MCP Server

Google Health MCP

README from the maker

bosch-flow-mcp

Disclaimer

Features

Requirements

Install

Auth

Sync

Register with Claude Code

Available tools

API credits

Configuration

Data safety

Contributing

License