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.
Control an Amazon Blink camera and its pan/tilt mount: aim it, read its position, grab a frame.
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 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
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.
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
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.
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.
SettingsDeveloperEdit Config
{
"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
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
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
A · Use an app that can connect Blink Camera
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)
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.
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
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.
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.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
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-mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Blink Camera listed as connected
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
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)
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.
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
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.
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.
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
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
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)
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.
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
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.
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.
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
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
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
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-mcpClaude 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"
}
}
}
}BLINK_USERNAME required envBLINK_PASSWORD secret required envBLINK_2FA_FILE secret required envBLINK_CAMERA_NAME envBLINK_STATE_FILE envBLINK_FFMPEG 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: blink-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 2 months 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 blink-camera-mcp@0.1.1
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-blink-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.
You need to fill in: BLINK_PASSWORD, BLINK_2FA_FILE
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 2 months ago, and the latest version (0.1.1) reached the registry 2 months 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: Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server
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’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
Search ~300 airlines and book flights with a checkout link. OAuth sign-in by email code.
Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.
Amazon Ads, Seller Central, Vendor Central and AMC data for AI agents. Read-only by default.
Search products, compare prices and discover deals across 6 European markets with your AI assistant.
| This one Blink Camera | Stripe MCP | flightclaw | Trade It | Marketplace Ad Pros: Amazon Ads & Seller Central | idealo MCP Server | |
|---|---|---|---|---|---|---|
| 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 | Yes | No | No | No | No | No |
| Add with + in Claude | No | Yes | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 5/5 | 4/4 | 4/4 |
| License | MIT | MIT | MIT | CC0-1.0 | MIT | 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 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
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:
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.
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).
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.
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", …].
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.
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' 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.
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.
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:
moved: false — success, not failure.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 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.
snapshot needs ffmpeg; it decodes one frame from the stream rather than opening a second session.pytest # 68 offline tests: protocol bytes, closed-loop logic, tool layer,
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.
MIT