Weather Mcp Server
Let your coding agent pull forecasts, climate history, and severe-weather alerts for a place so you can pick outdoor launch dates, events, or shoot days without leaving the chat.
Overview
com.thenextgennexus/weather-mcp-server is an MCP server for the Grow phase that delivers location-based weather forecasts, climate history, and severe alerts into your agent workflow.
What is this MCP server?
- Remote streamable-http MCP endpoint wired for agent clients with Bearer authorization
- Location-based forecasts for go/no-go decisions on outdoor launches and events
- Historical climate context for comparing typical conditions at a venue or date
- Severe-weather alerts so agents can flag safety or logistics risks before you commit
- Hosted via Apify proxy—register once and call tools from Claude Code, Cursor, or Codex
- Server schema version aligns with MCP 2025-12-11 server.schema.json
- Packaged as weather-mcp-server version 1.0.0
- Single streamable-http remote endpoint behind the Apify-hosted MCP proxy
What problem does it solve?
You are planning an outdoor launch or event and do not want to guess the weather or manually cross-check forecasts while your agent drafts schedules and copy.
Who is it for?
Solo builders orchestrating outdoor meetups, shoots, or regional activations who want weather data on demand inside Claude Code, Cursor, or Codex.
Skip if: Teams that need a full meteorology dashboard, proprietary station hardware, or deep numerical modeling outside what the hosted weather tools return.
What do I get? / Deliverables
After you register the remote server with your Apify token, your agent can cite forecasts, historical climate context, and active severe alerts for a location when you plan dates and logistics.
- Agent-callable weather forecasts for a specified location
- Climate history context the agent can use when comparing dates or venues
- Severe-weather alert information tied to a location for risk-aware planning
Recommended MCP Servers
Journey fit
Weather timing sits in Grow because solo builders use it to plan outdoor activations, meetups, and content shoots where attendance and safety depend on conditions, not to write application code. Content is the canonical shelf for event- and campaign-adjacent planning where location-specific forecasts and alerts inform scheduling and messaging.
How it compares
MCP data integration for weather queries, not an agent skill or a standalone forecasting web app.
Common Questions / FAQ
Who is com.thenextgennexus/weather-mcp-server for?
It is for solo and indie builders who use AI coding agents to plan outdoor events, launches, and location-dependent work and want forecasts, history, and alerts without leaving the agent.
When should I use com.thenextgennexus/weather-mcp-server?
Use it when you are choosing dates, routes, or venues for outdoor activities and need the agent to incorporate current forecasts, past climate patterns, or severe-weather warnings into the plan.
How do I add com.thenextgennexus/weather-mcp-server to my agent?
Add the streamable-http remote URL from the server manifest to your MCP client configuration, set the Authorization header to your Apify API token from console.apify.com, then restart or reload MCP so the weather tools appear.