Bosch Flow MCP

Name: Bosch Flow MCP
Author: partymola

作者：partymola版本 0.10.0i★ –i在你的电脑上运行

注册名称io.github.partymola/bosch-flow-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i起步阶段↓ 566/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 诊所与健康

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 partymola 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“诊所与健康”中的其他服务器比较i

星标数多于此分类中其他 1037 个服务器的 0%
发布到注册中心的时间比此分类中其他 1037 个服务器的 89% 更新
基础检查结果等于或优于此分类中其他 1037 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Bosch Flow MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.10.0）于3天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Mirobody, FHIR MCP Server, Google Health MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Mirobody

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

作者：thetahealth正在增长↓ 290/周★ 1408前天更新

在你的电脑上运行✓ thetahealth.ai

安装

FHIR MCP Server

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

作者：wso2正在增长↓ 823/周★ 13711天前更新

在你的电脑上运行

安装

Google Health MCP

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

作者：davidmosiah正在增长↓ 1024/周★ 794个月前更新

在你的电脑上运行

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.