Weather Forecast MCP 5fbc5ffb

MCP地图位置

提供方 adelie-ai

地图位置 未标注 无需鉴权 社区 / 第三方 Claude DesktopClaude

一个为LLM应用提供天气预测工具的MCP服务器,包括地理编码、当前天气状况、天气预报和警报等功能。

一句话选型结论

按资料字段整理

Weather Forecast MCP 5fbc5ffb 属于地图位置类 MCP 服务器,传输方式未标注,无需鉴权,可直接接入 Claude Desktop、Claude,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类地图位置 传输方式未标注 鉴权无需鉴权 部署方式未标注
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 4 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

地图位置
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量4暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

天气预测Rust本地部署地理编码MCP服务器LLM应用

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 4 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
地址与路线

查地址、算路线、找附近地点。

位置检索

按区域筛门店、站点与设施。

地理数据

拉取经纬度、行政区等地理信息。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 4 个工具,职责相对集中,接入后不容易误操作。
  • 已适配 Claude Desktop、Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在地图位置场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Weather Forecast MCP 5fbc5ffb当前 4 未标注 未标注 无 2026-05-17
MCP Server C2f246e3 20 stdio · 本地进程 本地部署 有 2026-05-17
OpenStreetMap MCP Server 12 stdio · 本地进程 本地部署 有 2026-05-18
Baidu Maps 10 stdio · 本地进程 本地部署 有 2026-05-17
Google Maps (google-maps-aa2563d3) 7 未标注 未标注 无 2026-05-17
generative-ai 未标注 stdio · 本地进程 本地部署 有 2026-04-17

服务器档案

地图位置
字段来自项目仓库与公开索引,中文说明由本站标注
提供方adelie-ai上游标注的维护方 adelie-ai
分类地图位置本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

5.6 KB
来自项目仓库与上游目录的原文,未做删改

weather-forecast-mcp

A Model Context Protocol (MCP) server that provides weather forecast tools for LLM applications. Built in Rust, it exposes geocoding, current conditions, forecasts, and alerts as callable MCP tools over stdio or WebSocket transports.

All weather data comes from the free Open-Meteo API — no API keys required.

Tools

Tool Description
weather_geocode Convert location names to geographic coordinates
weather_get_current Get current weather conditions for a lat/lon
weather_get_forecast Get daily or hourly forecasts (up to 16 days)
weather_get_alerts Get weather alerts for a location (placeholder for live provider integration)

All tools support configurable temperature units (celsius/fahrenheit) and wind speed units (km/h, m/s, mph, knots).

Building```bash

cargo build --release


## Usage

### Stdio transport (recommended for local/IDE use)```bash
weather-forecast-mcp serve --mode stdio

The server reads JSON-RPC messages from stdin and writes responses to stdout. It auto-detects newline-delimited JSON or Content-Length framing.

WebSocket transport```bash

weather-forecast-mcp serve --mode websocket --host 0.0.0.0 --port 8080


Connects via WebSocket at `ws://:/ws`.

### Claude Desktop configuration

Add to your Claude Desktop MCP config:```json
{
  "mcpServers": {
    "weather": {
      "command": "/path/to/weather-forecast-mcp",
      "args": ["serve", "--mode", "stdio"]
    }
  }
}

VS Code configuration

Add to your VS Code MCP settings (.vscode/mcp.json):```json
{
"servers": {
"weather": {
"command": "/path/to/weather-forecast-mcp",
"args": ["serve", "--mode", "stdio"]
}
}
}


## Logging

`mcp-core`'s `run` installs the process subscriber; this crate calls nothing to get it.
Logs go to stderr, never stdout -- the stdio transport frames JSON-RPC on stdout, and one
log line there would corrupt the protocol stream. `RUST_LOG` sets the level (default
`info`); see `mcp-core`'s own README for the full level contract, the request/tool-call
spans, and the standard `OTEL_*` environment variables.

A location -- a place name or a pair of coordinates -- is what every tool argument here
carries, and it is content: it says where a person is or cares about. It stays at DEBUG
only, never INFO, never a span field, whether it names a real place or is coarsened to a
city or a region.

What this server adds on top of what it inherits:

- A `debug!` line before each outbound Open-Meteo request (`weather_geocode`'s search, and
  the shared `/v1/forecast` call `weather_get_current` and `weather_get_forecast` both
  make), carrying the location. `RUST_LOG=debug` is what it takes to see it.
- `weather.upstream_failure`, a counter labelled `tool` and a bounded `reason`
  (`network`, `api_error`, or `malformed_response`), for a fault reaching outward. A "no
  match" answer from the geocoder and a coordinate or unit rejected by local validation are
  declines, not faults, and are not counted here.
- `mcp-core` already records a tool-call counter and a latency histogram by tool and
  outcome (`mcp.tools.call`, `mcp.tools.call.duration`); this server does not duplicate
  them.

### The `otel` feature

Off by default. A pure passthrough -- `weather-forecast-mcp -> mcp-core ->
adelie-telemetry` -- so this crate takes no direct dependency on `adelie-telemetry` or on
any opentelemetry crate. With the feature off, `cargo tree` resolves no opentelemetry
crate at all.```bash
cargo build --features otel
OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318 ./target/debug/weather-forecast-mcp serve --mode stdio

Pointing at a different upstream

--geocoding-base-url / WEATHER_GEOCODING_BASE_URL and --forecast-base-url /
WEATHER_FORECAST_BASE_URL override the two Open-Meteo hosts (default
https://geocoding-api.open-meteo.com and https://api.open-meteo.com). Open-Meteo is
the only backend this server speaks, so a normal deployment never sets these; they exist
so a test can point a compiled binary at a local mock server instead of a live service.

Testing```bash

just check # default features: fmt, lint, build, test
just check-otel # the same, built with --features otel
just check-all # both -- what the pre-push hook runs
just test-integration # additionally launch the live Open-Meteo API


Network-dependent integration tests in `tests/mcp_stdio_suite.rs` are gated behind
`RUN_NETWORK_TESTS=1` so the default suite is deterministic and offline. The
`tests/telemetry_*.rs` files are the telemetry acceptance suite: that a default build
resolves no opentelemetry crate, that stdout carries only JSON-RPC at `RUST_LOG=trace`,
and that no location -- from any registered tool, on both its success and its failure
path -- reaches an INFO line or a span field. Those tests drive a local mock of both
Open-Meteo endpoints (`tests/support::start_mock_server`), never the real API.

## Project structure```
src/
├── main.rs            Entry point, CLI, JSON-RPC routing, WebSocket transport
├── server.rs          MCP server state and protocol handling
├── tools.rs           Tool registry and execution dispatcher
├── transport.rs       Stdio transport with auto-detected framing
├── error.rs           Structured error types
└── operations/
    ├── current.rs     Current weather conditions
    ├── forecast.rs    Daily/hourly forecasts
    ├── geocode.rs     Location geocoding
    └── alerts.rs      Weather alerts (placeholder)

License

Apache-2.0

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Weather Forecast MCP 5fbc5ffb 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Weather Forecast MCP 5fbc5ffb 怎么在 Claude Desktop、Claude 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Weather Forecast MCP 5fbc5ffb 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Weather Forecast MCP 5fbc5ffb 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Weather Forecast MCP 5fbc5ffb 支持哪些客户端?

资料标注支持 Claude Desktop、Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Weather Forecast MCP 5fbc5ffb 能提供哪些能力?

资料显示约 4 个工具;能力标签包括 地理编码、Rust、Claude、LLM应用。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。