WeatherAPI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEATHERAPI_KEY | Yes | API key for WeatherAPI.com. Get a free API key at https://www.weatherapi.com/signup.aspx |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_weatherA | Get real-time current weather for any location. Returns temperature, wind speed and direction, humidity, pressure, UV index, visibility, feels-like temperature, and weather condition. Optionally includes air quality (AQI) data. |
| get_forecastA | Get weather forecast for 1 to 14 days. Returns daily summaries (max/min/avg temp, rain chance, UV, wind) and hourly breakdowns. Also returns current conditions, astronomy data (sunrise/sunset/moon phase), and optionally weather alerts and air quality. |
| get_historyA | Get historical weather data for a specific date from 1 January 2010 onwards. Returns daily summary and full hourly breakdown. Useful for past weather lookups, analytics, and backtesting. |
| get_future_weatherA | Get future weather forecast for a date between 14 and 300 days from today. Returns 3-hourly data. Available on Pro+ plan and above. |
| get_marine_weatherB | Get marine and sailing weather forecast including significant wave height, swell height, swell direction, swell period, and optionally tide data. Useful for nautical and coastal planning. |
| get_astronomyB | Get astronomy data for a location and date: sunrise, sunset, moonrise, moonset, moon phase, and moon illumination percentage. |
| get_timezoneA | Get timezone and current local time for any location. Returns IANA timezone ID (e.g. Europe/London), local time string, and unix epoch. |
| search_locationsA | Search for cities and towns by partial name or postcode. Returns an array of matching locations with their coordinates, region, country, and URL slug. Useful for building location pickers or resolving ambiguous place names. |
| ip_lookupA | Look up geolocation data for an IP address: city, region, country, coordinates, timezone, and whether it's in the EU. Pass 'auto:ip' to geolocate the caller's own IP address. |
| get_alertsA | Get active government weather alerts and warnings for a location. Covers USA, UK, Europe, and rest of world. Returns headline, severity, urgency, affected areas, and full description. |
| get_sportsB | Get upcoming sports events (football/soccer, cricket, golf) for a location, with stadium, country, tournament name, and start time. |
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 11 tools
Every tool has a clearly distinct purpose with no overlap; each targets a specific weather or location-related function (e.g., current weather, alerts, astronomy, marine, sports, timezone), making misselection unlikely. The descriptions reinforce unique scopes, such as separating forecast from history or marine from general weather.
All tools follow a consistent verb_noun pattern (e.g., get_alerts, get_astronomy, get_current_weather), with no deviations in style or convention. This predictability aids in easy identification and usage across the tool set.
With 11 tools, the count is well-scoped for a weather API server, covering diverse aspects like current conditions, forecasts, history, marine data, and location utilities. Each tool earns its place without feeling excessive or insufficient for the domain.
The tool set provides comprehensive coverage for weather and location services, including CRUD-like operations (e.g., get, search) across current, forecast, historical, marine, and astronomy data, plus utilities like timezone and IP lookup. No obvious gaps exist for typical agent workflows in this domain.