Skip to main content
Glama
zax0rz

birdnet-go-mcp

by zax0rz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Related Servers

Alternatives to birdnet-go-mcp

  • birdnet-mcp

    jbeker
    F
    license
    A
    quality
    C
    maintenance
    Enables LLM clients to query a BirdNET-Go bird-detection instance for detections, species summaries, activity patterns, and historical searches via natural language.
    9
    -

Related Servers

  • Birding Buddy MCP

    woodcreeper
    A
    license
    A
    quality
    D
    maintenance
    An AI-powered birding companion that connects Claude to eBird and Xeno-canto APIs, enabling personalized birding with life list tracking, route-based hotspot discovery, and recording enrichment.
    28
    2
    MIT

  • neon-mcp

    idss-mesa
    A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to discover NEON ecological data products and sites, check data availability, list and download data files, and generate citations via the NEON Data API.
    20
    MIT

  • eBird MCP Server

    birdingkit
    A
    license
    Not graded
    quality
    D
    maintenance
    Integrates the eBird API with Claude to query bird observation data, including recent sightings, rare bird reports, contributor statistics, hotspot locations, and taxonomy information through natural language.
    5
    MIT

  • Frigate MCP Server

    dedsxc
    F
    license
    A
    quality
    A
    maintenance
    Enables AI assistants to interact with Frigate NVR security camera systems, supporting camera management, event detection, snapshots, recordings, and system stats via natural language.
    7
    10
    -

  • BirdNet-Pi MCP Server

    DMontgomery40
    F
    license
    Not graded
    quality
    D
    maintenance
    A Python-based server that enables accessing and analyzing bird detection data through the Model Context Protocol, offering features like filtering detections, accessing audio recordings, and generating reports.
    3
    -
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 8 tools

Disambiguation5/5

Each tool serves a distinct purpose: audio retrieval (URL vs base64), detection details, recent/search/summary views, health status, and new arrivals. No overlapping functionality or ambiguous boundaries.

Naming Consistency5/5

All tools follow a consistent get_ prefix for retrieval operations, with search_ appropriately used for the query tool. The base64 suffix clearly differentiates the inline-data variant from the URL variant.

Tool Count5/5

With 8 tools, the set is well-scoped for a bird-observation monitoring service—covering the essential read and search operations without redundancy or bloat.

Completeness5/5

The surface covers all likely read-oriented needs for this domain: recent detections, historical search, summaries, per-detection details, audio retrieval (both URL and base64), health status, and new arrivals. No significant gaps are evident.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources