pollen-alert-mcp
Related Servers
Alternatives to pollen-alert-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables a household assistant to answer personalized air-quality and pollen questions, plan outdoor activities, issue threshold-based alerts, and log symptoms using live Open-Meteo data. It exposes these capabilities as tools with spoken responses and structured content for MCP clients.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to fetch Google Pollen API forecasts and turn them into daily briefs with custom alert thresholds per pollen type or plant, returning compact JSON and Markdown.Apache 2.0
- AlicenseAqualityDmaintenancePer-species pollen forecasts at any point on Earth, seven days ahead. Free tier covers casual use.41MIT
- AlicenseAqualityBmaintenanceThe official Model Context Protocol server for Ambee. It gives any MCP-compatible AI assistant — Claude, ChatGPT, Cursor, VS Code, Ollama, and more direct access to live air quality, pollen, and weather data.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables natural language interaction with air quality data from Airly, including real-time measurements, nearby stations, and forecasts.226 npmMIT
- AlicenseAqualityCmaintenanceEnables AI assistants to check live air quality in Poland, including the nearest official GIOŚ monitoring stations with the air quality index and hourly PM2.5, PM10, NO2, O3 and SO2 readings, plus smog warnings for the voivodeship and a 3-day Copernicus CAMS forecast of particulate matter and pollen. Can be used via a public no-key endpoint or run locally.3395 npmMIT
TDQS
Scored across 2 tools
Each tool has a distinct purpose: one converts place names to coordinates, the other retrieves pollen forecasts using coordinates. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern with snake_case (get_coordinates, get_pollen_forecast), making them predictable and easy to understand.
With only two tools, the server feels slightly thin, but it covers the essential workflow for a pollen alert service: location lookup and forecast retrieval. The count is reasonable for a focused domain.
The server provides the core functionality needed to get pollen alerts by location. A minor gap is the lack of a direct place-name-to-forecast tool, but the separate steps are logically sound.