Weather Data MCP Server

io.github.dgahagan由 GitHub 账号 dgahagan 发布v1.35.7更新于 Oct 30, 2026

17 weather tools, no API keys: forecasts, alerts, air quality, marine, radar, lightning, wildfires

概览

AI 生成的概览

本地 MCP 服务器,让助手无需 API 密钥即可获取全球各地的天气数据,包括实况、预报、预警和空气质量等。

可以做什么
  • 一次获取某地的综合天气概况:实况、预报、预警,可选空气质量与雷电信息
  • 查询未来天气预报,美国地区使用 NOAA,国际地区使用 Open-Meteo
  • 读取某地最新的实况观测数据
  • 列出生效中的天气预警、观察、警告与提示,覆盖多个国家的官方预警源
  • 按名称搜索地点并返回坐标,用于区分同名地点
  • 检查上游天气服务是否可达,并查看各服务状态
适用场景
适合让助手回答日常天气问题,例如现在天气如何、本周走势、是否有预警,或在户外活动前查看天气状况,且不想注册天气 API 账号时使用。
运行要求
以 stdio 方式作为本地进程运行,从 npm 包安装;需要 Node.js 以及访问公共天气与地理编码服务的出网连接。未声明任何账号、API 密钥、环境变量或请求头。
安装前请注意
依赖第三方公共服务(NOAA、Open-Meteo、Nominatim 及各国预警源),结果受其可用性影响,美国以外覆盖不均。地点名称会被发送到这些外部服务进行地理编码。注册表描述称有 17 个工具,而清单只列出 6 个。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Weather Data MCP Server,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

工具

6

get_weather_summary

Get a combined weather overview for a location in a SINGLE call — current conditions, forecast and alerts, optionally air quality and lightning. Best for broad questions like "What's the weather like in Seattle?", "Is it safe to hike today?", or "Give me a weather rundown". For a single specific data product (just the forecast, just alerts, etc.), call that specialized tool directly. Sections that are unavailable for a location (e.g. alerts in a country not yet covered) are noted rather than failing the whole summary.

输入参数daysunitsdetailsourceincludelatitudecity_namelongitudetime_formatdistance_unitlocation_namepressure_unit另有 3 个

get_forecast

Get future weather forecast for a location. Use this for upcoming weather predictions (e.g., "tomorrow", "this week", "next 7 days", "hourly forecast"). Automatically selects the best data source: NOAA for US locations (more detailed), Open-Meteo for international locations. For current weather, use get_current_conditions. For past weather, use get_historical_weather.

输入参数daysunitsdetailsourcelatitudecity_namelongitudegranularitytime_formatdistance_unitlocation_namepressure_unit另有 9 个

get_current_conditions

Get the most recent weather observation for a location. Use this for current weather or when asking about "today's weather", "right now", or recent conditions without a specific historical date range. Returns NOAA station observations for US locations and Open-Meteo model data for international locations. Automatically includes frostbite-risk and heat-stress (WBGT) context when conditions are extreme. For specific past dates or date ranges, use get_historical_weather instead.

输入参数unitssourcelatitudecity_namelongitudetime_formatdistance_unitlocation_namepressure_unitinclude_normalswind_speed_unittemperature_unit另有 2 个

get_alerts

Get active weather alerts, watches, warnings, and advisories for a location. Coverage: the United States (NOAA), Canada (Environment and Climate Change Canada), European MeteoAlarm member countries, Japan (JMA), and the official national CAP feeds of India (NDMA SACHET), the Philippines (PAGASA) and Indonesia (BMKG). All of the above are keyless. With an optional `GOOGLE_WEATHER_API_KEY`, official alerts are also available for ~45+ more territories (Australia, Brazil, Mexico, and others) via the Google Weather API. Use this for safety-critical weather information when asked about "any alerts?", "weather warnings?", "is it safe?", "dangerous weather?", or "weather watches?". For forecast data, use get_forecast instead.

输入参数detaillatitudecity_namelongitudeactive_onlylocation_name

search_location

Search for locations by name and get their coordinates. Uses Nominatim (OpenStreetMap) for coverage of cities, towns, villages and hamlets worldwide. The weather tools geocode city_name themselves, so use this to disambiguate an ambiguous place name or to show the candidate matches (e.g., "Springfield", "San Francisco, CA", "Small Village, County") — not as a required first step before a weather call.

输入参数limitquery必填

check_service_status

Check whether the upstream weather APIs (NOAA, Open-Meteo) are reachable. Call this after any weather tool returns an error, or before a batch of requests. Returns per-service status and links to the official status pages.

无需输入参数。

版本历史

39
  1. v1.35.7最新Oct 30, 2026
  2. v1.35.5Oct 23, 2026
  3. v1.35.4Oct 22, 2026
  4. v1.35.3Oct 21, 2026
  5. v1.35.2Oct 21, 2026
  6. v1.35.1Oct 20, 2026
  7. v1.35.0Oct 19, 2026
  8. v1.34.8Oct 16, 2026
  9. v1.34.6Oct 15, 2026
  10. v1.34.5Oct 15, 2026
  11. v1.34.4Oct 4, 2026
  12. v1.34.3Oct 3, 2026
  13. v1.34.2Oct 3, 2026
  14. v1.34.1Oct 2, 2026
  15. v1.34.0Oct 2, 2026
  16. v1.33.23Oct 1, 2026
  17. v1.33.22Oct 1, 2026
  18. v1.33.20Oct 1, 2026
  19. v1.33.18Sep 30, 2026
  20. v1.33.16Sep 30, 2026
  21. v1.33.15Sep 30, 2026
  22. v1.33.13Sep 29, 2026
  23. v1.33.11Sep 29, 2026
  24. v1.33.10Sep 29, 2026
  25. v1.33.8Sep 28, 2026
  26. v1.33.7Sep 28, 2026
  27. v1.33.6Sep 27, 2026
  28. v1.33.4Sep 27, 2026
  29. v1.33.2Sep 27, 2026
  30. v1.33.1Sep 26, 2026
  31. v1.33.0Sep 25, 2026
  32. v1.32.1Sep 25, 2026
  33. v1.31.5Sep 24, 2026
  34. v1.31.4Sep 23, 2026
  35. v1.31.3Sep 19, 2026
  36. v1.31.2Sep 18, 2026
  37. v1.31.0Sep 18, 2026
  38. v1.30.1Sep 18, 2026
  39. v1.30.0Sep 16, 2026

评分

已满足适用检查项的 65%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。