OpenWeatherMap MCP. Get global weather, pollution, and forecast data instantly.
OpenWeatherMap gives your agent instant access to global meteorological data, covering current conditions, 5-day forecasts, and air quality metrics for any location worldwide. It handles everything from converting city names to precise coordinates to running detailed pollution reports using tools like `get_air_pollution`. Stop relying on patchy weather websites; connect this MCP to your AI client for reliable, real-time environmental data right where you work.
Give Claude and any AI agent real-world access
Retrieve current temperature, wind speed, and atmospheric descriptions for any specified location.
Pull multi-day forecasts or detailed hourly projections spanning multiple days to plan logistics.
Get real-time pollution data, including specific metrics like PM2.5 and CO, for environmental assessments.
Translate a place name or zip code into latitude and longitude pairs for precise targeting.
Reverse engineer a geographical coordinate pair back into a readable city or place name.
Ask an AI about this
Waiting for input…
What AI agents can do with OpenWeatherMap MCP with 6 Tools
These tools allow you to pull current weather conditions, generate long-term forecasts, monitor pollution levels, and convert between city names and coordinates.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using OpenWeatherMap MCPGet Air Pollution
Retrieves current air pollution data, including metrics like PM2.5 and CO.
Get Current Weather
Gets the live weather conditions for a specified city or coordinate pair.
Direct Geocoding
Converts place names, like 'New York City', into precise latitude and longitude...
Get Forecast
Pulls a detailed 5-day forecast with three-hour interval predictions.
Get Onecall
Accesses comprehensive weather data, including hourly and daily projections for up...
Reverse Geocoding
Takes a coordinate pair and converts it back into a human-readable city name or location identifier.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with OpenWeatherMap, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by OpenWeatherMap. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Checking conditions requires jumping through too many hoops.
Right now, if you want a comprehensive view of an area—say, checking air quality and predicting rain for next week—you open one site for the forecast, another for pollution data, and maybe a third to confirm the coordinates. You copy-paste location names into different fields, wait for multiple pages to load, and then piece together what you actually need.
With this MCP integrated via Vinkius, your AI client handles all that complexity behind the scenes. You ask one simple question—like, 'What's the air quality in Miami next Tuesday?'—and it returns a clean answer built from multiple data sources, saving you hours of manual clicking and cross-referencing.
OpenWeatherMap MCP: Location Data on Demand
Manual location checks involve guessing if the system accepts a city name or requires coordinates. You might spend time converting 'Paris, France' into Lat/Long pairs just to ask about the current temperature.
This MCP makes that conversion invisible. By using tools like `direct_geocoding` and `reverse_geocoding`, your agent handles the messy geometry work automatically. The result is that you get immediate, validated weather data for any location without ever touching a coordinate pair yourself.
What OpenWeatherMap MCP does for your AI
Need to know what the weather's doing or if the air is breathable in a specific spot? This connector hands your AI agent global meteorological tools. You can pull live readings—like temperature and humidity—for any city or coordinate using get_current_weather. If you’re planning something bigger, like a multi-day trip or an industrial site inspection, you've got the 5-day forecast via get_forecast or even longer projections through get_onecall.
It also handles air quality monitoring with get_air_pollution, giving you hard numbers on things like PM2.5 and ozone levels. Need to figure out coordinates? You can convert city names into precise locations using direct_geocoding or map back from coordinates to a readable city name using reverse_geocoding. When you connect this MCP through Vinkius, your AI client instantly accesses all these services without needing separate API keys or messy manual lookups.
019e38cf-685b-714b-b609-44b8ef5b5cb8 How to set up OpenWeatherMap MCP
The bottom line is your AI agent speaks directly to global weather services, getting you actionable data without leaving your workflow.
Subscribe to this MCP and enter your OpenWeatherMap API Key within the Vinkius catalog.
Ask your AI client—whether it's Claude, Cursor, or any compatible agent—to find data for a specific location or time frame.
The MCP runs the necessary tool (like get_current_weather or get_air_pollution) and sends back structured, usable weather or environmental metrics.
Who uses OpenWeatherMap MCP
This MCP is essential for anyone whose job depends on accurate location and environmental context. If you're an operations lead who needs to reschedule a shipment because of unexpected fog, or a researcher tracking pollution spikes over time, this is for you.
Checks weather conditions along planned routes using get_forecast to avoid delays caused by storms or poor visibility.
Runs get_air_pollution at several coordinates to map out pollution hotspots and track pollutant changes.
Uses direct_geocoding and reverse_geocoding to validate property addresses or determine the closest city center from a given plot of land.
Benefits of connecting OpenWeatherMap MCP
Don't rely on manually checking multiple websites. You can use get_current_weather to get live temperature and wind speed in one prompt.
Need long-term planning? Use get_onecall to pull detailed weather patterns for eight days, letting you plan complex logistics cycles.
For environmental monitoring, running get_air_pollution gives immediate, quantitative data on pollutants like PM2.5 and CO levels.
Stop guessing locations. Use direct_geocoding to turn a vague city name into exact coordinates for any API call.
Need the reverse? If you only have GPS coordinates, use reverse_geocoding to identify the nearest major city name.
OpenWeatherMap MCP use cases
Optimizing multi-city travel routes
A travel coordinator needs to check weather for a tour spanning four cities over two weeks. They prompt their agent, which uses get_forecast and get_onecall sequentially, providing a consolidated report that flags periods of expected rain or high winds.
Assessing industrial site safety
An engineer needs to know if construction workers are exposed to bad air quality. They prompt the agent with coordinates and run get_air_pollution, instantly checking for dangerous levels of ozone or PM10.
Validating property data
A real estate analyst receives a list of vague addresses. Instead of manual lookups, they use the agent to run direct_geocoding on every entry, converting them all into standardized coordinates for mapping.
Building location-aware applications
A developer builds a service that displays weather. Instead of hardcoding locations, they use the agent to run reverse_geocoding on user-provided GPS data, making their application universally adaptable.
OpenWeatherMap MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Assuming location services are universal
Trying to check a location by just typing 'near the river' into an agent and expecting it to know the coordinates.
You must first use direct_geocoding on a specific city or zip code. If you have GPS points, use reverse_geocoding to confirm the nearest major place name.
Mixing up forecast types
Using get_current_weather when you actually need to know what will happen tomorrow.
If you want future data, use either get_forecast for the 5-day view or get_onecall for maximum detail across multiple days.
Ignoring pollution metrics
Only checking if it's 'rainy' and ignoring key environmental risks like high PM2.5 levels in the city.
Always include get_air_pollution when assessing urban or industrial areas, as weather doesn't cover air quality.
When to use OpenWeatherMap MCP
Use this MCP if your problem requires knowing what an external natural force—weather, pollution, or physical location coordinates—is doing. This is for predictive modeling (using get_onecall) or real-time environmental assessment (using get_air_pollution). Don't use it if you just need to look up a simple piece of data that doesn't change with time, like finding the population count of a zip code; for that, use a dedicated database lookup MCP. If your core task is manipulating structured text or executing complex business logic unrelated to geography, this isn't what you need.
Frequently asked questions about OpenWeatherMap MCP
How do I check multiple locations with OpenWeatherMap MCP? +
You ask your agent to process multiple coordinates or city names in one prompt. The agent will run the required tools, such as get_current_weather, for every location you specify.
Is OpenWeatherMap MCP better than a simple API call? +
Yes. Since this is an MCP, your AI client manages all the tool calling, error handling, and data formatting automatically, giving you clean text answers instead of raw JSON dumps.
Can I use OpenWeatherMap MCP to check historical weather? +
The primary focus is real-time or forecast data. For specific historical records, you might need a different time-series database tool, but we can get current conditions using get_current_weather.
What if my location name is vague for OpenWeatherMap MCP? +
You should use direct_geocoding first. This ensures the agent converts your fuzzy input (like 'the downtown area') into precise coordinates before attempting to get weather data.
Does OpenWeatherMap MCP handle pollution for different pollutants? +
Yes, when you run get_air_pollution, it reports on several key metrics simultaneously, including PM2.5, PM10, and Ozone levels.