Frigate MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRIGATE_API_KEY | No | API key for authentication | None |
| FRIGATE_TIMEOUT | No | HTTP request timeout (seconds) | 30 |
| FRIGATE_FRIGATE_URL | No | Base URL of Frigate instance | http://localhost:5000 |
| FRIGATE_SERVER_HOST | No | Server host for SSE/HTTP modes | 0.0.0.0 |
| FRIGATE_SERVER_PORT | No | Server port for SSE/HTTP modes | 8000 |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_camerasA | Get the list of all cameras configured in Frigate. Returns a list of cameras with their names, status, and configuration details. |
| get_eventsB | Get recent detection events from Frigate. Retrieves events based on optional filters for camera and detected object label. |
| get_statsA | Get Frigate system statistics and performance metrics. Returns information about CPU usage, memory, detector performance, camera FPS, and detection metrics. |
| get_event_detailsB | Get detailed information about a specific detection event. Retrieves comprehensive details including zones, thumbnails, clips, and timeline information for a single event. |
| get_snapshotB | Get a snapshot from a specific camera. Returns the URL to access a snapshot image from the camera, either current or from a specific timestamp. |
| get_recordingsB | Get recording information for a specific camera. Retrieves the recording summary including available recordings and storage information for a camera on a specific date. |
| get_configB | Get the complete Frigate configuration. Retrieves the full Frigate configuration including all cameras, detectors, motion settings, and system configuration. |
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 targets a distinct resource and action: camera listing, event listing, event detail, stats, snapshot, recordings, and config. get_events vs get_event_details might superficially overlap, but list-vs-detail is a clear and standard distinction.
All seven tools follow a strict get_<resource> snake_case pattern. No mixed conventions or vague verbs.
Seven tools is well-scoped for a read-oriented Frigate monitoring server. Each tool covers a distinct query surface without padding.
Core read workflows are covered: cameras, events, event details, snapshots, recordings, stats, and config. Write/administrative operations (event deletion, retention updates, restarts) are absent, but likely out of scope for a read-focused monitoring server.