MCP Tools DirectoryAbout this integration
MCP server for Bosch eBike Flow (BES3): battery health, charge cycles, components, and ride data.
- Transport
- stdio
- Authentication
- oauth
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.7.0
- Package
- bosch-flow-mcp
- Last compatibility test
- Not independently tested
Connect your agent
bosch-flow-mcpThis is an unofficial community integration using the user's own account. Publisher documentation establishes an initial browser authorization, offline token refresh, automatic stale-data synchronization, and stdio registration. The package and Bosch services were not executed or independently security-audited.
Capabilities: Synchronize Bosch eBike data, Read bike and battery status, Analyze battery trends, Read service and software history when available, Read ride activity summaries
Connected profiles
Additional details
io.github.partymola/bosch-flow-mcp
Source ↗ · Checked 2026-09-170.7.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17bosch-flow-mcp
Source ↗ · Checked 2026-09-190.7.0
Source ↗ · Checked 2026-09-19After user authorization, publisher documentation says data tools automatically synchronize stale data and saved tokens refresh through offline access; this is documented behavior, not a runtime test.
Source ↗ · Checked 2026-09-19OAuth with PKCE requires an initial Bosch account browser authorization. The standard flow includes a manual redirect-copy step; stored tokens then auto-refresh through offline_access.
Source ↗ · Checked 2026-09-19Existing connection identity is preserved as a local stdio console process registered with the client; no endpoint is asserted.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19