A side-by-side look at the Au Weather MCP and Open Meteo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Au Weather MCP for environment & nature work as a local process; choose Open Meteo for environment & nature as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Au Weather MCP when
You need dedicated capabilities in the Environment & Nature domain.
No tool names declared yet. Check the project README from the listing page.
Open Meteo tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Au Weather MCP is categorized under Environment & Nature and uses a local stdio subprocess. Open Meteo belongs to Environment & Nature and uses a local stdio subprocess. Pick Au Weather MCP for environment & nature work and Open Meteo for environment & nature.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Au Weather MCP has no declared pricing — check the project's own site. Open Meteo has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add au-weather-mcp and open-meteo as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Au Weather MCP has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Open Meteo has 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.