Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
IP cameras (ONVIF/RTSP) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
4
downloads a day
local
runs on your machine
77
downloads in 30d
What it does
MCP server for local IP cameras (ONVIF/RTSP): snapshots, recordings, pan/tilt, presets
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user ip-cameras-onvif-rtsp-mcp '--' uvx ipcam-mcp
# 2 — ask your agent for something these tools do
# list_cameras, camera_snapshot, camera_save_baseline and 17 more
IP cameras (ONVIF/RTSP) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AIAll 1 server
aidev-iprokszin1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts IP cameras (ONVIF/RTSP) as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user ip-cameras-onvif-rtsp-mcp '--' uvx ipcam-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take IPCAM_MCP_CONFIG (Path to cameras.toml (default: ~/.config/ipcam-mcp/cameras.toml)) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
20 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List configured cameras with their ids (names), uids, types and capabilities (camera, ptz). include_removed=true also lists removed cameras whose files are still on disk ("removed": true), e.g. to clean them up with delete_camera.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_removed | boolean | no | — |
Take a still picture from a camera. Returns the image (downscaled to at most 1280 px wide) and the path of the full-size JPEG saved on the local machine.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| camera | string | no | — |
| quality | no | — | |
| crop | array | no | — |
| region | no | — | |
| from_path | string | no | — |
Take a snapshot and keep it as a named reference for camera_compare (e.g.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| camera | string | yes | — |
| name | string | yes | — |
| quality | no | — |
Take a new snapshot and report what changed compared with this camera's previous snapshot in its current scene, or with a named baseline saved in that scene. Use the reported cells as region in camera_snapshot to look closer.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| camera | string | yes | — |
| baseline | string | no | — |
| quality | no | — |
Record a video clip (1-60 s) from a camera to an mp4 file on the local machine.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| camera | string | yes | — |
| seconds | integer | no | — |
| quality | no | — |
Pan or tilt a camera. Directions are as seen in the camera image ("left" turns the view left). amount: "small" is a slight nudge, "medium" a noticeable turn, "large" a big sweep. Waits until the camera has stopped, then returns its pan/tilt position if the camera reports one. Take a snapshot…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| camera | string | yes | — |
| direction | yes | — | |
| amount | no | — |
List the saved camera positions (presets) of a pan/tilt camera.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| camera | string | yes | — |
Move a pan/tilt camera to a saved preset, given by name or token.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| camera | string | yes | — |
| preset | string | yes | — |
Save the camera's current position as a preset. Refuses an existing name unless overwrite=true.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| camera | string | yes | — |
| name | string | yes | — |
| overwrite | boolean | no | — |
Delete a saved preset by name or token. This cannot be undone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| camera | string | yes | — |
| preset | string | yes | — |
Re-read cameras.toml after it was edited by hand and list the cameras, in the same format as list_cameras.
Takes no parameters.
Add an ONVIF/RTSP IP camera. Ask the user for the camera's IP address (from its app or router) and pick a short name such as "garage".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| host | string | yes | — |
| credentials_via | string | no | — |
| onvif_port | integer | no | — |
| scene | string | no | — |
Change a camera's name. Its baselines, snapshots and recordings stay with it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| old | string | yes | — |
| new | string | yes | — |
Move a camera to another scene (the place it watches). Its earlier snapshots stay with the earlier scene; camera_compare only compares within the current scene.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| camera | string | yes | — |
| scene | string | yes | — |
Remove a camera from the configuration. Never deletes snapshots or recordings (delete_camera does, after the user approves).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
Delete a camera and all its snapshots, recordings and baselines, or the leftover files of a removed camera with that name. The user approves in a form that lists what will be deleted; you cannot approve it. Without form support nothing is deleted and the result says how to do it by hand.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install IP cameras (ONVIF/RTSP) or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 0.4.1 · scanned 6 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digestf1f48d8b29d231736b5b671855c1957ddff5ccb90a7f77c9569a0198a0ec7592
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (20 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
9 of the 20 recovered tools are registered only when manager is not None and allow_management is false (src/ipcam_mcp/server.py:197) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 6.
5 of the 20 recovered tools are registered only when not allow_management is false (src/ipcam_mcp/server.py:465) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 6.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
6 tools are registered unconditionally · (1) 9 more only when manager is not None and allow_management is false (src/ipcam_mcp/server.py:197) · (2) 5 more only when not allow_management is false (src/ipcam_mcp/server.py:465) — typically when a key or option is configured. All 20 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_scenes | no tags | |
| scene_snapshot | no tags | |
| scene_compare | no tags | |
| scene_timeline | no tags | |
| list_cameras | no tags | |
| camera_snapshot conditional (1) | no tags | |
| camera_save_baseline conditional (1) | no tags | |
| camera_compare conditional (1) | no tags | |
| camera_record conditional (1) | no tags | |
| ptz_move conditional (1) | no tags | |
| ptz_list_presets conditional (1) | no tags | |
| ptz_goto_preset conditional (1) | no tags | |
| ptz_save_preset conditional (1) | no tags | |
| ptz_remove_preset conditional (1) | no tags | |
| reload_cameras | no tags | |
| add_camera conditional (2) | no tags | |
| rename_camera conditional (2) | no tags | |
| set_scene conditional (2) | no tags | |
| remove_camera conditional (2) | no tags | |
| delete_camera conditional (2) | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestf1f48d8b29d23173
Scanned2026-11-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.4.1. Pin a release below and the command asks for exactly that one.
0.4.1
6 Nov 2026
latestNo release note was published with this version.
0.4.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish IP cameras (ONVIF/RTSP) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.