How do I get a Weatherbit API key?

Sign up for free at [**weatherbit.io**](https://www.weatherbit.io/account/create). Free tier includes 500 API calls/day.

Can I search by city name?

Yes! Use get_current_weather_by_city or get_forecast_daily_by_city with city name and optional country code (e.g. city='London', country='GB').

How far ahead can I forecast?

Daily forecast supports up to 16 days ahead. Hourly forecast supports up to 240 hours (10 days). Historical data goes back 30+ years.

Does it include air quality data?

Yes! Use get_air_quality with coordinates to get AQI, PM2.5, PM10, O3, NO2, SO2 and CO concentrations with health recommendations.

Weatherbit MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Weatherbit
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Weatherbit through Vinkius, pass the Edge URL in the `mcps` parameter and every Weatherbit tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Weatherbit Specialist",
    goal="Help users interact with Weatherbit effectively",
    backstory=(
        "You are an expert at leveraging Weatherbit tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Weatherbit "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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

About Weatherbit MCP Server

Connect to Weatherbit and access global weather data through natural conversation.

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

What you can do

Current Weather — Get real-time conditions (temperature, humidity, wind, precipitation, UV) by coordinates or city name
Daily Forecast — Get up to 16-day daily forecasts with high/low temps, precipitation, wind and UV
Hourly Forecast — Get up to 10-day hourly forecasts with detailed conditions
Historical Weather — Access 30+ years of historical daily weather data
Weather Alerts — Get active severe weather warnings and watches
Air Quality — Get AQI, PM2.5, PM10, O3, NO2, SO2 and CO readings
Severe Weather — Query recent severe weather reports (tornadoes, hail, floods)

The Weatherbit MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Weatherbit to CrewAI via MCP

Follow these steps to integrate the Weatherbit MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Weatherbit

Why Use CrewAI with the Weatherbit MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Weatherbit through the Model Context Protocol.

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

Weatherbit + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Weatherbit MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Weatherbit for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Weatherbit, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Weatherbit tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Weatherbit against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Weatherbit MCP Tools for CrewAI (10)

These 10 tools become available when you connect Weatherbit to CrewAI via MCP:

get_air_quality

Returns AQI score, PM2.5, PM10, O3, NO2, SO2, CO concentrations and health recommendations. Get air quality index (AQI) by coordinates

get_current_weather

Returns temperature, feels like, humidity, wind speed/direction, precipitation, cloud cover, visibility, UV index, weather description and icon. Get current weather conditions by coordinates

get_current_weather_by_city

Returns temperature, feels like, humidity, wind, precipitation, cloud cover, visibility, UV index and weather description. Get current weather conditions by city name

get_forecast_daily

Returns daily high/low temperatures, weather conditions, precipitation probability, wind, humidity, UV index and sunrise/sunset times. Get daily weather forecast by coordinates

get_forecast_daily_by_city

Returns daily forecasts for up to 16 days ahead with temperatures, conditions, precipitation, wind and UV index. Get daily weather forecast by city name

get_forecast_hourly

Returns temperature, precipitation probability, wind, humidity, cloud cover and weather conditions for each hour. Get hourly weather forecast by coordinates

get_forecast_hourly_by_city

Returns hourly forecasts with temperature, precipitation, wind and conditions. Get hourly weather forecast by city name

get_historical_weather

Returns temperature, precipitation, wind, humidity and other metrics for dates in the past 30 years. Get historical weather data by coordinates

get_severe_weather

Useful for tracking recent severe weather activity. Query severe weather reports in a geographic area

get_weather_alerts

Returns alert type, severity, description, effective/expiry times and affected areas. Get active weather alerts by coordinates

Example Prompts for Weatherbit in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Weatherbit immediately.

"What's the weather in London today?"

"Give me the 5-day forecast for Tokyo."

"What's the air quality in São Paulo?"

Troubleshooting Weatherbit MCP Server with CrewAI

Common issues when connecting Weatherbit to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Weatherbit + CrewAI FAQ

Common questions about integrating Weatherbit MCP Server with CrewAI.

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.

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.

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.

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.

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.