Birding Planner
Sends daily briefing emails about birding migration conditions via Resend's email API.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Birding PlannerPlan a birding trip near Cincinnati this weekend"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Birding Planner
MCP server + daily email briefing for Cincinnati-area migration monitoring.
MCP Server Tools
All 10 tools for interactive birding planning in Claude Desktop:
Tool | What it does |
| Ranks nearby hotspots by recent species count + migration activity |
| BirdCast radar data + NWS weather interpretation |
| Recent species and notable sightings at a single hotspot |
| Side-by-side species comparison with iNaturalist verification |
| Where a species has been seen recently near a location |
| Recommends the best day in a date range using migration + weather |
| NWS overnight/morning forecast interpreted for migration prediction |
| Cross-references eBird reports against iNaturalist photo-verified obs |
| Sunrise, civil twilight, and recommended arrival time |
| Historical peak week and current phenology status via BirdCast |
Setup
1. API Keys
eBird API key (required): https://ebird.org/api/keygen — free
BirdCast API key (required): contact BirdCast at https://birdcast.info for API access
Resend API key (for email): https://resend.com — free tier, 3,000 emails/month
2. Environment
Copy .env.example to .env and fill in your keys:
cp .env.example .env3. Install dependencies
npm install4. Claude Desktop Integration
Add to your Claude Desktop claude_desktop_config.json:
{
"mcpServers": {
"ebird-birding-planner": {
"command": "node",
"args": ["/absolute/path/to/ebird-birding-planner/src/index.js"],
"env": {
"EBIRD_API_KEY": "your_key_here",
"BIRDCAST_API_KEY": "your_key_here"
}
}
}
}Daily Briefing (Anthropic Routine)
The briefing runs as a cloud-hosted Anthropic Routine — no machine needs to be on.
How it works
Agent runs at 5:45 AM ET daily during migration season
scripts/triage.jsfetches BirdCast + NWS data and outputs a JSON recommendationAgent decides: full briefing / quiet-period note / silent skip
scripts/briefing.jsbuilds HTML email and sends via Resend
Test locally
# Run triage check (outputs JSON recommendation)
node scripts/triage.js
# Generate briefing HTML (saves to ./briefing-output/ if no Resend key)
node scripts/briefing.js
# Generate quiet-period email
node scripts/briefing.js --quietSet up the Routine
See routine-prompt.md for the exact prompt to paste into claude.ai when creating the Routine. Required secrets to configure:
EBIRD_API_KEYBIRDCAST_API_KEYRESEND_API_KEYBRIEFING_EMAIL_TOBRIEFING_REGION(default: US-OH-061)BRIEFING_LAT/BRIEFING_LNG(default: 39.1 / -84.5)
Architecture
src/
index.js — MCP server (10 tools)
ebird-client.js — eBird API v2 wrapper
birdcast-client.js — BirdCast radar data
nws-client.js — NWS Weather API
inaturalist-client.js — iNaturalist photo verification
utils.js — Cache, location resolution, date parsing
scripts/
triage.js — Fast migration check, outputs JSON
briefing.js — HTML email builder + Resend senderResources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/minikdj/ebird-birding-planner'
If you have feedback or need assistance with the MCP directory API, please join our Discord server