camsentry-mcp

camsentry-mcp is an unofficial MCP server that gives a local model eyes on Wyze cameras. Ask it "is there a package at the front door?" or "arm the cameras and tell me if anyone shows up", and it answers from what your cameras actually recorded.

Why this one

Related MCP server: DesktopBridge

How it works

flowchart LR
    M[Local model + MCP client] -- stdio --> S[camsentry-mcp]
    S -- session tokens from OS keychain --> W[Wyze cloud: cameras, events, event images]
    S -- frame --> V[Local vision model, 127.0.0.1]
    S -. optional live frame .-> B[wyze-bridge on your LAN]

Quick start

You need: Python 3.12 – 3.14, a Wyze account, Ollama (or another local model server), and an OS keychain (Windows Credential Manager, macOS Keychain, or GNOME Keyring / KWallet on Linux).

1. Install

pipx install git+https://github.com/14manj01/camsentry-mcp
# or: uv tool install git+https://github.com/14manj01/camsentry-mcp

2. Get a small vision model

ollama pull gemma3:4b

It analyses a frame in about a second on a GPU that fits it.

3. Connect your Wyze account

Create a free API key at https://developer-api-console.wyze.com/#/apikey/view, then:

camsentry-mcp login

You are asked for your Wyze email, password, API Key ID and API Key (and a 2FA code if your account uses one). They are exchanged for session tokens, the tokens are saved to the OS keychain, and the password and API key are discarded.

camsentry-mcp status    # checks the Wyze session, the vision model and your settings
camsentry-mcp logout    # revokes the session with Wyze and deletes the tokens

4. Add it to your MCP client

Any MCP client that launches stdio servers works (LM Studio, Jan, Open WebUI via mcpo, ollmcp, …). There are no secrets in this block, so it is safe to share or commit:

{
  "mcpServers": {
    "camsentry": {
      "command": "camsentry-mcp",
      "env": {
        "CAMSENTRY_VISION_MODEL": "gemma3:4b",
        "CAMSENTRY_ARMED_HOURS": "22:00-06:00"
      }
    }
  }
}

5. Ask

Check my cameras.

Is there a package at the front door?

Arm the cameras and tell me if anyone shows up.

Tools

{
  "camera": "Front Door",
  "source": "event",
  "time": "2026-03-01T23:41:07-06:00",
  "wyze_tags": ["Person"],
  "armed": true,
  "detection": {"people": 1, "pets": [], "packages": 1, "suspicious": false, "suspicious_reason": "", "summary": "A courier places a box on the porch."},
  "alerts": [
    {"type": "person", "reason": "1 visible; tagged by Wyze"},
    {"type": "package", "reason": "1 visible"},
    {"type": "intruder", "reason": "person detected while armed"}
  ]
}

How alerts are decided

Wyze's own tags need Cam Plus; the local model does not.

Settings

All optional, all non-secret environment variables.

Out of the box the server sees what the Wyze app's Events tab sees: a still image per motion event. Without Cam Plus, Wyze limits how often cameras record events.

For a frame from right now, run a wyze-bridge on your network and set CAMSENTRY_BRIDGE_URL. analyze_camera and view_camera then use a live snapshot when no event_id is given. If the bridge has BRIDGE_AUTH enabled, store its credentials in the keychain with camsentry-mcp bridge-auth.

Security

• 🖼️ Camera frames go to the vision endpoint only. It must be a loopback address unless you opt in.

• 🧱 Tools take camera names and event ids, never URLs or file paths.

• 🧹 Error messages and logs are scrubbed of tokens, pre-signed image URLs and raw Wyze responses.

• 🔎 This repository runs secret scanning (gitleaks) on every push and pull request.

The full threat model, including what a manipulated model can and cannot do, is in SECURITY.md.

Limitations

• Wyze has no official public API. This project uses the community wyze-sdk, which can break when Wyze changes their service.

• Wyze's Terms of Service restrict third-party applications that interact with their service. Using this project with your account may breach those terms, and Wyze could suspend the account. That risk is yours to weigh.

• watch_cameras is a poll, not a push: the model (or your client's scheduler) has to call it.

• set_armed and the "already reported" memory of watch_cameras reset when the server restarts.

Development

git clone https://github.com/14manj01/camsentry-mcp
cd camsentry-mcp
python -m venv .venv
.venv/bin/pip install -e ".[dev]"      # Windows: .venv\Scripts\pip
.venv/bin/pytest