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