Bosch Smart Home Camera MCP Server
The Bosch Smart Home Camera MCP Server exposes camera cloud and LAN APIs as MCP tools, enabling LLMs to control, monitor, and diagnose Bosch Smart Home cameras via natural language.
Camera Discovery & Status
List all cameras with online status, model, and hardware generation
Get per-camera status (privacy mode, spotlight state, last event)
Bulk health check all cameras at once
Check token validity/expiry and account-level feature flags
Media Capture (LAN-only)
Take JPEG snapshots directly over LAN
Get RTSPS stream URLs for use with ffmpeg/VLC/go2rtc
Open listen-only audio intercom sessions
Camera Control
Toggle privacy mode and spotlight on/off
Pan 360° cameras using named presets or directional commands
Toggle push notifications
Trigger/stop the indoor siren and set siren duration
Enable/disable 360° auto-tracking and audible privacy-chime
Motion, Detection & Audio Settings
Get/set motion detection state, sensitivity, and zones
Get/set privacy mask zones (permanently blacks out video regions)
Get/set intrusion detection mode, sensitivity, and distance (Gen2 only)
Enable/disable glass-break and fire/smoke alarm sound detection (Gen2 Audio-Plus only)
Get/set microphone and speaker levels (Gen2 only)
Recording, Lighting & Scheduling
Get/set cloud recording audio inclusion
Get/set LED lighting schedules (outdoor models only)
List, add, edit, and delete time-based automation rules per camera
Network & Diagnostics
TCP-probe cameras on LAN to check reachability
Get WiFi signal info (RSSI, SSID, signal quality)
Check cloud maintenance status from Bosch community RSS
Read ONVIF device scopes and RCP firmware version (Gen2 LAN, only)
Firmware Management
Check firmware status (current vs. latest version)
Install pending firmware updates
Camera Sharing
List friends and invitations with shared cameras
Invite friends by email, share/revoke specific cameras, remove friends
Events
List recent motion/person/audio events with timestamps and clip availability
Get unread event count per camera
MCP Resources & Prompts
Resources: camera list, per-camera snapshots, per-camera event feeds
Prompts: daily camera summary and pre-leave anomaly check
Transport: Supports stdio, SSE, and streamable-HTTP for flexible MCP client integration.
Provides tools for managing Bosch Smart Home Cameras, including capturing snapshots, streaming video, controlling privacy mode, panning 360° cameras, retrieving events, and adjusting settings like motion detection, audio, and lighting.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Bosch Smart Home Camera MCP ServerTake a snapshot of the front door camera"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Bosch Smart Home Camera — MCP Server
Model Context Protocol (MCP) server that exposes the Bosch Smart Home Camera cloud API as MCP tools. Drop-in for Claude Code, Claude Desktop, and any MCP-compatible client. Reuses the proven reverse-engineered API client from the sister Python CLI tool.
Status: v1.7.0 — family-parity closeout: motion zones, privacy masks, automation rules, camera sharing/friends, firmware install, siren duration, lighting schedule, listen-audio intercom. 55 tools + 3 resources + 2 prompts, stdio/SSE/streamable-HTTP, pipx/uvx-installable
Table of Contents
Integration Comparison — pick the right project for your platform
Related MCP server: Fibaro MCP
Disclaimer
This project is an independent, community-developed tool. It is not affiliated with, endorsed by, sponsored by, or in any way officially connected to Robert Bosch GmbH, Bosch Smart Home GmbH, or any of their subsidiaries or affiliates. "Bosch", "Bosch Smart Home", and related names and logos are registered trademarks of Robert Bosch GmbH.
The tool communicates with a reverse-engineered, undocumented, unofficial API. Provided "as is", without warranty of any kind. Use entirely at your own risk.
Why a separate MCP server?
The sister projects target different runtimes:
Project | Version | Runtime | User-facing surface |
v14.4.1 | Home Assistant | UI entities, Lovelace card, automations | |
v10.10.4 | terminal |
| |
v1.7.7 | ioBroker | datapoints, VIS-2 widgets (BoschCamera + BoschOverview), JSON-config admin UI | |
v0.2.5-alpha | Node-RED | flow nodes for automation pipelines | |
MCP Server (this repo) | v1.7.0 | Claude clients | MCP tools callable from LLMs |
LLM use-cases the existing sisters don't cover:
"Take a snapshot of the garden camera and describe what you see."
"What was the last motion event on the terrace, and at what time?"
"Enable privacy mode on the indoor camera until 22:00, then disable it."
"Pan the 360° camera to the left and grab a snapshot."
"Summarise today's motion events across all cameras."
These flows require an LLM in the loop — which is exactly what MCP is for.
Architecture
┌─────────────────────────┐ stdio / SSE / streamable HTTP ┌─────────────────────────┐
│ Claude Code / Desktop │ ←─────────────────────────────────────→ │ bosch-smart-home- │
│ (MCP host) │ MCP protocol │ camera-mcp server │
└─────────────────────────┘ └────────────┬────────────┘
│
imports / shared API client
│
▼
┌─────────────────────────┐
│ bosch_camera.py │
│ (sister Python CLI tool)│
└────────────┬────────────┘
│ HTTPS (OAuth2 PKCE)
▼
┌─────────────────────────┐
│ residential.cbs.bosch- │
│ security.com (cloud) │
└─────────────────────────┘The MCP server is a thin wrapper around the Python CLI's API layer. It does not re-implement OAuth, token refresh, FCM push, RTSP, or RCP — it imports them.
LAN-fallback tool routing
flowchart LR
Agent["LLM / Claude Code"] -->|tool call| MCP[MCP Server]
MCP -->|prefer_local=False| Cloud[Bosch CBS API]
MCP -->|prefer_local=True| RCP["Camera LAN RCP\n192.168.x.y:443\nHTTPS Digest"]
RCP -->|success| Done["return {status, method: local}"]
RCP -->|fail| Cloud
Cloud --> Done2["return {status, method: cloud}"]
style RCP fill:#d4f1c4,color:#000
style Cloud fill:#dce8fb,color:#000bosch_camera_lan_ping tool flow
sequenceDiagram
participant Agent as LLM Agent
participant Tool as bosch_camera_lan_ping
participant TCP as TCP connect :443
Agent->>Tool: {camera_name: "Outdoor"}
Tool->>Tool: resolve LAN IP from bosch_config.json
Tool->>TCP: connect 192.168.x.y:443 (1.5 s timeout)
TCP-->>Tool: connected / timeout
Tool-->>Agent: {reachable: true, ip: "...", latency_ms: 12}MCP tools (55 total, v1.7.0)
Tool | Description | Returns |
| List all configured cameras | array of |
| Get online/offline + privacy state for one camera |
|
| LAN-only JPEG capture (no cloud) — HTTP Digest to camera IP |
|
| LAN-only RTSPS stream URL (no cloud relay) — consumable by ffmpeg/VLC/go2rtc |
|
| List recent motion/person/audio events | array of |
| Turn privacy mode on/off; |
|
| Turn spotlight on/off; |
|
| Pan the 360° camera; |
|
| Toggle push notifications |
|
| TCP-probe a camera on LAN port 443 (1.5 s timeout) |
|
| Fetch current cloud maintenance announcement from community RSS feed |
|
| Get microphone level, speaker level, intercom flag (Gen2 only) |
|
| Set microphone level and/or speaker level 0-100 (Gen2 only) |
|
| Get intrusion detection config: mode, sensitivity 0-7, distance 1-8 m (Gen2 only) |
|
| Update intrusion detection mode/sensitivity/distance (Gen2 only) |
|
| Get glass-break + smoke/fire-alarm sound detection config (Gen2 Audio-Plus only) |
|
| Update glass-break and/or fire-alarm sound detection (Gen2 Audio-Plus only) |
|
| Get WiFi RSSI, SSID, and derived signal quality 0-100 % |
|
| Direct LAN MJPEG snapshot via RTSP inst=3 (Gen2 only, ffmpeg, no cloud roundtrip) |
|
| Read ONVIF device scopes from camera LAN RCP 0x0a98 (Gen2 only) |
|
| Read RCP library version from camera LAN opcodes 0xff00 + 0xff04 |
|
| Fetch account-level Bosch cloud feature flags (no camera param) |
|
| Trigger the indoor siren (Gen2 Indoor II only); |
|
| Get motion detection enabled state + sensitivity |
|
| Set motion detection enabled and/or sensitivity |
|
| Get cloud recording sound setting |
|
| Set cloud recording sound |
|
| Get 360° auto-tracking state (Gen1 Indoor only) |
|
| Set 360° auto-tracking (Gen1 Indoor only) |
|
| Get audible privacy-chime state |
|
| Set audible privacy-chime state |
|
| Get unread event count for a camera |
|
| Bulk health summary for all cameras (status + WiFi + privacy + last-event + unread) | array of per-camera health dicts |
| Local JWT parse — returns validity, expiry, email (no network call) |
|
| List motion-detection zone rectangles (normalized 0.0-1.0) | array of |
| Replace all motion zones (full-replace, not merge) | array of |
| Remove all motion zones |
|
| List privacy-mask zone rectangles (normalized 0.0-1.0) | array of |
| Replace all privacy masks (full-replace, not merge) | array of |
| Remove all privacy masks |
|
| List automation (time-schedule) rules for one camera | array of |
| Create a new schedule rule |
|
| Update an existing rule (partial update) |
|
| Delete a rule |
|
| List camera-sharing friends/invitations (account-level) | array of |
| Invite a friend by email (account-level) |
|
| Share one camera with an existing friend (merges with their existing shares) |
|
| Revoke all camera shares from a friend |
|
| Remove a friend entirely |
|
| Get current/latest firmware version + update availability |
|
| Install the pending firmware update (camera reboots 3-7 min) |
|
| Set the siren alarm duration, 10-300 s (Gen2 Indoor II only) |
|
| Get the LED lighting schedule (outdoor Eyes cameras) |
|
| Update the LED lighting schedule (outdoor Eyes cameras) |
|
| Open a listen-audio session (camera mic → caller); returns an RTSPS URL, listen-only |
|
Tools intentionally NOT exposed to LLMs (write-risky / time-consuming):
Token refresh (handled silently by the underlying client)
Cloud clip download (large payloads)
Two-way talk (caller mic → camera speaker): not exposed by the Bosch cloud API at all (same limitation the sister CLI has) —
bosch_camera_intercom_openis listen-only
Reliability — transparent credential rotation
LAN-RCP tools (bosch_camera_privacy_set, bosch_camera_light_set, bosch_camera_pan with prefer_local=True) automatically retry once on HTTP 401 after re-fetching fresh Digest credentials from bosch_config.json. No user-visible API change — the retry is silent and the tool result is identical whether or not rotation was needed. This eliminates cold-start failures when the cached Digest nonce has expired.
MCP resources
Resource URI | Description |
| JSON list of all cameras (id, name, model, status, firmware, mac, description) |
| Latest cached JPEG, or fresh capture if cache empty |
| Last 50 events (motion, person, audio) as JSON list |
bosch://cameras is a static resource. The {name} variants are resource templates.
MCP prompts
Prompt | Arguments | Description |
|
| Multi-step report: events per camera, type breakdown, time distribution, anomaly highlights |
| (none) | Snapshot every camera, describe scene, flag anomalies, recommend indoor privacy mode |
Privacy stance — media operations are LAN-only
Snapshots and stream URLs go directly from the MCP host to the camera over the LAN — no Bosch cloud relay. The remaining tools (status, events, privacy/light/pan/notifications) still use the cloud because no local API is currently exposed for those endpoints.
Tool | Path |
| LAN only — HTTP Digest to camera IP |
| LAN only — RTSPS via local Bosch TLS proxy |
| LAN only — TCP connect to camera port 443 |
| Bosch cloud (no local API yet) |
| Bosch cloud |
| LAN-RCP first, cloud fallback — Gen2 only |
| Bosch cloud (no local API yet) |
The MCP host must be on the same network as the cameras for media tools to work. If it isn't, the snapshot/stream tools surface local_unavailable rather than falling back to cloud — by design.
Auth model
Server runs with the user's existing bosch_config.json from the sister Python tool — no separate OAuth flow. Two startup modes:
--config-from-cli(default): expectsbosch_config.jsonnext tobosch_camera.pyin a sibling checkout--config <path>: explicit path to abosch_config.json
The MCP server never reads or writes credentials beyond what the CLI tool already does (token refresh on 401, atomic save).
Transport modes
Three transport modes are supported via the --transport flag:
Mode | Flag | Use case |
|
| Claude Code / Claude Desktop — local subprocess |
|
| Remote / multi-client deployments over HTTP |
|
| Legacy SSE clients |
HTTP and SSE modes bind to 127.0.0.1:8765 by default (security-safe local-only).
Pass --http-host 0.0.0.0 only in trusted, firewalled network environments.
# stdio (default) — used by Claude Code / Claude Desktop
bosch-smart-home-camera-mcp --config ~/.config/bosch-camera/bosch_config.json
# streamable-HTTP — local port for multi-client use
bosch-smart-home-camera-mcp --transport http --http-port 8765
# streamable-HTTP — expose to LAN (ensure firewall rules!)
bosch-smart-home-camera-mcp --transport http --http-host 0.0.0.0 --http-port 8765Tech stack
Python 3.10+
mcp— official MCP Python SDKpydantic(already a transitive dep ofmcp) for tool schemasReuse:
bosch_camera.pyfrom sister repo as a Git submodule or as a Python import path
Installation
# via pipx (recommended for end users — isolated environment, PATH entry)
pipx install bosch-smart-home-camera-mcp
# via uvx (zero-install, one-shot — no persistent env needed)
uvx bosch-smart-home-camera-mcp --help
# from source (for development)
pip install -e .[test]Maintainers: PyPI publishing is automated — pushing a
v*.*.*tag triggers the publish-pypi workflow via OIDC Trusted Publisher. Do not runtwine uploadmanually.
Add to Claude Code — stdio (local, recommended)
claude mcp add bosch-camera -- bosch-smart-home-camera-mcp \
--config ~/.config/bosch-camera/bosch_config.jsonAdd to Claude Code — streamable-HTTP (remote server)
# Start server first:
bosch-smart-home-camera-mcp --transport http --http-port 8765
# Then register the HTTP endpoint:
claude mcp add bosch-camera --transport http http://127.0.0.1:8765/mcpAdd to Claude Desktop
Add the following to your claude_desktop_config.json (usually ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"bosch-camera": {
"command": "bosch-smart-home-camera-mcp",
"args": [
"--config",
"/path/to/bosch_config.json"
]
}
}
}Replace /path/to/bosch_config.json with the actual path to your bosch_config.json (generated by the sister Python CLI tool via bosch_camera login). The server runs as a local stdio subprocess — no network port needed for Claude Desktop.
Repo layout
Bosch-Smart-Home-Camera-Tool-MCP/
├── README.md this file
├── CHANGELOG.md full version history
├── LICENSE MIT
├── pyproject.toml build + tool config
├── requirements.txt runtime pins (mcp, etc.)
├── requirements-test.txt pytest, pytest-asyncio, mocks
├── src/
│ └── bosch_camera_mcp/
│ ├── __init__.py
│ ├── server.py FastMCP server + all 32 MCP tools
│ ├── adapters/
│ │ ├── cli_bridge.py bridge to Python CLI for cloud ops
│ │ └── __init__.py
│ ├── lan_rcp.py direct LAN HTTPS+Digest for RCP writes
│ ├── maintenance.py cloud maintenance RSS feed fetcher
│ ├── errors.py shared error types
│ ├── resources.py MCP resources (bosch://cameras/…)
│ └── prompts.py MCP prompts (daily-summary, pre-leave)
├── tests/
│ ├── test_tools_integration.py
│ ├── test_audio_intrusion_wifi.py
│ ├── test_cert_pinning.py
│ ├── test_cred_rotation.py
│ ├── test_lan_ping.py
│ ├── test_lan_rcp_https.py
│ ├── test_maintenance.py
│ ├── test_packaging.py
│ ├── test_pan_presets.py
│ ├── test_prompts.py
│ ├── test_resources.py
│ ├── test_skeleton.py
│ ├── test_transport.py
│ └── test_v160_features.py
├── docs/
│ ├── architecture.md
│ └── release-process.md
└── .gitignoreRelease History
v0.1.0 — concept doc + skeleton server, all tools defined but not yet implemented (returns
NotImplementedError) ✅v0.2.0 — all 8 tools wired: read tools (list, status, events, snapshot) + write tools (privacy, light, pan, notifications) via sys.path injection (Option C) ✅
v0.4.0 — resources (
bosch://cameras,bosch://cameras/{name}/snapshot.jpg,bosch://cameras/{name}/events) + prompts (daily-camera-summary,pre-leave-check) ✅v0.5.0 — streamable-HTTP transport (
--transport http|sse|stdio), packaging forpipx/uvx, 24 new tests ✅v1.0.0 — first stable release: 106 tests, published wheel + sdist on GitHub Releases, PyPI publish pending ✅
v1.1.0 — LAN-only media path (privacy hardened):
bosch_camera_snapshotand newbosch_camera_stream_urlgo directly to camera over LAN, no Bosch cloud relay for media. 113 tests. ✅v1.2.0 —
bosch_camera_maintenance_statustool: fetches cloud maintenance announcements from community RSS feeds; returns state (active/scheduled/past/recent/unknown/idle), title, time window, link. ✅v1.3.0 — LAN-fallback feature set (ported from HA integration v12.4.10/v12.4.11):
bosch_camera_lan_pingtool (TCP-probe any camera on LAN);prefer_local=Trueonbosch_camera_privacy_set/bosch_camera_light_set(RCP-LAN write path, Gen2, cloud fallback on failure);recommended_actionfield onbosch_camera_maintenance_status("check_lan"when active,"wait"when scheduled). 173 tests. ✅v1.3.3 — audio get/set, intrusion detection get/set, WiFi info (cross-port from HA v12.7.0). 16 tools. ✅
v1.3.4 — PTZ named presets (
bosch_camera_pan preset=acceptshome / left / right / back-left / back-right); transparent cred-rotation on 401 for LAN-RCP tools (silent retry, no API change). ✅v1.3.6 — 9 bug fixes from live audit 2026-05-24 (camera list always live from cloud, Gen1/Gen2 hw_version, UUID resolution, events field mapping, audio camelCase, intrusion Gen2 gate, error codes, snapshot timestamp, requirements-test.txt mirror). ✅
v1.4.0 — 4 new tools:
bosch_camera_mjpeg_snapshot,bosch_camera_onvif_scopes,bosch_camera_rcp_version,bosch_camera_feature_flags._fetch_rcp_lanasync helper. 20 tools total. ✅v1.5.0 — 11 new tools + 8 bug fixes from live-camera audit (4 hardware units, all 4 generations): siren trigger, motion get/set, recording get/set, autofollow get/set, privacy-sound get/set, unread-count, health-check-all, token-status. ✅
v1.5.1 — fixed
_fetch_rcp_lan(used a non-existentaiohttp.DigestAuth→onvif_scopes/rcp_versionalways failed over LAN; nowhttpx.DigestAuth). Test coverage 83→98%, fixtures sanitized, CI bumped to Node-24-native action majors. ✅v1.5.2 — dependency hygiene: dropped unused
aiohttpruntime dep (test-only now), addedpyjwt>=2.13.0/starlette>=1.0.1security floors (pip-auditclean), fixed a test that mocked the wrong HTTP stack. ✅v1.5.3 — security patch: pin Bosch cloud CA for the MCP cloud session (CWE-295, GHSA-6qh5-x5m5-vj6v); closes adjacent-network MITM on OAuth tokens. Local TOFU pinning unchanged. ✅
v1.5.4 — event timestamps no longer drop the timezone offset:
/v11/eventsreturns offset-bearing timestamps (e.g.+02:00[Europe/Berlin]); the server now strips only the trailing[zone]suffix instead of truncating to 19 characters, preserving the explicit UTC offset. ✅v1.5.5 —
camera_eventsresource now useseventType + eventTagsfor correct event classification. ✅v1.6.0 — 2 new tools:
bosch_camera_audio_detection_get/bosch_camera_audio_detection_set— glass-break + smoke/fire-alarm sound detection for Gen2 Audio-Plus cameras (cross-port from HA integration v14.2.0). 34 tools total. ✅v1.7.0 — family-parity closeout (
docs/family-parity-plan.md§2b): 21 new tools closing the MCP-vs-HA/CLI capability gap — motion zones get/set/clear, privacy masks get/set/clear, automation rules list/add/edit/delete, camera sharing/friends list/invite/share/unshare/remove, firmware status/install (mirrors HA'sasync_install_firmwareguard), siren duration, LED lighting schedule get/set, and a listen-audio intercom tool (camera mic → caller, RTSPS URL; two-way talk is not exposed by Bosch's cloud API at all, same limitation as the sister CLI). CI hardening: coverage gate (--cov-fail-under=96),pip-audit(runtime deps only),pylint,codespell, CodeQL, gitleaks secret-scan, and a dependency-review workflow — Gold-tier parity with the HA integration's quality gates. 55 tools total. ✅
Releases
Latest: v1.7.0 — see the GitHub release page for full notes: v1.7.0 release notes →
All releases | GitHub Releases page — every tagged version with notes + downloadable assets |
Full history |
|
Integration Comparison
The Bosch Smart Home Camera reverse-engineered API is exposed via four sibling projects. Pick the one that fits your platform.
Feature | ||||||
Maturity | v15.0+ — HA Quality Scale Platinum | v10.12+ stable (Mini-NVR BETA) | v1.8+ stable · npm | v1.7+ stable · PyPI | v0.4.0 alpha · PyPI | v0.4.0 alpha · npm |
Platform | Home Assistant (HACS) | Standalone Python 3.10+ CLI | ioBroker (npm) | Python 3.10+ · pipx / uvx · stdio + streamable-HTTP for MCP clients (Claude Desktop, Claude Code, custom) | NiceGUI web app · Python 3.10+ | Node-RED palette · npm |
Login | OAuth2 PKCE (browser) | OAuth2 PKCE (browser) | OAuth2 PKCE (browser) | OAuth2 PKCE (browser, one-time) | ◑ shares CLI | ◑ refresh-token from CLI |
Snapshots | ✅ Native | ✅ | ✅ File-store + base64 DP | ✅ | ✅ live + event fallback | ✅ |
Live RTSP stream (LAN) | ✅ via HA Stream component | ✅ ffmpeg/RTSPS output | ✅ TLS proxy → local RTSP | ✅ | ◑ internal (go2rtc) | ◑ |
WebRTC (sub-second latency) | ✅ via integrated go2rtc | ✅ (v10.6.0) | ❌ | ❌ | ✅ via go2rtc (else snapshot) | ❌ |
Dual-stream URL (main + sub) | ✅ | ✅ | ✅ | ◑ | ❌ (sub-stream only) | ◑ URL only — no sub option |
External recorder (BlueIris, Frigate) | ✅ via go2rtc | ✅ stdout pipe | ✅ Digest-creds URL + LAN bind option | ✅ URL returned, hand off to ffmpeg / go2rtc downstream | ❌ | ◑ |
Privacy mode | ✅ switch entity | ✅ command | ✅ DP | ✅ | ✅ toggle | ✅ |
Front spotlight (Gen1/Gen2) | ✅ light entity | ✅ command | ✅ DP | ✅ | ❌ (Phase 2 stub) | ✅ |
RGB wallwasher (Gen2 Outdoor II) | ✅ light w/ RGB | ◑ on/off only — no RGB | ✅ color + brightness DPs | ❌ (on/off only — RGB not exposed) | ❌ | ◑ on/off + intensity only — no RGB (v0.3.0-alpha) |
Panic-alarm siren | ✅ button entity (Gen2 Indoor II) | ✅ command (Gen2 Indoor II only) | ✅ DP | ✅ | ✅ trigger + duration (Gen2 Indoor II only) | ❌ |
Firmware update | ✅ Update-Entity + Repairs fix-flow, install button (v14.4.10) | ✅ status + install (v10.11.0) | ✅ firmware states + install trigger, write-lock guard (v1.8.0) | ✅ status + install tools (v1.7.0) | ◑ read-only status display, no install action | ✅ status + install nodes (v0.4.0-alpha) |
Image rotation 180° | ✅ switch | ❌ | ✅ DP | ❌ | ❌ | ❌ |
Motion / person / audio events | ✅ FCM push + polling fallback | ◑ | ✅ FCM push + polling fallback | ✅ | ◑ pull-only events table | ✅ |
Motion edge-trigger state | ✅ | n/a | ✅ | n/a (request-response, no subscription) | ❌ | ❌ |
Auto-snapshot on motion | ✅ refreshes Camera entity | n/a | ✅ writes | n/a (no background loop) | ❌ | ❌ |
Synthetic motion trigger (external sensor) | ✅ service | n/a | ✅ DP | ❌ | ❌ | ❌ |
Motion zones / privacy masks | ✅ read + write | ✅ read + write | ✅ read + write (v1.8.0) | ✅ get / set / clear (v1.7.0) | ❌ (no visual editor yet) | ❌ |
Automation rules / schedules | ✅ read + write | ✅ read + write | ✅ full CRUD (v1.8.0) | ✅ list / add / edit / delete (v1.7.0) | ✅ full CRUD (list/add/edit/delete) | ❌ |
Lighting schedule | ✅ read (write via service, Gen1 Eyes Outdoor only) | ✅ read + write | ✅ read (Gen1-only, v1.2.0) | ✅ get / set (v1.7.0) | ✅ read + write (outdoor Eyes cameras) | ❌ |
Cloud clip download (history ~30 d) | ✅ via Media Browser | ❌ | ❌ (parked — no community request yet) | ❌ (intentionally not exposed — large payloads) | ❌ (use CLI) | ◑ |
Mini-NVR (local recording) | ✅ continuous + event-buffered, ring-buffer preroll (v11.2.0 BETA → v14.7.0 modes) | ◑ event-triggered segment muxing, no preroll ring (v10.7.0 BETA) | ❌ (delegates to external recorder via credential-free RTSP endpoint) | ❌ (no NVR concept) | ◑ continuous only, no event-buffered (v0.4.0-alpha) | ◑ continuous only via |
SMB / NAS clip upload | ✅ | ✅ (v10.7.0 BETA) | ❌ | ❌ | ❌ | ❌ |
Camera sharing (friends) | ✅ services (share / invite / list) | ✅ command | ✅ share / invite / remove (Gen2 only, v1.8.0) | ✅ list / invite / share / unshare / remove (v1.7.0) | ✅ list/invite/remove/share/unshare | ❌ |
Pan / tilt (360° Gen1) | ✅ services | ✅ command | ✅ | ✅ | ✅ slider wired to live API | ❌ |
Named pan presets (home / left / right / back-left / back-right) | ✅ opt-in select entity | ✅ | ✅ | ✅ | ❌ | ❌ |
Two-way audio / intercom | ❌ | ✅ command | ❌ | ◑ listen-only | ❌ | ❌ |
Webhook delivery on events | ✅ service + opt-in options | ✅ | ✅ via MQTT bridge | ❌ (request-response model) | ❌ | ❌ |
MQTT event bridge (motion / audio / person) | n/a (HA event bus native) | n/a (single-run) | ✅ admin-config | n/a | ❌ | ❌ |
Apple HomeKit (via HA Core bridge) | ✅ documented | n/a | n/a | n/a | n/a | n/a |
Snapshot scheduler / time-lapse | ✅ examples/ YAML | ✅ cron + ffmpeg examples | ✅ Blockly example | n/a | ❌ | ❌ |
Native dashboard card / widget | ✅ 2 Lovelace cards (single + grid) | n/a | ✅ 2 vis-2 widgets — BoschCamera + BoschOverview multi-cam | n/a | ✅ (is itself a web dashboard) | ❌ |
Picture-in-Picture survives backgrounded tab | ✅ | n/a (no UI) | ✅ own PiP + freeze-recovery, Web-Worker heartbeat (v1.7.2/v1.7.3) | n/a (no UI) | ✅ reconnect-timeout + freeze-recovery (v0.4.0-alpha) | n/a (no UI) |
Cloud-relay REMOTE fallback | ✅ auto-switch when LAN unreachable | ✅ remote mode | ❌ (LOCAL-only by design) | ❌ (media LAN-only; status/events via cloud) | ◑ inherits CLI | ◑ REMOTE opt (manual) |
Browser-based admin / config UI | ✅ HA Config Flow | n/a (CLI) | ✅ JSON-config tabs | n/a (LLM-mediated; config via CLI / MCP client) | ✅ Settings page | ◑ editor config node |
UI languages | EN · DE · FR · ES · IT · NL · PL · PT · RU · UK · ZH-Hans (v12.4.0) | EN · DE · FR · ES · IT · NL · PL · PT · RU · UK · ZH-Hans (v10.3.0) | EN · DE · FR · ES · IT · NL · PL · PT · RU · UK · ZH-CN | n/a (no UI — LLM is the front-end) | ◑ backend i18n · UI mostly EN | n/a (English only) |
Legend: ✅ supported · ❌ not supported / not planned · n/a not applicable for this platform.
All four projects share the same reverse-engineered Cloud API + RCP protocol research, but evolve independently. The Home Assistant integration is the most feature-complete reference implementation; the Python CLI is the lowest-level / scriptable surface; the ioBroker adapter targets VIS dashboards and Blockly automations; the MCP server exposes a curated, LAN-first tool surface to MCP clients (Claude Desktop, Claude Code, custom) for natural-language camera control.
Related Projects
Part of a five-implementation family for Bosch Smart Home Cameras (plus an alpha frontend):
Implementation | Repo | Status |
🏆 Home Assistant Integration | v14.4.1 · HA Quality Scale Platinum · production-ready | |
🐍 Python CLI | v10.10.4 · Mini-NVR + SMB upload (BETA) · LAN-fallback (ping / --local) · PTZ presets · webhook delivery · capture / research / standalone | |
🟢 ioBroker Adapter | v1.7.7 · stable · npm · privacy-toggle Digest rotation · MQTT bridge · PTZ presets · VIS-2 widgets (BoschCamera + BoschOverview) | |
🤖 MCP Server (this repo) | v1.7.0 · cred-rotation · PTZ presets · TOFU cert pinning · cloud CA pinned (CWE-295) · LAN-ping + prefer_local · zones/masks/rules/friends/firmware-install · Claude Code / Claude Desktop integration | |
🔴 Node-RED nodes (alpha) | v0.2.5-alpha · 4 nodes (event / snapshot / privacy / config) |
Also: Bosch Smart Home Camera — Python Frontend (NiceGUI) — v0.1.5-alpha (dashboard + camera detail + settings) — community interest welcome
HA stays the reference implementation — features land there first; the Python CLI, ioBroker Adapter and MCP Server catch up over time.
License
MIT — see LICENSE.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
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/mosandlt/Bosch-Smart-Home-Camera-Tool-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server