Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

IP cameras (ONVIF/RTSP)

by aidev-iprokszinversion 0.5.1i★ 3iRuns on your computerRepository ↗
Registry nameio.github.aidev-iprokszin/ipcam-mcp

How to install

What it does

MCP server for local IP cameras (ONVIF/RTSP): snapshots, recordings, pan/tilt, presets

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity20/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score32/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install IP cameras (ONVIF/RTSP). Follow https://mcp.popnx.com/i/aidev-iprokszin-ipcam-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server IP cameras (ONVIF/RTSP) for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "ipcam": { "command": "uvx", "args": [ "ipcam-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the IP cameras (ONVIF/RTSP) tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "ipcam": {
          "command": "uvx",
          "args": [
            "ipcam-mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use IP cameras (ONVIF/RTSP) and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using IP cameras (ONVIF/RTSP) or shows a IP cameras (ONVIF/RTSP) tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • IPCAM_MCP_CONFIG Path to cameras.toml (default: ~/.config/ipcam-mcp/cameras.toml)

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect IP cameras (ONVIF/RTSP) yet

IP cameras (ONVIF/RTSP) runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect IP cameras (ONVIF/RTSP)

  • Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server IP cameras (ONVIF/RTSP) for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user ipcam -- uvx ipcam-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the IP cameras (ONVIF/RTSP) tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user ipcam -- uvx ipcam-mcp
  4. Type /mcp in Claude Code

    You should see IP cameras (ONVIF/RTSP) listed as connected

  5. Try it

    Use IP cameras (ONVIF/RTSP) and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using IP cameras (ONVIF/RTSP) or shows a IP cameras (ONVIF/RTSP) tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • IPCAM_MCP_CONFIG Path to cameras.toml (default: ~/.config/ipcam-mcp/cameras.toml)

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server IP cameras (ONVIF/RTSP) for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "ipcam": { "command": "uvx", "args": [ "ipcam-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the IP cameras (ONVIF/RTSP) tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use IP cameras (ONVIF/RTSP) and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using IP cameras (ONVIF/RTSP) or shows a IP cameras (ONVIF/RTSP) tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • IPCAM_MCP_CONFIG Path to cameras.toml (default: ~/.config/ipcam-mcp/cameras.toml)

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server IP cameras (ONVIF/RTSP) for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "ipcam": { "type": "stdio", "command": "uvx", "args": [ "ipcam-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the IP cameras (ONVIF/RTSP) tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use IP cameras (ONVIF/RTSP) and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using IP cameras (ONVIF/RTSP) or shows a IP cameras (ONVIF/RTSP) tool in the answer, you are connected

1 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • IPCAM_MCP_CONFIG Path to cameras.toml (default: ~/.config/ipcam-mcp/cameras.toml)

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use IP cameras (ONVIF/RTSP)💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user ipcam -- uvx ipcam-mcp

Claude Desktop (claude_desktop_config.json)

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

Cursor (~/.cursor/mcp.json)

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

VS Code (mcp.json)

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

Values you fill in

  • IPCAM_MCP_CONFIG env
    Path to cameras.toml (default: ~/.config/ipcam-mcp/cameras.toml)

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
585/wk
Connection
Runs on your computer
Latest versioni
0.5.1
Categoryi
Other
Published to registryi
Nov 9, 2026
Code last changedi
Nov 17, 2026
Maker
aidev-iprokszin
Packages
pypi: ipcam-mcp
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account aidev-iprokszin, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for ipcam-mcp@0.5.1

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/aidev-iprokszin-ipcam-mcp.svg)](https://mcp.popnx.com/en/servers/aidev-iprokszin-ipcam-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 93% of the other 20653 servers in this category
  • Published to the registry more recently than 82% of the other 20653 servers in this category
  • Basic checks equal to or better than 99% of the other 20653 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is IP cameras (ONVIF/RTSP) safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 2 days ago, and the latest version (0.5.1) reached the registry 10 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
IP cameras (ONVIF/RTSP)
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

ipcam-mcp

An MCP server that lets Claude Code, or another MCP client, see through and control the IP cameras on your local network (ONVIF + RTSP): snapshots, video clips, pan/tilt and change detection, all handled locally.

Any ONVIF camera should work. See known cameras for what has been tested.

What you can ask

Once a camera is added, ask in plain words, for example:

  • "Take a snapshot of the front door."
  • "Save this view as door-closed." Later: "Does the front door still look like door-closed?"
  • "Did anything change at the front door since the last snapshot?"
  • "Pan the office camera a bit to the left."
  • "Record 10 seconds from the garage."
  • "Show me what the garage cameras captured yesterday."

Prerequisites

  • Linux or WSL2, on the same network as the camera
  • uv on your PATH (it installs Python 3.13+ and the dependencies for you)
  • ffmpeg: sudo apt install ffmpeg
  • An ONVIF-capable IP camera with a local camera account (username and password), with ONVIF and RTSP enabled
  • Claude Code or another MCP client that supports stdio servers

Install

Pick one. All of them run the ipcam-mcp package from PyPI and need ffmpeg and, except pipx, uv (see Prerequisites).

  • Claude Code plugin (recommended for Claude Code): /plugin install ipcam --marketplace aidev-iprokszin/ipcam-mcp

On Claude Code older than 2.1.275, run /plugin marketplace add aidev-iprokszin/ipcam-mcp, then /plugin install ipcam@ipcam-mcp. The plugin runs the server from a lockfile (every dependency pinned with hashes). Update it with claude plugin update ipcam@ipcam-mcp, which also updates the server; a new server version reaches the plugin shortly after its PyPI release.

  • Claude Code, without the plugin: claude mcp add ipcam -s user -- uvx ipcam-mcp
  • Other MCP clients (Cursor, VS Code, Codex CLI, …): configure the stdio command uvx ipcam-mcp. See Other MCP clients.
  • A permanent `ipcam-mcp` command: uv tool install ipcam-mcp (or pipx install ipcam-mcp), then configure your client to run ipcam-mcp. Update with uv tool upgrade ipcam-mcp (or pipx upgrade ipcam-mcp).

Then add your first camera.

Add your first camera

  1. Camera account: create or find the camera's local ONVIF/RTSP account (username and password). This is not your cloud login. See known cameras for where your brand hides it.
  2. IP address: look it up in the camera's app or your router. Network discovery is not supported (WSL2 NAT blocks it).
  3. Ask Claude to add it, for example "add my camera at 192.0.2.10 as front-door". Claude calls add_camera, which asks for the username and password in a login form, so they never pass through the model. Before you type the password, check that the IP in the form is your camera's. Without a config file the server starts with no cameras; add_camera creates cameras.toml and the camera's secrets file. See Managing cameras for the other management tools and for clients that cannot show forms.
Or configure it by hand
  1. Secrets file (outside any repo), e.g. ~/.config/ipcam-mcp/secrets.env:
   CAMERA_IP=192.168.x.y

CAMERA_USER=... CAMERA_PASSWORD=...

   The host is a bare IP address or hostname: no `rtsp://`, user name, port or path (ports go

in Camera settings). Make it readable only by you: chmod 600 . The server warns at startup if other users can read it.

  1. Camera config: copy cameras.example.toml to ~/.config/ipcam-mcp/cameras.toml (or point IPCAM_MCP_CONFIG at another path) and adjust the camera name / variable names. Only variable *names* go in this file, never the secrets themselves. Use type = "onvif".

After editing cameras.toml by hand while the server runs, ask Claude to reload the cameras (reload_cameras).

Camera settings

All optional, set in the camera's section of cameras.toml. A wrong type is reported when the config loads.

SettingTypeDefault
onvif_portinteger 1–6553580
rtsp_portinteger 1–65535the port in the camera's stream URI, else 554 (a value you set always wins)
invert_panbooleanfalse
ptzbooleanfalse
stream_highpath starting with /looked up over ONVIF
stream_lowpath starting with /looked up over ONVIF

ptz = false means the camera has no pan/tilt tools. Set stream_high/stream_low if the ONVIF lookup fails or picks the wrong stream. Set invert_pan = true if ptz_move left turns the view to the right. Some brands need other values; see known cameras.

Other MCP clients

Any client that supports stdio servers (Cursor, VS Code, Codex CLI, …) can run the same command: uvx ipcam-mcp, or uv --directory /absolute/path/to/ipcam-mcp run ipcam-mcp for a clone.

Claude Desktop on Windows: the server runs inside WSL2, so install uv and ffmpeg there (see *Prerequisites*). In Claude Desktop, open *Settings → Developer → Edit Config*, add the ipcam entry below to mcpServers and keep the rest of the file:

{

"mcpServers": { "ipcam": { "command": "wsl.exe", "args": ["-e", "/home/ /.local/bin/uvx", "ipcam-mcp"] } } }

Replace `<you>` with your WSL user name (`which uvx` in WSL shows the path). With several WSL

distributions, add "-d", " " before "-e". Then quit Claude Desktop from the tray icon (closing the window is not enough) and start it again. The server uses the same cameras.toml and media folder inside WSL as Claude Code there. Use *Edit Config* rather than a fixed path: the Microsoft Store version keeps the file under %LOCALAPPDATA%, not %APPDATA%\Claude. For a clone, use "args": ["-e", "/home/ /.local/bin/uv", "--directory", "/home/ /path/to/ipcam-mcp", "run", "ipcam-mcp"].

WSL2 networking

If the camera can't be reached from WSL (nc -zv 554 fails), enable mirrored networking in %UserProfile%\.wslconfig:

[wsl2]

networkingMode=mirrored

then run `wsl --shutdown` from Windows.

Tools

ToolWhat it does
list_cameras(include_removed=False)Configured cameras with their uid, scene and capabilities (camera, ptz); include_removed=true also lists removed cameras whose files are still on disk
camera_snapshot(camera=None, quality="high", crop=None, region=None, from_path=None)Returns the picture (≤1280 px wide) and saves the full-size JPEG. crop=[x, y, w, h] (fractions 0–1) or region (top-left, top, top-right, left, center, right, bottom-left, bottom, bottom-right) returns a detail at full resolution. from_path reuses an earlier snapshot (for example one from scene_timeline) without contacting a camera; camera is then optional
camera_save_baseline(camera, name, quality="high")Takes a snapshot and keeps it as a named reference (e.g. door-closed)
camera_compare(camera, baseline=None, quality="high")Takes a snapshot and reports what changed against the camera's previous snapshot in its current scene, or against a named baseline saved in that scene
camera_record(camera, seconds=10, quality="high")Records 1–60 s to an mp4, returns its path
ptz_move(camera, direction, amount="small")Pan/tilt left/right/up/down by small/medium/large; waits for the move to finish and returns the final position if the camera reports one
ptz_list_presets(camera)Saved positions
ptz_goto_preset(camera, preset)Move to a preset by name or token
ptz_save_preset(camera, name, overwrite=False)Saves the current position as a preset; refuses an existing name unless overwrite=true
ptz_remove_preset(camera, preset)Deletes a preset by name or token (cannot be undone)
list_scenes()Every scene with its cameras, removed cameras that watched it, the first and last capture and counts
scene_snapshot(scene, quality="high")A snapshot from every camera in the scene, each labelled with the camera's name; a camera that fails reports its error without failing the others; the call fails only if every camera does
scene_compare(scene, baseline=None, quality="high")camera_compare for every camera in the scene, labelled the same way
scene_record(scene, seconds=10, quality="high")Records 1–60 s with every camera in the scene at the same time, labelled the same way; returns each clip's path and size. Combining the clips (split screen etc.) is up to you
scene_timeline(scene, start=None, end=None, limit=50)The scene's snapshots, recordings and baselines, newest first, from every camera that watched it (removed ones too). start/end: YYYY-MM-DD (whole day) or an ISO datetime; limit 1–500

camera is a camera's name: its section name in cameras.toml. quality="high" uses the camera's main stream (its resolution is set on the camera), "low" the sub stream (smaller, quicker). Media is saved to the camera's own folder, / / _ .jpg|.mp4 (media_dir defaults to ~/.local/share/ipcam-mcp/media).

Tool hints. Every tool carries MCP annotations so clients can tell what it does: list_cameras, list_scenes, scene_timeline and ptz_list_presets are read-only; camera_save_baseline, ptz_save_preset, ptz_remove_preset, remove_camera and delete_camera may replace or delete data; everything else only adds files or moves the camera. Snapshots and recordings are not marked read-only because they save files. These are hints for the client; the server's own safeguards (such as delete_camera's approval form) still apply.

Compare and crop. camera_compare lists the grid cells that changed (the same names as region) and a box around them. It compares the frames at the size the camera sends them, so the stream resolution you set on the camera decides how small a change it can notice; a reference of another size is scaled to the new frame. Pass a changed cell as region to camera_snapshot, ideally with from_path set to the snapshot you just looked at, to see it closer. Baselines live in / /baselines/ as a JPEG plus a small JSON file.

Managing cameras

Instead of editing cameras.toml by hand you can let Claude add, rename, remove and delete cameras. This is on by default. To turn it off, set allow_management = false in cameras.toml (see cameras.example.toml), then run /mcp reconnect ipcam; the flag is only read at startup. Claude Code still asks before each tool call unless you allowlist it; if you allowlist the camera tools, consider leaving remove_camera, delete_camera and ptz_remove_preset off the list.

add_camera logs into whatever host it is given. Before you type a password into the login form, check that the IP it shows is your camera's (from the camera's app or your router), not one the agent picked up elsewhere.

ToolWhat it does

| `add_camera(name, host, credentials_via="form", onvif_port=None, scene=No

Only the beginning is shown; read the rest in the repo