Weather MCP — Current Conditions & Forecast for Agents
Pricing
from $20.00 / 1,000 tool calls
Weather MCP — Current Conditions & Forecast for Agents
MCP server exposing current weather and forecast lookup as an agent tool. Connect Claude, Cursor, n8n or the OpenAI Agents SDK to live weather data.
Pricing
from $20.00 / 1,000 tool calls
Rating
0.0
(0)
Developer
NexGenData
Maintained by CommunityActor stats
0
Bookmarked
10
Total users
3
Monthly active users
8 days ago
Last modified
Categories
Share
Weather MCP
A Model Context Protocol server that gives AI agents weather data — current conditions and forecast for any location — as a callable tool. For assistants, planning and travel agents.
🛠 Tools (1)
get_weather— Current weather and forecast for a location.
🔌 Connect (Claude Desktop / Cursor / n8n / OpenAI Agents SDK)
Add this MCP server to your client config:
{"mcpServers": {"weather": {"url": "https://nexgendata--weather-mcp-server.apify.actor/mcp"}}}
Sample agent prompt:
Get the current weather and 5-day forecast for Chicago.
Pricing: $0.02 per tool call (Pay-Per-Event). Runs in Standby mode.
Related NexGenData MCP Servers
| Use case | Actor |
|---|---|
| Google Maps MCP (local business search) | google-maps-mcp-server |
| News MCP | news-mcp-server |
| Web-scraping MCP | web-scraping-mcp-server |
| Reddit MCP | reddit-mcp-server |
| 26-server gateway | enterprise-mcp-gateway |
FAQ
Q: What tool does this server expose?
A: One tool — get_weather(location) — returning current conditions and a multi-day forecast.
Q: Does it cover non-US regions?
A: Yes — pass any city name or lat,lon coordinates. Resolution varies by location.
Q: How do I call it?
A: Connect from an MCP client (Claude Desktop, Cursor, Cline, Windsurf) and invoke get_weather at reasoning time.
Input Example
This MCP server requires no run input — it is started by your MCP-compatible AI client (Claude Desktop, Cursor, Cline, Windsurf, n8n) and tools are invoked at reasoning time. To launch it directly via the Apify API for a test ping, pass an empty input:
{}
Output Example
When invoked through an MCP client, the get_weather tool returns structured JSON that the LLM consumes directly. A representative response looks like:
{"type": "text","text": "Weather data for 'London, UK'","structuredContent": {"weather": [{"location": "London, UK","temperature_c": 14,"conditions": "Light rain","humidity_pct": 82,"wind_kph": 19,"forecast": [{ "day": "Tue", "high_c": 16, "low_c": 9, "conditions": "Showers" },{ "day": "Wed", "high_c": 18, "low_c": 10, "conditions": "Partly cloudy" }]}],"total": 1}}
The underlying Apify dataset stores the same items in CSV / JSONL / Excel export formats for downstream pipelines.
How NexGenData Pricing Works
Every NexGenData actor uses pay-per-event pricing — you only pay for results that actually land in your dataset. No monthly minimum, no seat fees, no surprise overage bills.
- Actor Start: a single-event charge each time you spin the actor up (scaled to memory size)
- Result / tool call: charged per MCP tool call
- No charge for retries, internal proxy rotation, or failed sub-requests — those are absorbed by the platform
Apify Platform Bonus
New to Apify? Sign up with the NexGenData referral link — you get free platform credits on signup and help fund the maintenance of this actor fleet.
Integration Surface
Every actor in the NexGenData catalog can be triggered from:
- Apify console — point-and-click run
- Apify API — REST + webhooks
- Apify Python / JS SDKs — programmatic batch
- Zapier, Make.com, n8n — official integrations
- MCP — exposed as an MCP tool for Claude / ChatGPT / Cursor agents
- Schedules — built-in cron for daily / weekly / monthly runs
- Webhooks — POST results to any HTTPS endpoint on dataset write
Support
NexGenData maintains a large catalog of Apify actors and ships updates regularly. Bug reports via the Apify console issues tab get a response within 24 hours.
Home: thenextgennexus.com Full catalog: apify.com/nexgendata