Open Meteo Weather vs Tomorrow Io
A side-by-side look at the Open Meteo Weather and Tomorrow Io MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Open Meteo Weather for environment & nature work as a local process; choose Tomorrow Io 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 Open Meteo Weather when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
Choose Tomorrow Io when
- You need dedicated capabilities in the Environment & Nature domain.
- You prefer a local stdio subprocess transport.
- You want tools like
realtime, forecast.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Environment & Nature | Environment & Nature |
| Quality signal | 37/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Open Meteo Weather | View Tomorrow Io |
Tools & capabilities
Open Meteo Weather tools
No tool names declared yet. Check the project README from the listing page.
Tomorrow Io tools 2
realtimeGet current/real-time weather conditions for a location — temperature, feels-like, humidity, wind, precipitation probability, cloud cover, UV index, and visibility. Location can be "lat,lon" coordinates or a city name. Example: realtime({ location: "new york", units: "imperial" }) or realtime({ loc…forecastGet a daily or hourly weather forecast for a location. Returns a list of forecast periods with conditions, temperatures, precipitation probability, and wind. Location can be "lat,lon" coordinates or a city name. Example: forecast({ location: "london", timestep: "1d", units: "metric" })
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.
Open Meteo Weather
{
"mcpServers": {
"open-meteo-weather": {
"command": "uvx",
"args": [
"setup"
]
}
}
}
Tomorrow Io
{
"mcpServers": {
"tomorrow-io": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-tomorrow-io"
]
}
}
}
Frequently asked questions
Open Meteo Weather is categorized under Environment & Nature and uses a local stdio subprocess. Tomorrow Io belongs to Environment & Nature and uses a local stdio subprocess. Pick Open Meteo Weather for environment & nature work and Tomorrow Io 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.
Open Meteo Weather has no declared pricing — check the project's own site. Tomorrow Io 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 open-meteo-weather and tomorrow-io as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Open Meteo Weather has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Tomorrow Io has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.