Tomorrow.io (BYOK) — connector documentation

MCP endpoint: https://byok-tomorrowio.connectorbay.com/mcp
REST API: POST https://byok-tomorrowio.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-tomorrowio.connectorbay.com/openapi.json
Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
Authentication: your own Tomorrow.io API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
Health: https://byok-tomorrowio.connectorbay.com/health · Tool schemas: https://byok-tomorrowio.connectorbay.com/tools.json
Publisher: Unify Dynamics LLC · connectorbay.com/byok-tomorrowio · agent@connectorbay.com

What Tomorrow.io (BYOK) is for

Tomorrow.io (BYOK) lets an AI assistant read your own Tomorrow.io data through the Tomorrow.io API with a key you supply (API key). Read-only: 6 tools (get_realtime_weather, get_weather_forecast, get_recent_history, get_custom_timeline, list_saved_locations, get_weather_events). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.tomorrow.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Tomorrow.io. Tomorrow.io and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

"What is the weather like right now in Boston?"
"What is the daily forecast for the next 5 days in London?"
"What was the hourly weather in Austin over the last 24 hours?"
"Show hourly temperature and humidity in Boston for the next 12 hours"
"Which locations have I saved in Tomorrow.io?"
"Are there any wind events forecast near Boston?"

What it does

get_realtime_weather: Get the current weather at a location: temperature, feels-like, humidity, wind speed, gust and direction, cloud cover, visibility, pressure, UV index, precipitation probability and a numeric weather code.
get_weather_forecast: Get the forecast at a location: hourly for the next 120 hours (timesteps 1h) or daily for the next 5 days (1d), with temperature, wind, precipitation, cloud, UV and weather code values per step. Minute-by-minute needs a premium plan.
get_recent_history: Get the past weather at a location: hourly values for the last 24 hours (1h) or the daily summary of the last day (1d).
get_custom_timeline: Get a time series of chosen data layers (for example temperature, humidity, windSpeed, precipitationIntensity, uvIndex, cloudCover) for a point between a start and end time, at a step from 1m to 1d.
list_saved_locations: List the locations saved in the key owner's Tomorrow.io account with id, name and coordinates.
get_weather_events: Get active or forecast weather events (insights) of one category near a location, with start and end time, severity, certainty and urgency.

BYOK key

You bring your own Tomorrow.io API key (https://app.tomorrow.io/development/keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.tomorrow.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

https://docs.tomorrow.io/reference/welcome (the API this connector calls, with a BYOK key)

Live from the Tomorrow.io API (api.tomorrow.io) with a BYOK key; documentation: https://docs.tomorrow.io/reference/welcome. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Tomorrow.io. Tomorrow.io and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Tomorrow.io account.

Built for: Worldwide. Languages: English.