CONNECT GUIDES

Ask WeatherX through an AI assistant

One line gives an assistant such as Claude Code your key. From then on you ask in your own words, and it answers for your account only.

All connect guides

Everything else in these guides is a destination: a place we send alerts to. This is not a destination. No alert is ever sent to an assistant. Instead, an AI assistant you already use — Claude Code, for example — is given your key, and from then on it can ask us on your behalf, in your own words: is rain coming, which places do we watch, send a test alert. It answers for your account only.

Before you start

You need an assistant that speaks MCP — the standard several assistants use to reach an outside tool — and that lets you set a request header. Claude Code does, with the one line below. So do most IDE and agent tools that let you add an MCP server; their own settings screen asks for the same two things, the address and the header.
It cannot be added as a connector inside the Claude app or on claude.ai. Those need a sign-in flow (OAuth) we do not offer; your key is the only identity we issue.
Your API key, from your welcome email. The line below says YOUR-KEY where it goes.

The steps

Open a terminal on the computer where Claude Code runs, and paste this line with your key in place of YOUR-KEY:

claude mcp add --transport http weatherx https://nowcasting.weatherxanalytics.com/mcp \ --header "X-API-Key: YOUR-KEY"

Check it is there:
```
claude mcp list
```
It lists weatherx with the address above.
Start Claude Code and ask it, in your own words: Is rain coming to our depot in the next hour? or Which places do we watch? It picks the right question to ask us on its own; you never name a tool.
Read the answer. Every weather statement names the time it describes and how many minutes old the data is, so you can judge it — what every answer carries is below.

That line holds your key. Claude Code saves it, key included, in its own settings on that computer, so anyone who can use that computer can ask as you. Keep it off shared machines. If the key gets out, write to support@weatherx.earth and we disable it at once and issue another.

What you can ask

It has 8 tools. You never call one yourself; the assistant picks the one that answers what you asked.

Tool	What it answers
`get_forecast_summary`	Is it raining at this place now, is rain, lightning or hail expected in the next few hours, and for how long.
`get_precip_timeseries`	How the rain at this place changes, ten minutes at a time, from two hours ago to six hours ahead.
`get_lightning_risk`	Whether lightning is near this place now or will be shortly, and how far away.
`get_hail_risk`	Whether a hail-bearing storm is near this place now or will be shortly. Never a hail size: we cannot measure one.
`list_alert_sites`	The places your account watches.
`get_recent_events`	The alerts we have sent you recently, newest first.
`create_alert_site`	Adds a place to watch. On a free account, which holds one place, it says so instead.
`send_test_alert`	Sends one real test alert to every destination on one of your places, so you can see the whole path works.

What every answer carries

Its unit. A rain rate says mm/h, a distance says km.
The time it describes, and how many minutes old that is. They are not the moment you asked: a forecast cycle takes a few minutes to publish, and the answer says which moment it is about.
After 30 minutes the answer says so, in a plain sentence, so the assistant does not read an old forecast out as the weather now.
A place outside our two forecast areas gets a plain sentence: “We do not cover this location yet -- it is outside both of our forecast grids (Europe and the continental United States).”
Data we could not read this cycle gets one too: “This location is inside our coverage, but we could not read the forecast data for it right now. This is temporary -- try again shortly.” It never guesses a value, and never says “no hail” about a moment it cannot name.

Two things it asks you first

create_alert_site and send_test_alert change something: the first adds a place to your account, the second makes a real message leave — to every destination on that place, so if the place writes into your team's chat, your team sees the test. Both are marked so that a well-behaved assistant asks you before calling either.

On a free account, which holds one place, asking to add a second is answered with “Your plan holds one place.” and nothing changes.

How much you can ask

A free key may spend 300 calls a day, across everything the key opens — the assistant and our data routes together. Past that, every call gets a plain sentence saying the allowance starts again at midnight UTC. Your alerts are not affected: they run on our side, not on your calls. Paid keys have no allowance.

What it cannot do

Nothing about anybody else's account. Your key is the only identity it has, so there is no way to ask about another customer's places or alerts.
It cannot connect a destination for you. The buttons in your welcome email do that, and each has its own page here.
It cannot move a free place. A free account's one place is fixed at sign-up.
It sees Europe and the continental United States, the same as everything else we serve.

How to stop it

Take it off the assistant with one command:

claude mcp remove weatherx

That is all there is to do on your side, and nothing on ours changes. It does not stop the alerts and does not disable the key. The key still works everywhere else it is used, and every destination carries on receiving.

To stop the alerts for a place, your WeatherX email carries a Stop link at the bottom. Open it, and press the button on the page it shows. It stops every alert for that place and turns off every destination on it, at any hour. It needs no key and no reply.

Write to support@weatherx.earth, and ask us to disable the key itself, if it has got out or you no longer want it — we disable it at once and can issue another.

That is the whole job

If the assistant answers and you know how to take it off again, you are done. You can stop reading here.

Everything below this line is for a developer — somebody who makes calls to our API from a program. It is a different way to do some of the same things, and one thing more. Nobody needs it to receive alerts.

For any assistant, not only Claude Code

Any client that speaks MCP over HTTP can use this. It needs two things:

The address: https://nowcasting.weatherxanalytics.com/mcp. It answers POST only; a browser that opens it gets a refusal, which is why nothing on this page draws it as a link.
Your key, in a header. Either X-API-Key: wx_live_… or Authorization: Bearer wx_live_… works. If both are sent, X-API-Key is the one we read.

The server keeps no session between calls: every request carries everything it needs, so two calls may land on two different workers and both are answered. Every call counts against a free key's daily allowance, the start-up handshake included.

The same answers, without an assistant

Every tool calls the same function as a public route, so a program can skip the assistant and ask the route directly, with the same key in the same header:

GET /summary?lat=…&lon=…
X-API-Key: wx_live_…

The four weather tools stand on /summary, /timeseries, /lightning/risk and /hail/risk. The account tools stand on the /portal routes named in the second half of every destination page here: the list of places, adding one, and the test send.

If it refuses

401 and a sentence: no key, an unknown key, or a disabled one. Nothing is answered without a working key.
429 and a sentence: a free key's allowance for today is spent. A Retry-After header says when it starts again.

The steps on this page were checked on 6 September 2026. If the commands on this page no longer work in your assistant, or it answers differently from what this page says, write to support@weatherx.earth and tell us. A person reads it.

This page holds no key, sets no cookie and runs nothing that follows you.