
Recommended: Install automatically for Claude Desktop using Smithery:
Recommended: Install automatically for Claude Desktop using Smithery:
·
English | 简体中文
MCP server for QWeather API, providing comprehensive weather information query capabilities through Model Context Protocol (MCP).
Recommended: Install automatically for Claude Desktop using Smithery:
npx -y @smithery/cli install @overstarry/qweather-mcp --client claude# stdio server
npx -y qweather-mcpQWeather has announced that API Key authentication will be deprecated in 2027 and recommends migrating to JWT (EdDSA + Ed25519). Generate an Ed25519 key pair, upload the public key to the QWeather console, and configure:
QWEATHER_API_BASE=https://<your-host>.qweatherapi.com
QWEATHER_PROJECT_ID=<project-id>
QWEATHER_KEY_ID=<credential-id>
# Either pass the PEM path…
QWEATHER_PRIVATE_KEY_PATH=/path/to/ed25519-private.pem
# …or the PEM content directly (newlines preserved)
# QWEATHER_PRIVATE_KEY="-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----"If both QWEATHER_PRIVATE_KEY_PATH and QWEATHER_PRIVATE_KEY are provided, the path takes precedence. For QWEATHER_PRIVATE_KEY, the literal two-character sequence \n is auto-converted to real newlines, so the single-line form above works in shells, .env files, and JSON configs.
JSON config example:
{
"mcpServers": {
"qweather": {
"command": "npx",
"args": ["-y", "qweather-mcp"],
"env": {
"QWEATHER_API_BASE": "https://<your-host>.qweatherapi.com",
"QWEATHER_PROJECT_ID": "<project-id>",
"QWEATHER_KEY_ID": "<credential-id>",
"QWEATHER_PRIVATE_KEY_PATH": "/path/to/ed25519-private.pem"
}
}
}
}JWT details: tokens are signed with alg=EdDSA, iat is back-dated 30s to tolerate clock skew, exp = iat + 900s (15 min, well under QWeather's 24h cap), and tokens are cached and reused until ~30s before expiry. See the official authentication docs.
QWEATHER_API_BASE=https://api.qweather.com
QWEATHER_API_KEY=<your-api-key>JSON config example:
{
"mcpServers": {
"qweather": {
"command": "npx",
"args": ["-y", "qweather-mcp"],
"env": {
"QWEATHER_API_BASE": "<your-api-url>",
"QWEATHER_API_KEY": "<your-api-key>"
}
}
}
}| Env vars present | Mode |
|---|---|
Full JWT vars (QWEATHER_PROJECT_ID + QWEATHER_KEY_ID + QWEATHER_PRIVATE_KEY[_PATH]) | JWT (wins even if QWEATHER_API_KEY is also set) |
Full JWT vars + QWEATHER_API_KEY | JWT (API Key is ignored) |
Partial JWT vars + QWEATHER_API_KEY | API Key, with a startup warning to stderr |
| Partial JWT vars only | startup error |
QWEATHER_API_KEY only | API Key |
| neither | startup error |
The active mode is logged to stderr at startup, e.g. Weather MCP Server running on stdio (auth: JWT/EdDSA).
Get current weather information for a specified location.
Get weather forecast information for a specified location with customizable forecast days:
Forecast data includes:
Provides minute-by-minute precipitation forecast for the next 2 hours, including:
Provides hourly weather forecasts for 24, 72, or 168 hours, including:
Provides real-time weather warning information, including:
Provides weather life indices information, supporting various index types:
Provides real-time air quality data, including:
Provides hourly air quality forecast for the next 24 hours:
Provides air quality forecast for the next 3 days:
Issues and improvements are welcome! Please check our contribution guidelines.
MIT
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add qweather -- npx -y qweather-mcp{
"mcpServers": {
"qweather": {
"env": {
"QWEATHER_KEY_ID": "",
"QWEATHER_API_BASE": "",
"QWEATHER_PROJECT_ID": "",
"QWEATHER_PRIVATE_KEY_PATH": ""
},
"args": [
"-y",
"qweather-mcp"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"qweather","env":{"QWEATHER_KEY_ID":"","QWEATHER_API_BASE":"","QWEATHER_PROJECT_ID":"","QWEATHER_PRIVATE_KEY_PATH":""},"args":["-y","qweather-mcp"],"command":"npx"}'[mcp_servers.qweather]
command = "npx"
args = ["-y", "qweather-mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/qweather-mcp to learn what the "Qweather Mcp" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
npx -y @smithery/cli install @overstarry/qweather-mcp --client claude
npx -y qweather-mcpThis server runs locally, so we can't read its tool list over the web yet.
We could not run this server: its npm package has not answered in our offline sandbox, which usually means it needs an API key or other configuration to start. The four checks that need a live server are left out, and the grade tops out at B until we can read its tools.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/qweather-mcp)Nothing comparable is listed yet.
No tagged releases on record.
Connect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "qweather-mcp" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.