A side-by-side look at the Met No and Weather MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Met No for environment & nature work as a local process; choose Weather MCP Server 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 Met No when
You need dedicated capabilities in the Environment & Nature domain.
No tool names declared yet. Check the project README from the listing page.
Weather MCP Server 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.
Met No is categorized under Environment & Nature and uses a local stdio subprocess. Weather MCP Server belongs to Environment & Nature and uses a local stdio subprocess. Pick Met No for environment & nature work and Weather MCP Server 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.
Met No has no declared pricing — check the project's own site. Weather MCP Server 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 met-no and weather-mcp-server-3 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Met No has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Weather MCP Server has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.