4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
OpenWeatherMap MCP Server

Bring Meteorology
to CrewAI

Learn how to connect OpenWeatherMap to CrewAI and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Direct GeocodingGet Air PollutionGet Current WeatherGet ForecastGet OnecallReverse Geocoding

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
OpenWeatherMap

What is the OpenWeatherMap MCP Server?

Connect OpenWeatherMap to your AI agent to get instant access to global meteorological data. Whether you're planning travel, monitoring environmental conditions, or building weather-aware automations, this server provides the precise data you need.

What you can do

  • Current Conditions — Get live temperature, humidity, wind speed, and weather descriptions for any city or coordinate via get_current_weather.
  • Extended Forecasts — Access 5-day/3-hour forecasts with get_forecast or use the One Call 3.0 API for 48-hour hourly and 8-day daily projections via get_onecall.
  • Air Quality Monitoring — Retrieve real-time pollution data including PM2.5, PM10, CO, and Ozone levels using get_air_pollution.
  • Geocoding Services — Seamlessly convert city names to coordinates with direct_geocoding and vice versa with reverse_geocoding to power location-based queries.

How it works

  1. Subscribe to this server
  2. Enter your OpenWeatherMap API Key
  3. Ask about weather or air quality in any location from Claude, Cursor, or any MCP client

Who is this for?

  • Travelers & Logistics — Check conditions at destinations or along routes to optimize schedules.
  • Developers — Integrate weather context into apps and workflows without leaving your code editor.
  • Environmental Researchers — Monitor air quality and weather patterns across different coordinates instantly.

Built-in capabilities (6)

direct_geocoding

Convert city names or zip codes into coordinates

get_air_pollution

5, PM10, and NH3. Get current air pollution data

get_current_weather

Get current weather data

get_forecast

Get 5 Day / 3 Hour Forecast

get_onecall

Get One Call API 3.0 weather data

reverse_geocoding

Convert coordinates into city names

Why CrewAI?

When paired with CrewAI, OpenWeatherMap becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call OpenWeatherMap tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

OpenWeatherMap in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

OpenWeatherMap and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect OpenWeatherMap to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for OpenWeatherMap in CrewAI

The OpenWeatherMap MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 6 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

OpenWeatherMap
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures OpenWeatherMap for CrewAI

Every tool call from CrewAI to the OpenWeatherMap MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How do I get a comprehensive weather report including hourly and daily forecasts?

Use the get_onecall tool with latitude and longitude. It provides current data, 48-hour hourly forecasts, and 8-day daily forecasts in a single request.

02

Can I check the air quality for a specific location?

Yes, the get_air_pollution tool returns real-time data for pollutants including CO, NO2, O3, and particulate matter (PM2.5/PM10) for any coordinates.

03

How do I find coordinates for a city name to use with the weather tools?

Use the direct_geocoding tool. Simply provide the city name (and optionally state/country), and it will return the latitude and longitude needed for tools like get_onecall.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →