Qweather1 MCP Server
# qweather-mcp [](https://mseep.ai/app/ae24a36c-f029-49b3-9c42-fc111021add0) [
[![MseeP.ai Security Assessment.
What you get
Recommended: Install automatically for Claude Desktop using Smithery:
Setting it up
The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Configuration and credentials
You will need 6 environment variables: QWEATHER_API_BASE, QWEATHER_PROJECT_ID, QWEATHER_KEY_ID, QWEATHER_PRIVATE_KEY_PATH, QWEATHER_API_KEY, QWEATHER_PRIVATE_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Before you rely on it
- It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
- Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
- MCP clients confirm each tool call by default. Leave that on until you have watched what the qweather1 mcp server does with a few real requests.
Choosing this one
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by overstarry; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
How to install the Qweather1 MCP server
JSON config example:
```json
{
"mcpServers": {
"qweather": {
"command": "npx",
"args": ["-y", "qweather-mcp"],
"env": {
"QWEATHER_API_BASE": "<your-api-url>",
"QWEATHER_API_KEY": "<your-api-key>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
Configuration
| Variable | Description | Required |
|---|---|---|
| QWEATHER_API_BASE | Configuration value read at startup. | Optional |
| QWEATHER_PROJECT_ID | Configuration value read at startup. | Optional |
| QWEATHER_KEY_ID | Credential the server authenticates with. | Yes |
| QWEATHER_PRIVATE_KEY_PATH | Credential the server authenticates with. | Yes |
| QWEATHER_API_KEY | Credential the server authenticates with. | Yes |
| QWEATHER_PRIVATE_KEY | Credential the server authenticates with. | Yes |
Frequently asked questions
Alternatives to the Qweather1 MCP server
Memory
OfficialA knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Context7
OfficialKill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Notion
OfficialYour workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Sequential Thinking
OfficialA structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Serena
OfficialSymbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Obsidian
Chat with your second brain — search, read and write vault notes through the Local REST API.