Blink Camera runs on your own machine — the client starts it, so there is no endpoint to ping. 116 installs a week from pypi. Last commit 26 Sep 2026.
Control an Amazon Blink camera and its pan/tilt mount: aim it, read its position, grab a frame.
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
completed = subprocess.run( # noqa: S603 - fixed argv, configured binary
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add blink-camera-mcp -e 'BLINK_USERNAME=<BLINK_USERNAME>' -e 'BLINK_PASSWORD=<BLINK_PASSWORD>' -- uvx blink-camera-mcp{
"mcpServers": {
"blink-camera-mcp": {
"command": "uvx",
"args": [
"blink-camera-mcp"
],
"env": {
"BLINK_PASSWORD": "<BLINK_PASSWORD>",
"BLINK_USERNAME": "<BLINK_USERNAME>"
}
}
}
}[mcp_servers.blink-camera-mcp]
command = "uvx"
args = ["blink-camera-mcp"]
env = { BLINK_USERNAME = "<BLINK_USERNAME>", BLINK_PASSWORD = "<BLINK_PASSWORD>" }{
"mcpServers": {
"blink-camera-mcp": {
"command": "uvx",
"args": [
"blink-camera-mcp"
],
"env": {
"BLINK_PASSWORD": "<BLINK_PASSWORD>",
"BLINK_USERNAME": "<BLINK_USERNAME>"
}
}
}
}{
"servers": {
"blink-camera-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"blink-camera-mcp"
],
"env": {
"BLINK_PASSWORD": "<BLINK_PASSWORD>",
"BLINK_USERNAME": "<BLINK_USERNAME>"
}
}
}
}Put your own values in place of
<BLINK_USERNAME> (Blink account email address), <BLINK_PASSWORD> (Blink account password).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
BLINK_2FA_FILE (Path to a file holding the 2FA code, when the account has verification enabled. The code is read from the file, never from the command line), BLINK_CAMERA_NAME (Which camera to drive, when the account has more than one), BLINK_STATE_FILE (Where to cache the login token. Defaults to ~/.blink-mcp/state.json), BLINK_FFMPEG (Path to the ffmpeg binary, if it is not on PATH).
Alternatives to Blink Camera
same job, measured the same wayControl an OBSBOT Tiny 2 camera: pan/tilt/zoom, AI tracking, focus, exposure, snapshots, recording
Control a USB (UVC) pan/tilt/zoom camera, with every move confirmed from the picture.
Turns a phone into a camera+Bluetooth remote so AI assistants can see and control any PC.
Paste a draft and see the habits that make writing read like it came from an AI model.
MCP server for Reolink cameras: snapshots, device state, AI detection, PTZ, and deterrence controls
Read-only MCP access to DSGHT.ai published foresight and country-grounded claim resolution.
MCP Server for Revit integration - AI-Powered Revit Control
Lets an AI agent hand a secret to a person as a one-time link, with no way to read it back.
Blink Camera — questions
Answers built from our own checks of this server.