Meteomatics (BYOK)

Meteomatics (BYOK) — connector documentation

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

What Meteomatics (BYOK) is for

Meteomatics (BYOK) lets an AI assistant read your own Meteomatics data through the Meteomatics API with a key you supply (API username). Read-only: 8 tools (get_current_weather, get_weather_time_series, get_weather_at_time, get_postal_code_weather, list_recent_earthquakes, list_flood_alerts, list_lightning_strikes, get_account_usage). 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.meteomatics.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Meteomatics. Meteomatics 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 temperature right now at 47.4245, 9.3767?"
• "Give me the hourly temperature forecast for the next 2 days at 47.4245, 9.3767"
• "What was the temperature at 47.4245, 9.3767 on 2026-07-01 at noon UTC?"
• "What is the temperature now in Berlin postal code 10117?"
• "Which earthquakes happened in the last day?"
• "Are there flood alerts in the Alps right now?"

What it does

• get_current_weather: Current values of one or more weather parameters at a latitude and longitude. Answers are JSON time series: data[].parameter, coordinates[].lat/lon and dates[] with date and value.
• get_weather_time_series: A time series of weather parameters at a point: from a start time for a duration at a step, for example two days hourly. Past dates give history, future dates give forecast. Answers are JSON time series: data[].parameter, coordinates[].lat/lon and dates[] with date and value.
• get_weather_at_time: Weather parameters at a point for one date and time (past, present or future). Answers are JSON time series: data[].parameter, coordinates[].lat/lon and dates[] with date and value.
• get_postal_code_weather: Current weather parameters for a postal code, written with country prefix, for example postal_DE10117 or postal_CH9014; join several with a plus sign. Answers are JSON time series: data[].parameter, coordinates[].lat/lon and dates[] with date and value.
• list_recent_earthquakes: Recent earthquakes as GeoJSON features with magnitude, depth, source and issue time. Defaults to the last 24 hours worldwide.
• list_flood_alerts: Active flood alerts worldwide or inside a bounding box, with the alert provider and properties; flood area geometry only on request.
• list_lightning_strikes: Lightning strokes inside a bounding box and time range: stroke time, latitude, longitude, current in kA and type.
• get_account_usage: Show how many queries the account has used and its limits (JSON usage statistics).

BYOK key

You bring your own Meteomatics API username (https://www.meteomatics.com/en/weather-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 api.meteomatics.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.

Data sources

• https://www.meteomatics.com/en/api/getting-started/ (the API this connector calls, with a BYOK key)

Live from the Meteomatics API (api.meteomatics.com) with a BYOK key; documentation: https://www.meteomatics.com/en/api/getting-started/. 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 Meteomatics. Meteomatics 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 Meteomatics account.

Built for: Worldwide. Languages: English.

Meteomatics (BYOK) — Privacy Policy

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

What Meteomatics (BYOK) is. Meteomatics (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Meteomatics data: Read current weather, forecasts and history for any point or postal code, plus lightning, flood alerts and earthquakes from Meteomatics with your own username and password. You bring your own Meteomatics API username; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Meteomatics 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 api.meteomatics.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 Meteomatics 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 Meteomatics receives. The request we make on your behalf, including the key and the arguments, under Meteomatics's own terms and privacy policy. Meteomatics acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Meteomatics 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 Meteomatics 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. Meteomatics (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 Meteomatics at any time to end all access.

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

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

Meteomatics (BYOK) — Terms of Service

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

1. The Service. Meteomatics (BYOK) provides: Read current weather, forecasts and history for any point or postal code, plus lightning, flood alerts and earthquakes from Meteomatics with your own username and password. 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 Meteomatics credentials and only access data you are allowed to access. Meteomatics's terms apply to your use of Meteomatics; 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 Meteomatics. Meteomatics 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 Meteomatics returns, lightly trimmed; it may be incomplete, delayed or changed by Meteomatics. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Meteomatics 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 Meteomatics'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; Meteomatics 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 Meteomatics 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 Meteomatics 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-meteomatics

Meteomatics (BYOK) support

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

• MCP endpoint: https://byok-meteomatics.connectorbay.com/mcp
• REST API: https://byok-meteomatics.connectorbay.com/openapi.json
• Live status: https://byok-meteomatics.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. Meteomatics (BYOK) never asks for them.