Spot AI MCP (Unofficial)

io.github.phil-bryantPublished by GitHub account phil-bryantv0.3.0Updated Oct 24, 2026

Unofficial community MCP server for the Spot AI camera and video-intelligence REST API. Read-only.

The publisher's own server: Spot

VerifiedSTDIODesktop onlySecurity & MonitoringData & Analytics

Overview

AI-generated overview

Unofficial read-only MCP server for the Spot AI camera and video-intelligence REST API, letting an assistant browse cameras, zones and intelligence reports.

What you can do
  • List locations, cameras, camera details and enabled-camera counts, plus recorders (appliances)
  • Inspect zones defined on a camera
  • Retrieve counting, idle and presence intelligence events for people, vehicles or forklifts over a date range
  • Get license-plate-recognition reports for LPR cameras
  • Generate live-stream viewing URLs for up to four cameras
  • Call any documented v1 or v2 GET path as an escape hatch
When to use it
Useful when you want an assistant to answer questions about a Spot AI camera deployment — which cameras exist and where, what activity was counted in a period, plate reads, or a live view link — without giving it write access to the organization.
Requirements
Runs locally over stdio as a Python 3.9+ package (uvx or pip install spot-ai-mcp, or python3 -m spot_ai_mcp). Needs a Spot AI API key in the SPOT_AI_API_KEY environment variable, or optionally a secret-helper command configured through the SPOT_AI_OP_BIN, SPOT_AI_OP_ITEM and SPOT_AI_OP_FIELD variables. Network access to the Spot AI API is required.
Before you install
Requires a Spot AI API key, which must be given an authorization role in the dashboard; a key without a role returns empty lists. The key is sent as a bearer token to the Spot AI API. The server is read-only by design, but one tool issues a POST that generates a live viewing URL, and the generic GET escape hatch can reach any documented API path. It is unofficial and not affiliated with Spot AI.

Installation

In SourceWeft

  1. Open Spot AI MCP (Unofficial) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

spot-ai-mcp

Unofficial community MCP server for the Spot AI camera / video-intelligence REST API. Not affiliated with or endorsed by Spot AI.

Single-file, stdio transport, no dependencies beyond Python 3.9+. Read-only by design: it can browse cameras and intelligence data but can never modify anything in your Spot AI org. Every tool wraps a GET endpoint except get_live_stream_urls, which wraps POST /v1/cameras/live — a read-like POST that only generates a viewing URL. All tools declare the readOnlyHint: true MCP annotation.

Install

bash
uvx spot-ai-mcp

or pip install spot-ai-mcp, or run straight from a checkout with python3 -m spot_ai_mcp (no dependencies to install).

Register with Claude Code:

bash
claude mcp add spot-ai -s user -e SPOT_AI_API_KEY=YOUR_KEY -- uvx spot-ai-mcp

API key

Create a key in the Spot AI dashboard's API settings, then add an authorization (a role, e.g. Owner, optionally scoped) on the key's settings page. A key without a role returns empty lists from every resource endpoint while get_camera_count still works — that's the tell.

The server resolves the key lazily on the first API call:

  1. SPOT_AI_API_KEY environment variable — the normal path.
  2. Optionally, a secret-helper command, so the key never sits in an env var or config: the server runs $SPOT_AI_OP_BIN -f $SPOT_AI_OP_ITEM $SPOT_AI_OP_FIELD (defaults 1psa -f spot.ai api_key, per 1psa, a vault-scoped 1Password service-account CLI). Point these at any command with the same flag convention.

The key is never written to disk or config by this server.

Tools

ToolWhat it does
list_locationsLocations the key can see (paginated)
list_camerasCameras with status, location, IP, MAC (paginated)
get_cameraOne camera by id
get_camera_countNumber of enabled cameras in the org
list_appliancesIntelligent Video Recorders (paginated)
get_zonesZones defined on a camera
get_intelligenceCounting / idle / presence events for people, vehicles, or forklifts over a date range
get_lpr_reportLicense-plate-recognition report for an LPR camera
get_live_stream_urlsLive-stream viewing URL for up to 4 cameras
spot_api_getEscape hatch: GET any documented /v1/ or /v2/ path

Notes

  • Dual-era MCP server: speaks both the modern per-request protocol (server/discover, spec 2026-07-28) and the legacy initialize handshake (2024-11-05 through 2025-06-18), so old and new clients both work.
  • Base URL is https://dev-api.spot.ai, auth is Authorization: Bearer <key>.
  • Cloudflare in front of the API rejects Python's default user agent with error 1010; the server sends User-Agent: spot-ai-mcp/<version>.
  • Endpoint index: https://developers.spot.ai/llms.txt (append .md to any docs URL for markdown, including the OpenAPI definition per endpoint).

License

MIT

Source: README.md at commit 110c90e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Spot integrations