World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Control a USB (UVC) pan/tilt/zoom camera, with every move confirmed from the picture.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 7/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install UVC PTZ Camera. Follow https://mcp.popnx.com/i/abhijatsaxena-uvc-ptz-camera-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
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 UVC PTZ Camera 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": { "uvc-ptz-camera": { "command": "uvx", "args": [ "uvc-ptz-camera-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 UVC PTZ Camera 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.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: 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
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
SettingsDeveloperEdit Config
{
"mcpServers": {
"uvc-ptz-camera": {
"command": "uvx",
"args": [
"uvc-ptz-camera-mcp"
]
}
}
}Use UVC PTZ Camera and tell me what you can do for me, then show me one thing✓ If Claude says it is using UVC PTZ Camera or shows a UVC PTZ Camera tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
UVC_PTZ_STATE_DIR Where to store what has been learned about each camera. Defaults to ~/.uvc-ptz-camera-mcp. Holds angles, never credentials.UVC_PTZ_SIM_SOURCE Path to an image to use as the simulator's panorama instead of the synthesised one.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 UVC PTZ Camera yet
UVC PTZ Camera runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect UVC PTZ Camera
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)
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 UVC PTZ Camera 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 uvc-ptz-camera -- uvx uvc-ptz-camera-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 UVC PTZ Camera 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.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: 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
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
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user uvc-ptz-camera -- uvx uvc-ptz-camera-mcpYou should see UVC PTZ Camera listed as connected
Use UVC PTZ Camera and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using UVC PTZ Camera or shows a UVC PTZ Camera tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
UVC_PTZ_STATE_DIR Where to store what has been learned about each camera. Defaults to ~/.uvc-ptz-camera-mcp. Holds angles, never credentials.UVC_PTZ_SIM_SOURCE Path to an image to use as the simulator's panorama instead of the synthesised one.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)
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 UVC PTZ Camera 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": { "uvc-ptz-camera": { "command": "uvx", "args": [ "uvc-ptz-camera-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 UVC PTZ Camera 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.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: 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
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
Use UVC PTZ Camera and tell me what you can do for me, then show me one thing✓ If Cursor says it is using UVC PTZ Camera or shows a UVC PTZ Camera tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
UVC_PTZ_STATE_DIR Where to store what has been learned about each camera. Defaults to ~/.uvc-ptz-camera-mcp. Holds angles, never credentials.UVC_PTZ_SIM_SOURCE Path to an image to use as the simulator's panorama instead of the synthesised one.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)
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 UVC PTZ Camera 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": { "uvc-ptz-camera": { "type": "stdio", "command": "uvx", "args": [ "uvc-ptz-camera-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 UVC PTZ Camera 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.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: 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
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
Use UVC PTZ Camera and tell me what you can do for me, then show me one thing✓ If VS Code says it is using UVC PTZ Camera or shows a UVC PTZ Camera tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
UVC_PTZ_STATE_DIR Where to store what has been learned about each camera. Defaults to ~/.uvc-ptz-camera-mcp. Holds angles, never credentials.UVC_PTZ_SIM_SOURCE Path to an image to use as the simulator's panorama instead of the synthesised one.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
Claude Code
claude mcp add --scope user uvc-ptz-camera -- uvx uvc-ptz-camera-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"uvc-ptz-camera": {
"command": "uvx",
"args": [
"uvc-ptz-camera-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"uvc-ptz-camera": {
"command": "uvx",
"args": [
"uvc-ptz-camera-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"uvc-ptz-camera": {
"type": "stdio",
"command": "uvx",
"args": [
"uvc-ptz-camera-mcp"
]
}
}
}UVC_PTZ_STATE_DIR envUVC_PTZ_SIM_SOURCE envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
pypi: uvc-ptz-camera-mcpBased 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
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account AbhijatSaxena, which owns the repo
Code last changed 42 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for uvc-ptz-camera-mcp@0.2.0
Checks only this package version, not every dependency · checked Nov 16, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/abhijatsaxena-uvc-ptz-camera-mcp)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.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed 42 days ago, and the latest version (0.2.0) reached the registry 42 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
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
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one UVC PTZ Camera | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
An MCP server for USB (UVC) pan/tilt/zoom cameras: aim them, nudge them, sweep them smoothly, zoom, and look through them — with every move confirmed by comparing the picture before and after.
No account, no cloud, no vendor SDK. One device, one USB cable.
camera_status the camera, its axes and ranges, and whether it is real
aim point an axis at an absolute value, confirmed from the picture nudge move relative to where the device says it is sweep a smooth timed move, streamed at 15 Hz zoom set zoom as a multiplier (1x .. the camera's maximum) recentre every axis back to its default look one frame, returned as an image aim_learn remember "this direction is the desk" aim_list what has been recorded for this camera go_to point at a recorded direction plan_shot compile a multi-step shot and report what it would do, moving nothing run_shot execute a multi-step move, verified after every waypoint mark_view store the current picture under a label check_view has the picture changed since that label? track_start follow a subject: detect, measure, take a step, look again track_status what the follow loop is doing, iteration by iteration track_stop stop following and report what it saw and what it moved
Composing a shot is plan_shot then run_shot. Planning compiles exactly the steps the executor will compile, reports the per-step schedule, how far each axis travels and how long it takes, and touches nothing — so an agent can iterate on "a panorama, then zoom in on me" against the camera's real ranges *before* anything moves, instead of finding out afterwards.
track_start runs a loop that keeps the camera pointed at a subject: detect it, measure how far it is from the centre of the frame, take a bounded step, look again. It decides only from the picture, for the same reason every other move here does — this camera's own report of where it is pointing cannot be trusted. It stops on its own when the subject is lost, when it settles inside the dead zone, when the camera stops answering, or after max_seconds, and track_status lists every iteration with the offset it measured and the step it applied.
Two quantities are *mount*-dependent rather than device-dependent, so they are explicit parameters instead of clever guesses: gain, degrees of movement per pixel of offset, and invert, which flips the direction. A wrong choice shows up honestly as a residual error that grows, and a single iteration is capped at 25 degrees, so a wrong gain converges slowly rather than throwing the camera across its whole range in one command.
Detection uses OpenCV's bundled face cascade (pip install 'uvc-ptz-camera-mcp[tracking]'), which needs no model download, no account and no network at first use. It finds faces: this follows a person, not a car or a dog. The loop and its arithmetic are tested against the simulator, but no part of follow mode has ever run against real hardware — treat it as the least proven thing here.
This class of camera reports positions it never moved to. Measured on the reference device (a DJI Osmo Pocket 4P in webcam mode, over its standard UVC controls):
180 read back `180` while the video proved the camera had not moved at all;0 on every sample while the frame demonstrably changed;120 read back 119, pan 200 read back 199.An agent acting on those values reports moves that never happened. So this server treats every device-reported value as a hint — returned, labelled, never trusted — and decides moved by comparing frames.
The threshold is not a guess either. It was calibrated on labelled hardware frames: every "same view" pair scored ≤ 0.104 (a 96-second quiet baseline, and two commands the hardware ignored), every "view changed" pair scored ≥ 0.624 (a pan, a tilt, a 12× zoom, two aim steps). The shipped threshold is the midpoint, 0.364 — a 6× separation — and the test suite asserts it still separates them. The labelled pairs and the values the metric produced are kept in the repository (tests/fixtures/) so the number can be re-checked rather than believed — as measurements, not pictures: no frame or video taken by a camera is committed here, and a test fails if one appears. The measurements behind the calibration are in docs/measurements.md.
device_reported is returned beside it, labelled a hint.moved: false, no error.uvx uvc-ptz-camera-mcp # run without installing
pip install uvc-ptz-camera-mcp # or install it
For a real camera on Windows you also need the DirectShow extras:
pip install "uvc-ptz-camera-mcp[dshow]"
Then point your host at it — --print-config emits the snippet with the right interpreter:
uvc-ptz-mcp --print-config
uvc-ptz-mcp --list-devices # what to pass to --device uvc-ptz-mcp --backend simulator # try it with no camera attached
Claude Desktop, Cursor, VS Code and friends all take the same shape — this is the whole configuration, because there is nothing to authenticate:
{
"mcpServers": { "ptz-camera": { "command": "uvx", "args": ["uvc-ptz-camera-mcp"] } } }
Add "--device", "Osmo" (any substring of the name --list-devices prints) when the machine has more than one camera, and "--backend", "simulator" to work with none. Both can also be set in the environment instead of the args — UVC_PTZ_DEVICE, UVC_PTZ_BACKEND and UVC_PTZ_STATE_DIR — which is what the Claude Desktop bundle uses, and which survives a host restart without editing its config again. A flag wins over the environment, and an empty value means "not set" (a host that leaves an option blank writes "", not nothing). Claude Desktop also accepts the .mcpb bundle attached to each release as a one-click install.
| Backend | What it is |
|---|---|
auto (default) | Prefer a real camera; fall back to the simulator, saying why |
dshow | Windows DirectShow: the real device path |
simulator | No hardware at all: a model calibrated from the measurements below |
Every result carries "simulated": true or false, and camera_status reports the reason when the simulator is standing in. Nothing quietly pretends to be hardware: a caller must never believe it is driving a camera when it is driving a model.
The simulator is calibrated from the reference device, not invented: ~0.4 s from write to first motion, a pan completing in about a second, a 4× zoom in about 2.5 s, silently dropped writes, and a read-back that echoes a request the hardware never applied. It renders frames by cropping a wide panorama, so a simulated pan genuinely changes the pixels — a simulator with a static picture would let verification pass vacuously.
v4l2; the interface is in place, the implementation is not written.IKsControl is refused on the device filter, IKsTopologyInfo lists three nodes and no vendor node, and CreateNodeInstance fails on all of them. Linux can reach it through uvcvideo's UVCIOC_CTRL_QUERY; that is a separate backend.check_view is there for judging a view rather than a move.pip install -e ".[dshow]" numpy pytest pytest-asyncio ruff
python -m pytest -q # 39 tests, three layers python -m ruff check . && python -m ruff format --check .
The suite is layered deliberately: the tool surface in-process against the simulator (mapping, validation, honest failure), pure unit tests for the compiler and the metric, and a real stdio handshake as a subprocess — including one run with a device name that cannot exist, because a server that dies at startup is invisible to every host and directory that lists it.
Built against a DJI Osmo Pocket 4P in webcam mode: VID_2CA3 / PID_0023, exposing pan −38…215°, tilt −33…105°, roll ±35°, zoom 100…1200 (1×–12×) as standard UVC camera controls. Any UVC PTZ camera exposes the same surface; the ranges are read from the device at startup rather than assumed, and nothing vendor-specific is hard-coded.
Not affiliated with, endorsed by, or supported by DJI.