Integration

Visual Crossing Weather integration

Visual Crossing is a global weather data API built on one Timeline endpoint. Get the 15-day forecast, current conditions, and more than 50 years of historical observations for any address, US ZIP code or latitude,longitude, as daily and hourly records (temperature, precipitation, wind, humidity, pressure, UV, solar radiation, sunrise, moon phase) with active weather alerts, nearby hail, tornado, wind and earthquake events, statistical normals and degree days, for one location or several at once. Dates can be exact or dynamic periods (today, last30days, next7days). Each call is billed in records, one per day or per hour returned for each location (reported as queryCost). The legacy forecast and history endpoints (retired by the vendor at the end of 2026) and the CSV and flat JSON output formats are not exposed. Authentication is an API key sent as the key query parameter.

Connect Visual Crossing Weather How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Visual Crossing Weather.Built from the 4 Visual Crossing Weather tools below, on the connection you add once.

What you can do with Visual Crossing Weather

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Timeline, 3 operations

get_weather_for_dateGet weather for dateGETReturns weather for one date, past or future, a dynamic period such as today, yesterday or last30days, or one hour (date with time, filling currentConditions). Past dates are observations, near dates forecast, far dates statistical.
get_weather_for_date_rangeGet weather for date rangeGETReturns daily and hourly weather between two dates, both inclusive: historical observations for the past, the 15-day model forecast, then statistical forecast for later dates. Either date can be a dynamic period.
get_weather_forecastGet weather forecastGETReturns the 15-day weather forecast for a location, starting at midnight today local time: daily and hourly records, current conditions and active weather alerts.

Weather, 1 operation

get_weather_for_multiple_locationsGet weather for multiple locationsGETReturns Timeline weather for several locations in one call, by default the 7-day daily forecast of each. Limited to one concurrent request; for large datasets call get_weather_for_date_range per location.

Use Visual Crossing Weather from Claude Code, Cursor or Codex

Connect Visual Crossing Weather in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Visual Crossing Weather operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Visual Crossing Weather

Create your workspace
Sign up free. Nothing to install.
Connect Visual Crossing Weather once
Add your Visual Crossing Weather connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.