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

Blink Camera

by AbhijatSaxenaversion 0.1.1i★ 0iRuns on your computerRepository ↗
Registry nameio.github.AbhijatSaxena/blink-camera-mcp

How to install

What it does

Control an Amazon Blink camera and its pan/tilt mount: aim it, read its position, grab a frame.

  • Connects Runs on your computer
  • Account or key Needs BLINK_PASSWORD, BLINK_2FA_FILE · 1 setting to fill in (BLINK_USERNAME)
  • Category Online shops & payments

Why it ranks here

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

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score7/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 Blink Camera. Follow https://mcp.popnx.com/i/abhijatsaxena-blink-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

You need a Blink Camera key (create it on the maker’s site) · 1 setting(s) to fill in (BLINK_USERNAME) · 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 Blink 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": { "blink-camera": { "command": "uvx", "args": [ "blink-camera-mcp" ], "env": { "BLINK_USERNAME": "your-value", "BLINK_PASSWORD": "your-value", "BLINK_2FA_FILE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For BLINK_PASSWORD, BLINK_2FA_FILE, BLINK_USERNAME, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Blink 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.

  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. Sign up and create a Blink Camera key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Blink Camera site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • BLINK_USERNAME Blink account email address.

    Descriptions are as written by the maker.

  4. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  5. Paste these settings and save the file

    {
      "mcpServers": {
        "blink-camera": {
          "command": "uvx",
          "args": [
            "blink-camera-mcp"
          ],
          "env": {
            "BLINK_USERNAME": "your-value",
            "BLINK_PASSWORD": "your-value",
            "BLINK_2FA_FILE": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Quit Claude and open it again

  7. Try it

    Use Blink Camera and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Blink Camera or shows a Blink Camera tool in the answer, you are connected

3 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.

  • 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.

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 Blink Camera yet

Blink Camera 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 Blink Camera

  • You need a Blink Camera key (create it on the maker’s site) · 1 setting(s) to fill in (BLINK_USERNAME) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Blink Camera key (create it on the maker’s site) · 1 setting(s) to fill in (BLINK_USERNAME) · Install Python (uv) on your computer first (one time)
  • You need a Blink Camera key (create it on the maker’s site) · 1 setting(s) to fill in (BLINK_USERNAME) · Install Python (uv) on your computer first (one time)
  • You need a Blink Camera key (create it on the maker’s site) · 1 setting(s) to fill in (BLINK_USERNAME) · Install Python (uv) on your computer first (one time)

B · Others in Online shops & payments 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

You need a Blink Camera key (create it on the maker’s site) · 1 setting(s) to fill in (BLINK_USERNAME) · 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 Blink 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 blink-camera --env BLINK_USERNAME=your-value --env BLINK_PASSWORD=your-value --env BLINK_2FA_FILE=your-value -- uvx blink-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) For BLINK_PASSWORD, BLINK_2FA_FILE, BLINK_USERNAME, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Blink 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.

  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. Sign up and create a Blink Camera key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Blink Camera site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • BLINK_USERNAME Blink account email address.

    Descriptions are as written by the maker.

  4. Open Terminal

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

  5. Paste this command and press Enter

    claude mcp add --scope user blink-camera --env BLINK_USERNAME=your-value --env BLINK_PASSWORD=your-value --env BLINK_2FA_FILE=your-value -- uvx blink-camera-mcp

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Type /mcp in Claude Code

    You should see Blink Camera listed as connected

  7. Try it

    Use Blink Camera and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Blink Camera or shows a Blink Camera tool in the answer, you are connected

3 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.

  • 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.

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

You need a Blink Camera key (create it on the maker’s site) · 1 setting(s) to fill in (BLINK_USERNAME) · 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 Blink 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": { "blink-camera": { "command": "uvx", "args": [ "blink-camera-mcp" ], "env": { "BLINK_USERNAME": "your-value", "BLINK_PASSWORD": "your-value", "BLINK_2FA_FILE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For BLINK_PASSWORD, BLINK_2FA_FILE, BLINK_USERNAME, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Blink 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.

  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. Sign up and create a Blink Camera key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Blink Camera site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • BLINK_USERNAME Blink account email address.

    Descriptions are as written by the maker.

  4. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  5. Fill in your key

    In the Blink Camera settings, BLINK_PASSWORD, BLINK_2FA_FILE, BLINK_USERNAME is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in Cursor in Agent mode

  7. Try it

    Use Blink Camera and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Blink Camera or shows a Blink Camera tool in the answer, you are connected

3 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.

  • 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.

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

You need a Blink Camera key (create it on the maker’s site) · 1 setting(s) to fill in (BLINK_USERNAME) · 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 Blink 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": { "blink-camera": { "type": "stdio", "command": "uvx", "args": [ "blink-camera-mcp" ], "env": { "BLINK_USERNAME": "your-value", "BLINK_PASSWORD": "your-value", "BLINK_2FA_FILE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For BLINK_PASSWORD, BLINK_2FA_FILE, BLINK_USERNAME, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Blink 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.

  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. Sign up and create a Blink Camera key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Blink Camera site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • BLINK_USERNAME Blink account email address.

    Descriptions are as written by the maker.

  4. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  5. Fill in your key

    In the Blink Camera settings, BLINK_PASSWORD, BLINK_2FA_FILE, BLINK_USERNAME is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

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

  7. Try it

    Use Blink Camera and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Blink Camera or shows a Blink Camera tool in the answer, you are connected

3 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.

  • 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.

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 Blink Camera💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user blink-camera --env BLINK_USERNAME=your-value --env BLINK_PASSWORD=your-value --env BLINK_2FA_FILE=your-value -- uvx blink-camera-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "blink-camera": {
      "command": "uvx",
      "args": [
        "blink-camera-mcp"
      ],
      "env": {
        "BLINK_USERNAME": "your-value",
        "BLINK_PASSWORD": "your-value",
        "BLINK_2FA_FILE": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "blink-camera": {
      "command": "uvx",
      "args": [
        "blink-camera-mcp"
      ],
      "env": {
        "BLINK_USERNAME": "your-value",
        "BLINK_PASSWORD": "your-value",
        "BLINK_2FA_FILE": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "blink-camera": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "blink-camera-mcp"
      ],
      "env": {
        "BLINK_USERNAME": "your-value",
        "BLINK_PASSWORD": "your-value",
        "BLINK_2FA_FILE": "your-value"
      }
    }
  }
}

Values you fill in

  • BLINK_USERNAME required env
    Blink account email address.
  • BLINK_PASSWORD secret required env
    Blink account password.
  • BLINK_2FA_FILE secret required env
    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 env
    Which camera to drive, when the account has more than one.
  • BLINK_STATE_FILE env
    Where to cache the login token. Defaults to ~/.blink-mcp/state.json.
  • BLINK_FFMPEG env
    Path to the ffmpeg binary, if it is not on PATH.

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
47/wk
Connection
Runs on your computer
Latest versioni
0.1.1
Published to registryi
Sep 26, 2026
Code last changedi
Sep 26, 2026
Maker
AbhijatSaxena
Packages
pypi: blink-camera-mcp
Website
github.com
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 AbhijatSaxena, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 months 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 blink-camera-mcp@0.1.1

Checks only this package version, not every dependency · checked Nov 16, 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/abhijatsaxena-blink-camera-mcp.svg)](https://mcp.popnx.com/en/servers/abhijatsaxena-blink-camera-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 Online shops & paymentsi

  • More stars than 0% of the other 2932 servers in this category
  • Published to the registry more recently than 33% of the other 2932 servers in this category
  • Basic checks equal to or better than 99% of the other 2932 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 Blink Camera 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?

You need to fill in: BLINK_PASSWORD, BLINK_2FA_FILE

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 months ago, and the latest version (0.1.1) reached the registry 2 months 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: Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server

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

Stripe MCP

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

by stripeWidely used★ 2.1KUpdated 13 months ago

Runs in the cloud✓ service owner · stripe.com

flightclaw

Search ~300 airlines and book flights with a checkout link. OAuth sign-in by email code.

by flightclawGrowing★ 86Updated 2 months ago

Runs in the cloud✓ service owner · flightclaw.com

Trade It

Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.

by trade-it-incEarly★ 62Updated 34 days ago

Runs in the cloud✓ service owner · tradeit.app

idealo MCP Server

Search products, compare prices and discover deals across 6 European markets with your AI assistant.

by idealoEarly★ 28Updated 6 months ago

Runs in the cloud✓ service owner · mcp.idealo.com
Compared with similar ones
This one
Blink Camera
Stripe MCPflightclawTrade ItMarketplace Ad Pros: Amazon Ads & Seller Centralidealo MCP Server
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 keyYesNoNoNoNoNo
Add with + in ClaudeNoYesNoNoNoNo
Basic checks3/34/44/45/54/44/4
LicenseMITMITMITCC0-1.0MITMIT
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.

blink-camera-mcp

An MCP server for Amazon Blink cameras, including the pan/tilt mount that Blink's own API gives you no way to move.

Install it with uvx blink-camera-mcp. It is listed in the official MCP Registry as io.github.AbhijatSaxena/blink-camera-mcp.

Give any MCP host — Claude Desktop, an IDE agent, your own client — the ability to see where a camera is pointing, aim it, and look through it.

camera_status       where it points, travel limits, session state, stream URL

pan_tilt aim at an absolute angle, wait until the hardware confirms pan_tilt_nudge turn relative to where it points now pan_tilt_stop stop the motors pan_tilt_home go to the saved home position pan_tilt_set_home save the current angle as home pan_tilt_overview 360° sweep snapshot one still frame, returned as image content

Why this exists

Blink cameras are cloud devices. There is no local API, no ONVIF, no UVC — video exists only as a short-lived session brokered by Blink's cloud, capped at 300 seconds. Two consequences:

  1. Anything that wants to use the camera has to hold that session open and refresh it.
  2. The pan/tilt mount is not a device you can talk to. It has no endpoint of its own: it is driven *inside* the camera's media session, and its position comes back on the same socket. A client that reads only the video and skips every other message never sees any of that traffic, which is why the mount has looked uncontrollable for years.

This server owns the session (or reuses one), frames it correctly, routes the accessory messages, and exposes the whole thing as MCP tools with closed-loop semantics.

Install

pip install blink-camera-mcp          # or without installing: uvx blink-camera-mcp

The distribution is blink-camera-mcp; the command it installs is blink-mcp.

You need Python 3.10+, a Blink account, and ffmpeg on PATH for snapshot (set BLINK_FFMPEG if it lives somewhere unusual).

Configure

Credentials come from the environment, and only the first run needs them:

export BLINK_USERNAME="you@example.com"

export BLINK_PASSWORD="..." export BLINK_CAMERA_NAME="Front Door" # optional; defaults to the only camera

The token is cached (token material only — a password is never written to disk), so later runs need no credentials. Cache location defaults to ~/.blink-mcp/state.json; override with BLINK_STATE_FILE.

If Blink asks for a 2FA code, the server will not prompt you and will not take the code from anywhere but a file:

export BLINK_2FA_FILE=/path/to/code.txt

Write the newest code into that file; it is read once and deleted. This keeps a live credential out of chat logs, shell history and argument lists.

Add it to your MCP host

blink-mcp --print-config
{

"mcpServers": { "blink": { "command": "uvx", "args": ["blink-camera-mcp", "--stream-port", "9000"] } } }

Hosts that manage their own Python (Claude Desktop, VS Code, LM Studio, …) run uvx as above. If you installed it into a virtualenv instead, set command to that interpreter and args to ["-m", "blink_mcp", …].

Claude Desktop — one-click

Download blink-camera-mcp-0.1.1.mcpb from the releases page and open it. Claude Desktop prompts for your Blink email and password (kept in the OS keychain), and asks for the 2FA code file only if your account uses verification. The bundle carries no server code of its own — it depends on this package from PyPI, so it can never drift from the released version.

LM Studio, VS Code, Cursor, Cline and friends

They all read the same JSON as above. Paste it into the host's MCP config — LM Studio: mcp.json; VS Code: .vscode/mcp.json; Cursor: .cursor/mcp.json. Cline installs it from this README.

Hermes

Hermes' curated catalog is for remote, OAuth-authenticated servers, and this one has to run on a machine that can reach your camera — so add it as an ordinary stdio server in ~/.hermes/config.yaml:

mcp_servers:

blink: command: "uvx" args: ["blink-camera-mcp"] env: BLINK_USERNAME: "you@example.com" BLINK_PASSWORD: "…"

Restart the session (or /reload-mcp) and the eight tools show up like any other.

Two ways to run it

Standalone (default) — the server owns the camera's live session and publishes the video to a local TCP port (tcp://127.0.0.1: , or a fixed one with --stream-port 9000). Point OBS at it as a Media Source if you want the camera as a webcam as well.

Against a bridge — if something else already holds the session:

blink-mcp --control-url http://127.0.0.1:9100 --stream-url tcp://127.0.0.1:9000

This matters because Blink allows one live session per camera: a viewer and a controller have to share it or take turns. Running two things that each insist on their own session means one of them loses.

What "closed-loop" means here

The mount reports its angle *while it is moving*. So pan_tilt does not sleep and hope: it sends the command and returns only when the hardware reports that its motors stopped at the requested angle — typically well under a second.

pan_tilt_nudge(+4)  -> settled=True moved=True elapsed=0.67s -> pan=117 tilt=-75

pan_tilt_nudge(-4) -> settled=True moved=True -> pan=113 tilt=-75

Two deliberate behaviours, because a confident wrong answer is worse than a failure:

  • if the mount never confirms, the tool fails rather than returning the last angle it happened to know (a stale position dressed up as success would have an agent announce a move that never happened);
  • a command to the angle the camera already holds is a no-op reported as moved: false — success, not failure.

Privacy and safety

  • snapshot decodes a frame of whatever the camera is pointed at. The tool description says so, and tells the agent to use it only when the user asks. Nothing here captures anything on its own.
  • The server talks to Blink directly, and the token cache holds no password.
  • Any bridge control plane is loopback-only by design: it moves a physical camera.

How it was built

The accessory channel is undocumented. It was recovered from the official Android app — dex bytecode and the native library's symbol table — and then verified against hardware:

frame        [flag:1][id:4 big-endian][length:4 big-endian][payload]

send flag 0x14 INLINE_COMMAND, id = commandId move=3 [0,0,0,0, , ,0] stop=4 home=5 set_home=6 overview=7 receive flag 0x15 ACCESSORY_MESSAGE, id = message id POSITION=2 / HOME_POSITION=3 [ , , , ] ROSIE_LIMITS=4 PAN_OVERVIEW_COMPLETE=5 lights/siren = 0/1/6/7

status is 0x00 idle and 0x10 moving. Angles are single signed bytes.

The same protocol knowledge is being contributed upstream to blinkpy so every Blink integration benefits, not just this server. blink_mcp/immi.py is byte-identical to the module submitted there, and switches to the upstream copy automatically once it ships.

Standing on the shoulders of blinkpy, which implements the Blink cloud API and the IMMI transport.

Limitations

  • Verified on a Blink Mini with the pan/tilt mount. Other camera families use a different live transport (WebRTC with JSON-RPC commands rather than this binary channel) and are not supported yet.
  • One live session per camera, as above.
  • Blink caps a session at 300 s; the server rotates it around 270 s and consumers never notice.
  • snapshot needs ffmpeg; it decodes one frame from the stream rather than opening a second session.

Tests

pytest                    # 68 offline tests: protocol bytes, closed-loop logic, tool layer,

a real stdio handshake, and a stub control plane

The suite is offline and needs no camera. For real hardware:

python tests/live_smoke.py --state-file ~/.blink-mcp/state.json

which logs in, moves the camera out and back, and captures a frame.

License

MIT