google-weather-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_WEATHER_API_KEY | Yes | Your Google Maps Platform Weather API key. Required for fetching weather data; without it the dashboard runs with demo weather but the MCP server cannot provide real weather tools. | |
| GOOGLE_GEOCODING_API_KEY | No | Optional Google Geocoding API key. If not set, city search uses OpenStreetMap Nominatim. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| geocode_locationA | Resolve a city or address to latitude and longitude. |
| get_current_weatherA | Current conditions from the Google Maps Platform Weather API for a place or coordinates. |
| get_hourly_forecastA | Hourly forecast (default 24 hours, max 240) from the Google Weather API. |
| get_daily_forecastC | Daily forecast (default 10 days) from the Google Weather API. |
| get_weather_dashboardA | Combined current conditions, 24-hour, and 10-day forecast for a location. Best for filling a weather UI. |
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 5 tools
Each tool targets a clear weather data need: geocoding, current conditions, hourly, daily, and combined dashboard. The dashboard overlaps with the individual forecast tools, but its purpose as a one-call UI filler is clearly distinct.
Most tools follow a get_<detail> pattern, and geocode_location is also verb_noun, so the set is readable and predictable. The only minor deviation is geocode_location not using the get_ prefix.
Five tools is well-scoped for a weather server: geocoding plus current, hourly, daily, and dashboard views cover the domain without unnecessary bloat.
The tool surface covers the full basic weather workflow: resolve location, fetch current conditions, get forecasts at different granularities, and retrieve a combined view. No significant gaps for a weather-focused MCP server.