mcp-openweather

MCP OpenWeather is a weather service that integrates with the MCP platform to provide current weather conditions and a 5-day forecast using the OpenWeatherMap API. It supports configurable units (Celsius, Fahrenheit, Kelvin) and multiple languages, making it useful for chat assistants and automated agents that need weather data. The server runs as a standalone binary and exposes a weather tool via the MCP protocol, which you can invoke through the MCP front-end or client tooling. To use it, ensure your environment provides a valid OpenWeatherMap API key and point the MCP server to run the mcp-openweather binary with the required environment variable.

Prerequisites:

• Go 1.20+ installed for building from source
• An OpenWeatherMap API key
• A working MCP environment where you can deploy the service (e.g., Claude, Claude Desktop, or your own MCP setup)

Installation steps:

1. Obtain an API key from https://openweathermap.org/api and note it down.
2. Clone the repository: git clone https://github.com/mschneider82/mcp-openweather.git cd mcp-openweather
3. Build the binary: go build -o mcp-openweather
4. Run the service locally (example): export OWM_API_KEY=your_api_key_here ./mcp-openweather
5. If you are integrating via Smithery, you can install via: npx -y @smithery/cli install @mschneider82/mcp-openweather --client claude
6. Configure the MCP integration (see the mcp_config section below) to point to the built binary and provide the API key via environment variable.

Tips and common considerations:

• Ensure OWM_API_KEY is set in the environment where the binary runs.
• The MCP configuration expects the binary path and, if needed, environment variables as shown in the example: "env": { "OWM_API_KEY": "PUT_API_KEY_HERE" }.
• Units and language can be controlled via the MCP tool parameters (city, units, lang).
• If you encounter network or API rate issues, verify API key validity and consider caching results if your MCP client supports it.
• For Smithery installation, the CLI will fetch the service and configure the client accordingly; ensure the designated client (e.g., claude) is installed on your system.
• The example response in the README demonstrates the structure of responses you can expect from the tool.