Tempest Weather (BYOK)

Tempest Weather (BYOK) — connector documentation

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

What Tempest Weather (BYOK) is for

Tempest Weather (BYOK) lets an AI assistant read your own Tempest Weather data through the Tempest Weather API with a key you supply (Tempest personal access token). Read-only: 5 tools (list_stations, get_station, get_latest_station_observation, get_device_observations, get_station_forecast). 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 swd.weatherflow.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Tempest Weather. Tempest Weather 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:

• "Which Tempest stations and devices do I have?"
• "What devices are attached to my Tempest station 12345?"
• "What is the temperature, wind and rain at my Tempest station right now?"
• "Show yesterday's observations from my Tempest device"
• "What is the forecast for my Tempest station for the next days, in Fahrenheit and mph?"

What it does

• list_stations: List the Tempest stations the token owner can access with station id, name, elevation and the ids of the devices at each station.
• get_station: Get one Tempest station: name, elevation and the devices attached to it.
• get_latest_station_observation: Get the latest observation of a station: station units, timezone and one record with air temperature, pressure, humidity, wind, rain, UV, solar radiation, lightning and derived values such as feels-like and dew point.
• get_device_observations: Get observations of one device: the latest one, a whole UTC day (day_offset) or a time range (time_start and time_end, at one-minute resolution when five days or less). Each observation is a list of numbers in the order the Tempest API reference gives for the device type.
• get_station_forecast: Get the forecast for a station: current conditions plus daily and hourly forecast, in the chosen units.

BYOK key

You bring your own Tempest Weather Tempest personal access token (https://weatherflow.github.io/Tempest/api/). 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 swd.weatherflow.com 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.

Notices

Weather data from WeatherFlow Tempest; rebroadcasting needs credit to WeatherFlow or Tempest and a link back.

Data sources

• https://weatherflow.github.io/Tempest/api/swagger/ (the API this connector calls, with a BYOK key)

Live from the Tempest Weather API (swd.weatherflow.com) with a BYOK key; documentation: https://weatherflow.github.io/Tempest/api/swagger/. 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 Tempest Weather. Tempest Weather 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 Tempest Weather account.

Built for: Worldwide. Languages: English.

Tempest Weather (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Tempest Weather (BYOK) is. Tempest Weather (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Tempest Weather data: Read your Tempest weather station list, latest and recent observations and the station forecast with your own personal access token. You bring your own Tempest Weather Tempest personal access token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Tempest Weather call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to swd.weatherflow.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Tempest Weather rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Tempest Weather receives. The request we make on your behalf, including the key and the arguments, under Tempest Weather's own terms and privacy policy. Tempest Weather acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Tempest Weather gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Tempest Weather data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Tempest Weather (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Tempest Weather at any time to end all access.

Children. Tempest Weather (BYOK) is a general-audience service operated by the adult using the assistant, under Tempest Weather's own age rules.

Changes. We will post changes here with a new effective date.

Tempest Weather (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Tempest Weather (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Tempest Weather (BYOK) provides: Read your Tempest weather station list, latest and recent observations and the station forecast with your own personal access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Tempest Weather credentials and only access data you are allowed to access. Tempest Weather's terms apply to your use of Tempest Weather; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Tempest Weather. Tempest Weather and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Tempest Weather returns, lightly trimmed; it may be incomplete, delayed or changed by Tempest Weather. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Tempest Weather account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Tempest Weather's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Tempest Weather may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Tempest Weather key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Tempest Weather takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-tempest-weather

Tempest Weather (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-tempest-weather.connectorbay.com/mcp
• REST API: https://byok-tempest-weather.connectorbay.com/openapi.json
• Live status: https://byok-tempest-weather.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Tempest Weather (BYOK) never asks for them.