Openweather vs Weatherapi — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Openweather vs Weatherapi
In-depth architectural comparison of the Openweather and Weatherapi MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Openweather
Developer Tools · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Weatherapi
Developer Tools · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Openweather if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Weatherapi if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
O
Choose Openweather when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Get the current weather for a city or coordinates: temperature, "feels like", conditions, humidity, wind speed, and cloud cover. Example: current_weather({ city: "London", units: "metric" })
forecast
Get a multi-step weather forecast (3-hour intervals) for a city or coordinates: temperature, conditions, wind speed, and precipitation probability over time. Example: forecast({ city: "Tokyo", count: 8 })
air_quality
Get the current air quality for a set of coordinates: an air quality index (AQI, 1=Good to 5=Very Poor) plus pollutant component concentrations (CO, NO2, O3, PM2.5, PM10, etc.). Example: air_quality({ lat: 51.5, lon: -0.12 })
geocode
Resolve a place name (city, optionally with state/country) to geographic coordinates (latitude/longitude). Useful before calling air_quality, which needs lat/lon. Example: geocode({ query: "Paris", limit: 5 })
Weatherapi Tools (4)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Openweather is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Weatherapi belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Openweather when you need capabilities focused on developer tools and Weatherapi when you require tools for developer tools.
Get current/real-time weather for a location, including temperature, condition, humidity, wind, UV, and air quality (AQI). Location can be a city name, "lat,lon", zip code, or IATA airport code. Example: current({ q: "London", aqi: true }).
forecast
Get a multi-day weather forecast for a location: daily high/low temperature, condition, chance of rain, total precipitation, and sunrise/sunset times. Up to 10 days. Example: forecast({ q: "Tokyo", days: 5 }).
astronomy
Get astronomy data for a location and date: sunrise, sunset, moonrise, moonset, moon phase, and moon illumination. Example: astronomy({ q: "Reykjavik", dt: "2026-06-21" }).
marine
Get marine/ocean conditions forecast for a coastal location: significant wave height, swell height, water temperature, and wind. Up to 7 days, sampled every 6 hours. Example: marine({ q: "33.7,-118.4", days: 2 }).