The README is candid that this follows the MCP documentation's own weather demo, and the shape shows it: two tools, one data source, no abstraction layer. That is a fair trade when the requirement is Chinese city weather specifically, since the underlying API covers cities that global weather services describe thinly. Bring your own key rather than reusing the one printed in the setup snippet.
A small MCP server over the QWeather API, covering cities in mainland China, Hong Kong, Macau and Taiwan. You ask by Chinese city name; it resolves the city and returns either a forecast or the active meteorological warnings.
- `get-weather-forecast` takes a `city` name and an optional `days` count from 1 to 7, defaulting to 3
- Each forecast day carries high and low temperature, daytime and night-time conditions, wind direction and force, humidity, precipitation, pressure, visibility, the UV index, and sunrise and sunset times
- `get-weather-warnings` takes a `city` and returns the active alerts with title, type, severity level, affected area, start time and full text
- City coverage runs from the four municipalities down to county-level cities
A free API key from the QWeather developer platform. The project is Node.js: `npm install` then `npm run build`, after which the client launches the compiled `build/index.js` with `node`. The package is `china-weather-mcp`, version 1.0.0. Errors are handled for an invalid or missing key, an unknown city name, network failure, and API request limits.
Build from source — clone the repository and build it, then point your client at the binary