Tomorrow.io Weather MCP App

Forecasts, air quality, pollen and wildfire-risk widgets from Tomorrow.io inside Claude.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Tomorrow.io Weather MCP App connector does

The Tomorrow.io Weather MCP App connects Tomorrow.io's weather services to Claude and any MCP client. Nine read-only tools return forecasts, air quality, pollen levels, pollutant concentrations and wildfire risk for any coordinates, rendered as interactive widgets where the client supports them. It needs no Tomorrow.io account, API key or sign-in.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Tomorrow.io Weather MCP App tools (9)

  • tio_mcp_apps_list_widgetsRead-only

    List the available weather and air quality views that can be shown. USE when the user asks what types of weather information are available, or wants to know what views/widgets they can explore. For actual weather data, use the other tools directly: - show_upcoming / show_summary — weather forecast - show_aqi_mini — air quality - show_aqi_pollen — pollen levels - show_fire — fire risk

  • tio_mcp_apps_show_upcomingRead-only

    Show the weather forecast for a location — current conditions plus the next 6 days. USE when the user asks about the weather, forecast, temperature, or conditions for a specific place. This is the default weather tool — use it for any general weather question.

  • tio_mcp_apps_show_summaryRead-only

    Show a concise weather summary for a location — current conditions, a natural-language forecast for the next 24 hours, and how today compares to yesterday. USE when the user wants a quick overview or summary of the weather, or asks "what's it like outside?"

  • tio_mcp_apps_show_current_6Read-only

    Compare current weather across 2-6 locations side by side. USE when the user wants to compare weather in multiple cities, or asks about conditions in several places at once.

  • tio_mcp_apps_show_aqi_miniRead-only

    Show the current air quality index (AQI) for a location, alongside weather conditions. USE when the user asks about air quality, pollution levels, or whether it's safe to exercise outdoors.

  • tio_mcp_apps_show_aqi_6Read-only

    Compare air quality across 2-6 locations side by side. USE when the user wants to compare air quality in multiple cities.

  • tio_mcp_apps_show_aqi_pollenRead-only

    Show pollen levels (tree, grass, and weed) and air quality for a location. USE when the user asks about pollen, allergies, hay fever, or pollen forecasts.

  • tio_mcp_apps_show_aqi_pollutantRead-only

    Show detailed air pollutant concentrations (PM2.5, PM10, O3, NO2, CO, SO2) for a location. USE when the user asks about specific pollutants, particle matter, or detailed air quality data.

  • tio_mcp_apps_show_fireRead-only

    Show the wildfire risk index (FWI) and wind conditions across 2-6 locations. USE when the user asks about fire risk, wildfire danger, or fire weather conditions.

Read from the server on 2026-11-17, including each tool's own safety annotations.

Limits

  • Coordinates only. Every tool requires latitude and longitude. There is no place-name input and no geocoding tool on the server; the client resolves names before calling.
  • No single-location fire check. tio_mcp_apps_show_fire and both comparison tools require two to six locations, and a call fails when fewer than two resolve.
  • Readings, not health advice. The air quality, pollutant and pollen tools return values for a location. Neither the tools nor Tomorrow.io's reference interpret them for asthma, allergies or any other condition, and this page does not either.
  • No stated coverage or rate limit. Tomorrow.io's reference names no geographic coverage limits and no numeric rate limit; its troubleshooting advice for a rate limit is to wait briefly and retry. We did not call a tool, so we cannot report a quota.
  • Widgets need an MCP Apps client. Claude Code and other clients without MCP Apps get text and structured data only.
  • A different product needs a key. Tomorrow.io's raw-data MCP, documented separately, requires a Tomorrow.io API key. Anthropic's directory snapshot of 2026-11-17 lists only this MCP App.
  • Data handling, as Tomorrow.io states it. The reference says the connector receives only tool arguments — coordinates and unit preference — and cannot access conversation history, files or account information. The reference names Tomorrow.io's website privacy policy and terms of service as governing; Anthropic's listing links the product privacy policy instead.

Frequently asked questions

Do you need a Tomorrow.io account or API key to use the MCP App?

No. Tomorrow.io's documentation states the MCP App needs no Tomorrow.io account and no API key, and that the connector needs no sign-in. We confirmed it on 2026-11-17: an anonymous handshake returned all nine tool schemas with no credential and no authentication challenge. The API-key requirement belongs to a different product, Tomorrow.io's raw-data MCP, which this page does not cover.

Why do I get a text answer but no Tomorrow.io widget?

Your client does not support MCP Apps, the extension that renders the widget. Tomorrow.io documents that clients without it receive a short text summary and the structured data instead, and names Claude Code as one of them. The numbers are the same either way, so Claude can still answer follow-up questions; only the interactive card is missing.

Why does Tomorrow.io say it could not fetch weather data for a place?

The server could not resolve the place or found no data for it. Every tool takes latitude and longitude rather than a place name, and Claude converts the name you type into coordinates first. Tomorrow.io advises naming a nearby city or giving coordinates directly. Multi-location tools fail the same way when fewer than two of the locations resolve.

Why is the Tomorrow.io widget blank?

Start a new conversation first. Tomorrow.io's troubleshooting advice for a blank widget is to open a fresh chat, and if the widget is still empty, to reconnect the connector under Customize then Connectors. If the connector does not appear in a chat at all, open the plus menu, choose Connectors and confirm Tomorrow.io is switched on.

Sources

Use it in an agent

Put Tomorrow.io Weather MCP App to work.

Connect Tomorrow.io Weather MCP App once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.