OpenWeatherMap MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port for HTTP transport | 3000 |
| MCP_ENDPOINT | No | HTTP endpoint path | /stream |
| MCP_TRANSPORT | No | Transport type: stdio or httpStream | stdio |
| OPENWEATHER_API_KEY | No | Your OpenWeatherMap API key (required for stdio transport only) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-current-weatherC | Get current weather conditions for a location |
| get-weather-forecastC | Get weather forecast for up to 5 days |
| get-hourly-forecastB | Get hourly weather forecast for up to 48 hours |
| get-daily-forecastC | Get daily weather forecast for up to 8 days |
| get-minutely-forecastC | Get minute-by-minute precipitation forecast for next hour |
| get-weather-alertsC | Get active weather alerts and warnings |
| get-current-air-pollutionC | Get current air quality data |
| get-location-infoB | Get location information from coordinates (reverse geocoding) |
| get-onecall-weatherC | Get comprehensive weather data (current + 7-day forecast) |
| get-air-pollutionC | Get air quality index and pollution data |
| geocode-locationC | Convert location name to coordinates or vice versa |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| OpenWeatherMap API Documentation |
TDQS
Scored across 11 tools
Most tools are clearly distinct, covering specific weather and location data types like current weather, forecasts, air pollution, and geocoding. However, there is some overlap between 'get-daily-forecast', 'get-weather-forecast', and 'get-onecall-weather', which could cause confusion as they all provide forecast data with different scopes or formats.
All tool names follow a consistent 'get-' or 'geocode-' prefix pattern with descriptive kebab-case nouns, such as 'get-current-weather' and 'geocode-location'. This uniformity makes the tools predictable and easy to understand at a glance.
With 11 tools, the server is well-scoped for an OpenWeatherMap integration, covering a comprehensive range of weather and location services. Each tool serves a distinct purpose, from basic weather queries to specialized forecasts and alerts, without feeling bloated or sparse.
The tool set provides complete coverage for weather and location data, including current conditions, various forecast types (minutely, hourly, daily), air pollution, alerts, and geocoding. There are no obvious gaps, enabling agents to handle a wide range of weather-related queries effectively.