The weather-mcp project describes an MCP server with 17 tools covering forecasts, alerts, air quality, radar, rivers, marine conditions, wildfires and historical observations. It says it uses free public services such as NOAA and Open-Meteo, with no account or API key required for its core tools.
This fits a small, testable personal-agent project: give an assistant a real external capability and measure whether it retrieves trustworthy structured information instead of improvising a forecast. It could also be a reference design for adding tool interfaces to HomeControl or another local service.
What to do: Inspect the README, licensing and dependency footprint first. If it looks appropriate, test one read-only weather question in a disposable MCP client before giving it a permanent place in OpenClaw or any production automation.
Before you go further: An open-source README is not an independent security audit. Review what the package installs and what network calls it makes before running third-party code on a Mac that hosts personal services.