camsentry-mcp 0.2.0

Quick start · What it does · Tools · Alerts · Notifications · Settings · Security · Limitations

camsentry-mcp is an unofficial MCP server that gives a local model eyes on Wyze cameras. A small vision model on your own machine looks at every still your cameras record, remembers what it saw, and tells you when something matters, by push notification, email or text:

Person seen at Front Door: A courier in a blue uniform places a box on the step. (10:42 AM)

Someone is lingering at Back Door: A person has been in view for about 7 minutes. A man stands by the gate. (11:16 PM)

Your chat model can ask it anything: "what happened out back today?", "find the white van", "tell me if the gate is left open".

Quick start

You need: Python 3.12 – 3.14, a Wyze account, and Ollama. Nothing else: no Docker, no GPU libraries, no accounts with anyone but Wyze.

pipx install git+https://github.com/14manj01/camsentry-mcp   # or: uv tool install git+https://...
ollama pull qwen2.5vl:3b                                      # the 3 GB vision model that looks at the stills
camsentry-mcp setup                                           # sign in to Wyze, choose how to be notified

setup asks for your Wyze email, password and a free API key, exchanges them for session tokens kept in the OS keychain, and discards the password and key. It then prints the block to paste into your chat app's MCP settings (LM Studio, Jan, Open WebUI via mcpo, ollmcp, …). There is nothing secret in it and nothing to configure:

{
  "mcpServers": {
    "camsentry": { "command": "camsentry-mcp" }
  }
}

{
  "mcp": {
    "camsentry": { "type": "local", "command": ["camsentry-mcp"], "enabled": true }
  }
}

That is all. While the chat app runs, the cameras are watched and alerts reach you. To keep watching when it is closed, run camsentry-mcp autostart on: the watcher then starts in the background each time you log in (autostart off undoes it). camsentry-mcp watch runs it in a terminal instead.

What it does

How it compares with what smart-camera services advertise:

flowchart LR
    subgraph PC[Your computer]
        M[Chat app + your model] -- MCP --> S[camsentry-mcp]
        S <--> V[Vision model in Ollama]
        S <--> D[(Memory: what each still showed)]
    end
    S -- session tokens from OS keychain --> W[Wyze cloud: events + stills]
    S -- alert text --> N[ntfy / email / text / webhook] --> P[Your phone]

Tools

What your chat model can call. It does not need vision: everything comes back as text.

If a model changes what you are alerted about (set_armed, set_camera_alerts, remove_watch_rule), your phone is told, so alerts cannot be quietly switched off.

{
  "event_id": "…",
  "camera": "Front Door",
  "time": "2026-03-01T23:41:07-06:00",
  "armed": true,
  "detection": {"people": 1, "pets": [], "vehicles": 0, "packages": 1, "suspicious": false, "suspicious_reason": "", "summary": "A courier places a box on the porch."},
  "alerts": [
    {"type": "intruder", "reason": "person detected while armed", "priority": "urgent"},
    {"type": "person", "reason": "1 visible", "priority": "normal"},
    {"type": "package", "reason": "1 visible", "priority": "normal"}
  ],
  "new_alerts": ["intruder", "person", "package"],
  "changes": ["person arrived", "package appeared"]
}

Alerts

An alert is sent when it becomes true, not for every still in which it stays true: a parcel sitting on the porch all afternoon is one message. Wyze's own tags (Cam Plus) raise the same alerts when present.

Notifications

Chosen in camsentry-mcp setup, changed with camsentry-mcp notify …. Destinations live in the OS keychain.

camsentry-mcp notify test sends a test; camsentry-mcp notify off removes every destination.

An email address alone is not enough to be notified: something has to send the mail, and the free services that used to send to any address (ntfy.sh's email, Textbelt's free texts) have closed that door because of abuse. So email goes out through a mailbox you already own. Images are never sent anywhere.

Settings

Nothing has to be set. These environment variables exist for when you want something different.

Commands: setup, status, watch, autostart on|off, notify ntfy|text|email|sms|webhook|test|off, login, logout, forget (deletes the remembered history), and no command at all to run the MCP server.

Watching uses your GPU each time a camera records something. If you also run a large chat model on the same GPU, the two take turns and both get slower.

Security

• 🔐 Your Wyze password and API key are typed once and discarded. Session tokens, your phone number, push topic and mailbox app password live in the OS keychain.
• 🖼️ Camera images go to the vision endpoint only. It must be on this machine unless you opt in.
• 👀 Read-only towards Wyze: no tool can switch a camera off, unlock anything or change a Wyze setting.
• 🧱 Tools take camera names and event ids, never URLs or file paths. A model can text only you.
• 🧹 Error messages and logs are scrubbed of tokens, pre-signed image URLs, phone numbers and push topics.
• 🗂️ What the cameras saw is remembered as text for 30 days in a local database; camsentry-mcp forget erases it.

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

Limitations

• Stills, not video. One 640×360 image per event, as fast as Wyze uploads it. Without Cam Plus, Wyze spaces events on a camera several minutes apart, so "lingering" means "seen in consecutive stills".
• Not instant. New stills are fetched every 60 seconds and take about a second each to analyse.
• A camera with no events has nothing to analyse. If a camera shows nothing in the Wyze app's Events tab, it shows nothing here.
• Accuracy is that of a small model. See docs/ACCURACY.md. Watch rules in particular can call a false statement true.
• No faces, no live view, no device control.
• 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.

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

_{Not affiliated with, endorsed by or sponsored by Wyze Labs, Inc. Wyze is a trademark of Wyze Labs, Inc.
Released under the MIT license.}