BridgeMCP Weather Roadmap

[Arsie-codes]

This discussion tracks the planned direction for bridgemcp-server-weather.

v0.1.0 (released)

• get_current_weather, get_forecast, get_weather_summary tools
• Open-Meteo integration, no API key required
• Geocoding support (city names, coordinates)
• Full Pydantic model coverage
• WeatherPlugin lifecycle pattern

Potential future directions

These are possibilities, not commitments. Community feedback will shape priorities.

New tools

• get_air_quality — AQI, PM2.5, ozone via Open-Meteo air quality API
• get_marine_weather — wave height, sea temperature for coastal locations
• get_historical_weather — historical daily data for any date range
• get_climate_normals — 30-year climate averages for a location

Enhancements

• Hourly forecast breakdown within get_forecast
• UV index in get_current_weather
• Configurable unit system (metric / imperial / both)
• Caching layer to reduce Open-Meteo API calls for repeated queries

Ecosystem

• Serve as the canonical reference for additional official BridgeMCP servers

How to influence the roadmap

Open a GitHub issue or reply here with your use case. Concrete examples of what you are trying to build are more useful than feature requests in the abstract.

The rule from the BridgeMCP architecture guide applies here too: every addition should be universal, stable, and not implementable as a plugin without special-casing inside the server.