frigate-auth-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRIGATE_URL | No | Base URL of the authenticated port, default http://localhost:8971 | http://localhost:8971 |
| FRIGATE_USER | Yes | Frigate username, required | |
| FRIGATE_PASSWD | Yes | Password of the Frigate user, required (secret) | |
| FRIGATE_TIMEOUT | No | Seconds per request, default 30 | 30 |
| FRIGATE_IMAGE_CAMERAS | No | Cameras allowed to return images, comma-separated; default all | all |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| frigate_statusA | Frigate version, uptime, the cameras this user may see and per-camera fps / detection fps. |
| list_eventsB | Tracked-object events, newest first. after/before: ISO 8601 or unix seconds. label e.g. person, cat, squirrel. has_description=True keeps only events with a GenAI description. |
| get_eventB | One event in detail, including the GenAI description when there is one. |
| event_snapshotC | Snapshot of an event with its bounding box; crop=True zooms on the object. |
| latest_frameC | The current frame of a camera. |
| list_reviewsB | Review items (what the Frigate UI shows), newest first. severity: alert or detection. after/before: ISO 8601 or unix seconds; after defaults to 7 days ago (Frigate itself returns only the last 24 hours when it is not set). |
| review_summaryB | Counts of alerts and detections for the last 24 hours and per day for the last |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: server status, event listing/detail/snapshot, live camera frame, review listing, and review summary. The event vs. review split and metadata vs. imagery split are explained well enough to prevent misselection.
Most tools follow a readable verb_noun pattern (list_events, get_event, list_reviews), but there are noun-first compounds (event_snapshot, review_summary, latest_frame) and a prefixed frigate_status. The deviations are minor and still predictable.
Seven tools is well-scoped for a Frigate monitoring server. Each tool covers a distinct operation without obvious redundancy or missing core capability at this surface size.
The set covers status, events, snapshots, live frames, and review summaries, which handles core monitoring workflows. However, it lacks event clip/recording retrieval and any operation to mark reviews as reviewed, despite surfacing reviewed/not-reviewed counts.