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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
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. Returns: List of camera objects with name, enabled status, and other properties |
| 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. Returns: Dictionary containing system stats, detector info, and camera 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_snapshotA | 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_recordingsA | 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_configA | Get the complete Frigate configuration. Retrieves the full Frigate configuration including all cameras, detectors, motion settings, and system configuration. Returns: Complete Frigate configuration dictionary |
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 clear and distinct purpose: listing cameras, retrieving config, listing/details of events, recordings, snapshots, and stats. No two tools overlap significantly, so an agent can easily distinguish them.
All tool names follow a consistent 'get_' prefix with snake_case (e.g., get_cameras, get_event_details). The pattern is uniform and predictable.
With 7 tools covering key read-only aspects of a surveillance system (cameras, config, events, recordings, snapshots, stats), the count is well-scoped and neither too sparse nor excessive.
The set covers essential read operations for Frigate, including event details and recordings. Minor gaps like write operations (e.g., update event, set config) are absent, but this may be intentional for a read-only server.