birdnet-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BIRDNET_GO_URL | Yes | Base URL of the BirdNET-Go instance, e.g. http://birdnet.local:8080 | |
| BIRDNET_GO_TIMEOUT | No | HTTP timeout in seconds (default 10) | 10 |
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 |
|---|---|
| get_recent_detectionsA | Get the most recent bird detections ("what's been heard lately?"). |
| get_detectionsA | Get bird detections for a specific day, optionally narrowed to an hour window or species. |
| search_detectionsA | Search historical detections with flexible filters. Results are paginated 20 per page. |
| get_detectionA | Get full details for a single detection, including weather context if recorded. |
| get_species_summaryA | Per-species statistics: detection counts, first/last heard, average confidence. |
| get_new_speciesA | Species detected for the first time ever within the recent period ("anything new lately?"). |
| get_activity_patternA | Temporal detection activity: counts per day over a date range, or per hour for one day. |
| get_instance_statusA | Check whether the BirdNET-Go instance is reachable and report its health. |
| get_species_infoA | Species details (rarity for this location) and taxonomy for a scientific name. |
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 9 tools
The detection-fetching tools (get_recent_detections, get_detections, search_detections) overlap somewhat, but their scopes are clearly separated by time window, filters, and pagination. Species statistics, new species, activity patterns, status, and taxonomy tools are all distinct.
All tools use lowercase snake_case with a consistent get_/search_ verb prefix followed by a clear noun. Singular and plural forms like get_detection and get_detections are predictable, and search_detections fits the same pattern.
Nine tools cover the server's read-only bird-detection analytics scope without redundancy. Each tool contributes a distinct query type, and the count fits comfortably within a well-scoped tool set.
The surface covers recent detections, single-detection detail, day/hour filtering, flexible historical search, species summaries, new species discovery, temporal activity, taxonomy, and instance health. For a read-only monitoring and analytics server, no significant workflow dead ends are apparent.